BlockRun.AI vs Router.com (Ramp Router)

BlockRun.AI

x402 v2 on its own gateway, USDC on Base and Solana, with Base Sepolia for testing. The status page shows live checks only and keeps no incident history.

Router.com (Ramp Router)

Detailed Markdown docs with typed error codes, per-model capability data and routing an agent can set per request. No OpenAPI document, status page, changelog or published rate limits were found. Signup needs a US business email in a browser, and Ramp records prompts and outputs for a year by default unless switched off.

BlockRun.AI

1. Fund a dedicated wallet with a small USDC balance. The balance is the spending cap
2. Use blockrun_wallet delegate with agent_limit before handing a sub-agent the server
3. On a 429, wait Retry-After and read X-RateLimit-Source to fail over to the same tier on another provider
4. Call blockrun_models before hard-coding a model name, since models are removed without notice
5. Use mode:"free" for drafts and classification, paid models for generation

Router.com (Ramp Router)

1. Switch off content recording in Settings before sending private data. It is on by default and keeps prompts and outputs for a year
2. Read model ids from GET /v1/models at runtime. Ids are account-specific, an unknown one is a 404, and Gemini ids need your own Google key
3. Use POST /v1/responses with a models list for fallbacks. Router stops falling back once a stream has started
4. Set fallback_timeout and provider_timeout, or allow_flex_tier: false, when latency matters. Flex routing is on by default
5. Treat both 401 invalid_api_key and 401 api_key_deactivated as a possibly locked key, and stop retrying on 402