Build with Juicebox.

Read projects, prepare transactions, and follow results across chains. Start with a public request or connect your app in a few steps.

I need data →Read current values or search project history.I need a transaction →Prepare, review, sign, then check the result.I am building an integration →Find request formats and supported actions.

Your first request

Explore supported chains and execution options. No account required.

curl https://juicebox.center/api/v1/capabilities

For protected requests, create an API connection, download its file, and install the client:

npm install https://juicebox.center/api/client/juicebox-center-client-0.1.0.tgz
chmod 600 juicebox-connection.json
npx center account --connection juicebox-connection.json

The client handles authentication. Your wallet separately approves spending.

Complete quickstart → / Client workflows

Choose a data source

Read the blockchain: find the deployed contract and its interface (ABI), then call a read-only method. Results identify the verified block they describe.
Search history: Bendystraw collects blockchain records into a searchable index. Choose real funds (mainnet) or test funds (testnet), filter to V6, and use the returned cursor to get the next page. Pages may reflect different blocks.
Use a named operation: choose a project or developer task from the operations catalog and follow its required input format, called a schema.

Project routes require source=onchain or source=bendystraw. Keep amounts and large integers as decimal strings. If a value could not be read, report it as unknown.

Prepare → review → sign → check

Create a saved set of proposed transactions: a plan. Use a named preparation or contract_calls. Sign the API request and include an Idempotency-Key so a retry can find the same result.
Review the exact chain, recipient, encoded instructions (calldata), native token amount, required earlier steps, block evidence, plan commitment and expiry. Test each ready step with a simulation.
Have the plan wallet sign the exact transaction. Submit those signed bytes with a fresh owner-signed API request, or a bot request carrying the owner’s exact approval.
Retrieve the plan with refresh=true to check what happened. Continue only when required earlier steps are confirmed. Check an uncertain submission by its existing transaction hash before retrying.

API access does not let a bot spend the owner's funds. Check capabilities for supported ways to send transactions and pay network costs. Steps on different chains can succeed or fail separately; confirmation on the sending chain does not prove funds arrived on the receiving chain.

Plans, retries, confirmations and partial journeys / Session lifecycle and quotas

A project can also be created without a transaction: publish a signed, frozen set of per-chain launch calls, then let Center's sponsor execute them on the supported rollups. See project intents.

Prepay for transactions across chains

Prepare calls on supported chains and pay their network costs together. Center returns the exact calls for your wallet to approve, submits them, and prepares one funding transaction from the verified quote. Review and sign the funding transaction, then follow progress through Center.

Check whether funding already arrived before paying again. Verify each call on its destination chain; a quote or provider status alone does not prove payment or success. See the full guide and agent workflow.

Use one wallet address across networks

On Accounts, choose the networks for a separate transaction wallet. Review the shared setup and approve creation on each network. Then add prepared transactions to one review list and follow each network's result. Balances and permissions remain separate on each network. Your signed-in wallet pays the creation fees; supported later transactions can use sponsored network fees.

For unattended payments, approve a bot's allowed action, recipient, spending limits and expiry once on each network. After activation confirms, the bot can sign and send within those permissions without further owner prompts. Check sessions.configuredChainIds for networks where activation is available. Changes to the limits and transactions outside them need owner approval.

Wallet setup guide / Run an unattended payment / Current capabilities

Endpoint reference

Expand a group, then an endpoint. The OpenAPI document contains exact parameters and schemas; the contract method catalog supplies ABI-specific argument and output schemas.

Find an endpoint

Discovery (9)

Public, pinned schemas and current capability discovery.

GET/api/v1 public

Find API entry points