BlockRun.AI vs RouterPlus

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.

RouterPlus

The docs are written for agents, every model price is public, and each response carries its own cost. No terms of service, privacy policy, status page or changelog were found. Signup adds no free credit, and the chat catalogue is Claude and GPT only.

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

RouterPlus

1. Send max_tokens on every request. Without it the balance hold assumes up to 32,768 output tokens and can return insufficient_quota on a small balance
2. Switch on error_type. Retry rate_limit after retry-after, and stop on insufficient_quota, which needs a person to add credit or raise a cap
3. Don't add a retry loop on top of the SDK's. There is no idempotency key, so a retry that reaches a provider is billed again
4. Copy model ids from GET /v1/models or /api/models.json. An unknown id is a 404 and the gateway never substitutes one
5. Use /v1/messages for Claude when you need thinking or server tools, and /v1/chat/completions with response_format only for GPT ids