Superbridge
Start typing to search...

Reference

Commands

Full reference for every superbridge subcommand

Every command accepts the global flags below in addition to its own arguments. Run superbridge <command> --help for the canonical, up-to-date list.

Global Flags

Every command pretty-prints to stdout by default. Pass --output json to get raw JSON instead — useful for piping into jq, saving to a file, or feeding into another command.

FlagDescription
--api-keyOverride SUPERBRIDGE_API_KEY for this invocation.
--outputpretty (default) or json.

health

Check the API is reachable and your key works.

superbridge health

chains

List supported chains. Without filters, returns every chain Superbridge knows about.

FlagDescription
--keyFilter by shorthand chain key (e.g. eth).
--idFilter by native chain id (e.g. 1).
--uidFilter by Superbridge chain UID.
--mainnetsRestrict to mainnet chains.
--testnetsRestrict to testnet chains.
superbridge chains --mainnets
superbridge chains --key eth --output json | jq '.[0]'

tokens

List tokens, optionally filtered by chain or search term. Cursor-paginated.

FlagDescription
--addressFilter by token address.
--chain-key, --chain-id, --chain-uidFilter by chain.
--searchSearch by name, symbol, or address.
--cursorCursor for fetching the next page of results.
--limitPage size (1–100).
superbridge tokens --chain-key eth --search USDC --limit 5

routes

Fetch available routes for a bridge or swap. Body-heavy — pass the request via --body, with individual flags overriding fields.

FlagDescription
--bodyRequest body as inline JSON, @path/to/file.json, or - for stdin.
--from-chain-key, --from-chain-id, --from-chain-uidSource chain.
--to-chain-key, --to-chain-id, --to-chain-uidDestination chain.
--from-token, --to-tokenToken addresses (0x000...0 for native).
--sender, --recipientAddresses involved in the route. If omitted, a default address is derived for the source/destination chain's VM.
--amountAmount in human units (e.g. 0.01 for 0.01 ETH or USDC). The CLI scales by the from-token's decimals.
--slippageSlippage as a decimal (e.g. 0.005 for 0.5%).
--providerComma-separated list of providers to restrict the search to.
superbridge routes \
  --from-chain-key eth \
  --to-chain-key base \
  --from-token 0x0000000000000000000000000000000000000000 \
  --to-token   0x0000000000000000000000000000000000000000 \
  --amount 0.01

Or pass an entire request as JSON:

superbridge routes --body @route-request.json

See the Routes API reference for the full request schema.

activity

Fetch bridge activity (history). All filters are optional; without any, you'll get the most recent items.

FlagDescription
--tx-hashFilter by initiating transaction hash.
--addressFilter by sender or recipient address.
--statuspending or done (default: all).
--typemainnets or testnets (default: all).
--page-sizeMax 30.
--from-chain-*, --to-chain-*Chain filters (key / id / uid).
superbridge activity --tx-hash 0xabc...
superbridge activity --address 0xYourAddress --status pending

step

Find a ready step for an in-flight bridge, build its transaction, walk through signing/submission, and poll until the step status changes. Used during long-running flows where the user has to sign a follow-up transaction (for example, a Prove or Finalise step on an OP Stack rollup).

FlagDescription
--tx-hashInitiating transaction hash.
--actionRouteAction — e.g. Approve, Initiate, Prove, Finalise, Refund.
--yesSkip the confirmation prompt.
superbridge step \
  --tx-hash 0xabc... \
  --action Prove

In most cases you should let execute handle follow-up steps for you — see below.

execute

Quote a bridge interactively, pick a provider, and run it end-to-end: any required revoke / approval / gas-token-approval transactions, the initiating transaction (or a gasless intent), then activity polling with automatic step dispatch until the bridge is complete.

This command needs a private key for the from-chain's VM. Sender and recipient are derived from your wallet — pass --recipient to send somewhere else.

FlagDescription
--from-chain-key / --from-chain-id / --from-chain-uidSource chain. Required.
--to-chain-key / --to-chain-id / --to-chain-uidDestination chain. Required.
--from-token / --to-tokenToken addresses (0x000...0 for native). Required.
--amountAmount in human units (e.g. 0.01 for 0.01 ETH or USDC). The CLI scales by the from-token's decimals. Required.
--slippageSlippage as a decimal (e.g. 0.005). Default 0.005.
--recipientOverride the recipient address (defaults to your wallet on the to-chain).
--providerPre-select a provider by id or name, skipping the picker.
--yesSkip the confirmation prompt.
--no-waitSubmit the initiating transaction and exit without polling.
--evm-private-key / --evm-private-key-fileEVM signing key (or EVM_PRIVATE_KEY).
--svm-private-key / --svm-private-key-fileSVM signing key (or SVM_PRIVATE_KEY).
--stark-private-key / --stark-private-key-fileStarknet signing key (or STARK_PRIVATE_KEY).
--stark-account-addressStarknet account contract address (or STARK_ACCOUNT_ADDRESS).
export EVM_PRIVATE_KEY=0x...

superbridge execute \
  --from-chain-key eth --to-chain-key base \
  --from-token 0x0000000000000000000000000000000000000000 \
  --to-token   0x0000000000000000000000000000000000000000 \
  --amount 0.01

The CLI fetches quotes, prompts you to choose a provider, confirms the action, then logs progress to stderr (› evm tx sent on Ethereum: 0x...) until the bridge is complete.

For non-interactive use (CI, scripts), pass --provider <id> and --yes.

index-transaction and submit-gasless are intentionally not exposed as subcommands — they're called automatically by execute and aren't useful in isolation.