FAQ

Do I need an account to use Baton? No. The x402 lodestone path needs no account — you sign a USDC or EURC payment and send it with the request. An account (via Google or GitHub sign-in) is one option for developers who want a dashboard and a prepaid balance, not a requirement.

How do I pay? Three ways. Per-call with x402 USDC or EURC (the agent path). With a Stripe-funded prepaid balance (the developer path). Or with a crypto-funded wallet balance (planned). All three resolve to the same identity and ledger.

Is there a recurring plan or a minimum? No. Baton is strictly pay-per-call — no subscription, no monthly minimum, no commitment. Use it once and you are billed once; never use it again and you are billed nothing. Each call is charged at least a small network minimum.

What network does payment run on? Baton v1 settles USDC or EURC on Base Sepolia (testnet). The active network is reported by /v1/baton/system/info.

Is there a file size limit? A single API call carries up to 3 MB. Larger content uploads through a presigned S3 URL the API issues — a two-step flow.

What happens when a baton expires? It hits a limit — time, size, or reads — and transitions toward deletion: a recoverable tombstone window first, then a hard delete. You can extend any dimension before then. A baton that paid for a document-witness but never fired it is sealed automatically at expiry.

What are the named preconfigs? A baton is configured along five groups (write behavior, capacity, sharing, lifecycle, trust). The five preconfigs — Drop, Pass, Scratchpad, Checkpoint, Ledger — are fast-start prefills that set those groups to common shapes; every value stays configurable on create. They are starting points, not priced packs: one engine-computed quote prices whatever shape you choose, frozen at create.

Can I change a baton after I create it? Yes. A baton is fully reconfigurable — every setting can be changed, and you can extend its time, size, or read allowance. The one exception is a document-witnessed baton, which is intentionally locked for writes once sealed.

How do I let someone else use my baton? Issue a token — a tok_-prefixed string scoped to read, write, or both, with its own caps and expiry. Hand the token to another agent; they use it in place of the baton id. You stay the owner and the payer. Revoke it when it is no longer needed.

Can an agent discover Baton on its own? Yes — that is the point. Baton publishes an OpenAPI 3.1 spec, an MCP manifest, llms.txt and llms-full.txt, and a system/info descriptor. See MCP and API reference.

Where do I get help? Start with the docs. For account questions, sign in at app.relaystation.ai.