x402 rails

Where a BlockRun call settles — Base, Solana, Arc, Circle Gateway — and how the x402 protocol, its v2 manifest and the directories that index it fit together.

• Amazon Bedrock AgentCore Payments

  AgentCore Payments gives a Bedrock agent a wallet and spending limits; BlockRun is the sell side: the x402 endpoint the payment lands on and the model answer comes from.

• Arc

  BlockRun is a launch partner for Arc, Circle's network: the same routing and pay-per-call API, settling each x402 payment in USDC on Arc at arc.blockrun.ai.

• Solana

  BlockRun's Solana gateway settles each x402 payment in USDC on Solana: the full model catalog, media, search and RPC through one OpenAI-compatible API, no API keys.

• Base

  blockrun.ai settles each x402 payment in USDC on Base: one OpenAI-compatible endpoint for every model, media generation, search and RPC, priced per call, no API keys.

• x402 v2

  BlockRun publishes an x402 v2 manifest listing every payable endpoint with its price and CAIP-2 network, next to the v1 list and an OpenAPI document with an x402 scheme.

• Circle Gateway Nanopayments

  nano.blockrun.ai serves the full BlockRun catalog with Circle Gateway batched USDC nanopayments: per-call x402 pricing, settled in batches on the EVM chains Gateway supports.

• Coinbase x402 Bazaar

  BlockRun's endpoints are registered on x402scan and discoverable via the x402 Bazaar conventions: an OpenAPI document with x402 extensions plus a /.well-known/x402 manifest.