Runrail Public Beta — Base Sepolia

Recurring
on-chain maintenance,
without silent failure.

Schedule recurring EVM contract calls, then follow attempts, retries, confirmation, terminal receipts, transaction hashes, and explorer evidence in one place.

Open Runrail App Use the API
  • Base Sepolia
  • Chain ID 84532
  • Testnet only
  • App + API

What Runrail does

Turns recurring contract calls into inspectable scheduled outcomes.

Runrail coordinates interval-based Base Sepolia calls for protocol teams that need to know whether maintenance ran, retried, recovered, exhausted, confirmed, or failed.

Schedule the call

Choose a target, calldata, future start, and interval. Runrail fixes the network to Base Sepolia and transaction value to 0.

See every attempt

Follow the initial attempt and up to two retries through clear failure, recovery, or exhaustion states.

Verify the outcome

Confirmation, terminal receipts, transaction hashes, and Base Sepolia explorer links show the recorded result.

Why it is useful

Operational clarity where a silent gap is expensive.

A transaction submission is not treated as success. Runrail keeps job lifecycle, scheduled executions, attempts, confirmation, receipts, hashes, and explorer evidence connected so teams can understand what actually happened.

A visible result for every run

Every scheduled run leaves a visible record, including runs that confirm, retry, fail, or cannot start.

Failure you can follow

Primary and fallback paths, retry, recovery, and exhaustion stay visible in execution history.

State that survives return

Your Runrail workspace, Execution wallet, jobs, lifecycle, limits, and history remain the same when you come back.

One product, two self-service interfaces

Use the App or API without splitting your Runrail state.

Jobs created through the App or API appear in the same Runrail workspace, with the same Execution wallet, readiness, limits, lifecycle, and execution history.

Runrail App

Sign in with your wallet. The App uses the resulting secure browser session for your product actions.

Open Runrail App

Runrail API

Create a show-once bearer credential in the App, then use the API at https://api.runrail.app/v1 from your own tools and agents.

Read API usage guide

Browser sessions and bearer credentials are not interchangeable. The App never switches its own calls to bearer authentication. Multiple credentials do not increase quotas or rate limits.

Identity and execution

Your sign-in wallet verifies who you are. A separate wallet executes.

Sign in with a browser wallet to verify that you own the address. Your Runrail workspace has a separate Execution wallet that submits scheduled transactions using Base Sepolia test ETH you provide.

  1. Sign in

    Your wallet signature starts a secure browser session and recovers your Runrail workspace.

  2. Fund test gas

    Fund the dedicated Execution wallet with Base Sepolia test ETH; do not send valuable assets.

  3. Schedule

    Create recurring work with transaction value=0 and a future interval.

Execution evidence

Follow work from scheduled slot to terminal truth.

Runrail preserves lifecycle and execution history across both interfaces, including attempts, confirmation, receipts, hashes, and explorer evidence.

Attempts and retry

One initial attempt and up to two retries can expose failure, recovery, or exhaustion.

Confirmation and receipt

Confirmation-defined success leads to terminal receipt evidence rather than a submission-only claim.

Hash and explorer

Transaction hashes and server-provided Base Sepolia explorer links support the recorded outcome.

Limitations and safety

Testnet-only, with explicit safety limits.

Runrail runs on Base Sepolia, chain ID 84532, with user-funded test gas, transaction value=0, up to three attempts per scheduled slot, and server-controlled readiness, gas, quota, and safety checks.

Included

  • App and API over shared product state
  • Dedicated Execution wallet for each workspace
  • Jobs, lifecycle, attempts, confirmation, receipts, hashes, and explorer evidence
  • Show-once API credentials with metadata listing and terminal revocation

Not in the first release

  • Public run-now, webhooks, or caller-defined retry policy
  • Nonzero value, mainnet, or multi-chain execution
  • Billing, OAuth, organizations, teams, or RBAC
  • SDK program, developer portal, production support, or SLA
Read Limits and Safety

Secondary path

Guided Pilot for custom, out-of-scope, or higher-touch work.

Guided Pilot is a secondary manual path for teams whose concrete recurring use case does not fit Public Beta's Base Sepolia, value=0, scheduling, or safety limits. It is not required for ordinary App or API access.

FAQ

Short answers about the product boundary.

What network does Public Beta use?

Base Sepolia only, chain ID 84532. Public Beta does not execute on mainnet.

Do App and API create separate products?

No. They expose the same workspace, Execution wallet, jobs, lifecycle, limits, history, and evidence.

Does my sign-in wallet execute jobs?

No. It verifies your identity only. A separate Execution wallet submits Runrail transactions.

Can I use an API credential to sign in to the App?

No. The App uses your wallet signature and a secure browser session. Bearer credentials apply only to the Runrail API.

Does signing out revoke API credentials?

No. Credentials remain active until you permanently revoke them through the App.

Is Guided Pilot required for API access?

No. It is secondary manual review only for custom, out-of-scope, or higher-touch work.

Choose your interface

Use one Runrail product through App or API.

Start with the App, or create a self-service credential in the App and follow the API usage guide.

Open Runrail App Use the API