Docs

Runrail App Usage

Use the Runrail App to sign in, set up and fund your Execution wallet, manage recurring jobs, create API credentials, and inspect execution history on Base Sepolia.

Sign In With Your Wallet

At https://app.runrail.app, connect your browser wallet and sign the message Runrail requests. A successful signature starts a secure browser session for the Runrail workspace associated with that wallet address.

The sign-in wallet does not become the Execution wallet, pay gas, or sign scheduled transactions. The App does not persist wallet signatures, SIWE messages, or show-once API credential plaintext in localStorage or sessionStorage. Authentication still uses a secure browser session.

Return To The Same Workspace

Signing in with the same identity address returns you to the same Runrail workspace, including its Execution wallet, jobs, readiness, lifecycle, limits, and execution history.

Jobs created through the API appear in the App. Jobs created through the App appear through the API. An unavailable read is shown as unavailable, not as an empty workspace.

Set Up And Fund The Execution Wallet

Request Execution-wallet setup from the App. When Runrail reports the address as ready, fund it with Base Sepolia test ETH and use the App to inspect its lifecycle, balance, and readiness.

The Execution wallet submits scheduled transactions for your Runrail workspace. Runrail operates its key, and the App never receives the private key or signing capability.

Create And Manage Jobs

The App supports the full recurring-job workflow:

  • create a Base Sepolia job with a target, calldata, future start, and interval;
  • inspect ready, not_ready, or unknown readiness and any reported reason;
  • activate, pause, resume, or irreversibly archive the job;
  • inspect scheduled executions and individual attempts.

Runrail fixes transaction value to 0 and controls validation, simulation, gas policy, retry classification, quotas, rates, and safety checks. See Limits and Safety for exact values.

Understand Execution Results

For each scheduled slot, the App shows the current execution state and up to three attempts. It distinguishes retryable failures, recovery, exhaustion, reverted transactions, policy skips, and failed preconditions.

Confirmed success includes terminal receipt evidence. A transaction hash or explorer page supports inspection but does not replace Runrail's confirmation state.

Create And Protect API Credentials

Use API Access in the App to:

  • create a credential through your browser session;
  • copy its plaintext exactly once;
  • list non-secret metadata;
  • revoke an active credential permanently.

Plaintext cannot be recovered after you dismiss or lose the one-time display. If a create request has an unclear result, refresh the metadata list and revoke any possible unknown credential before you explicitly create another. Do not automatically repeat the create request.

You may have at most 3 active credentials and create at most 10 credentials in a rolling 24-hour period. A frozen workspace can list and revoke credentials but cannot create one.

API credentials work only at https://api.runrail.app/v1; they do not sign you in to the App. The App continues to use its browser session. Signing out or letting the browser session expire does not revoke an API credential.

Sign Out

Signing out revokes the current browser session and clears session-specific App memory. It does not delete your workspace, Execution wallet, jobs, history, or API credentials.

Product Limits

The App does not provide public run-now, webhooks, caller-defined retry policy, nonzero transaction value, mainnet, multi-chain execution, billing, OAuth, organizations, teams, RBAC, an SDK program, or a developer portal.

See Runrail API Usage and Limits and Safety.

Back to docs index