BlockRun.AI vs SiliconFlow

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.

SiliconFlow

Per-token prices for every listed model are public, and one key reaches chat, embeddings, reranking, image, video and speech through OpenAI-style and Anthropic-style routes. No status page, SLA, security page or official SDK was found, release notes stop at 11 June 2026, and several model removals are dated the same day as their notice.

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

SiliconFlow

1. Set the OpenAI client's base URL to https://api.siliconflow.com/v1, or the Anthropic client's to https://api.siliconflow.com/, and send the key as a Bearer token
2. Take model ids from the model pages or GET /v1/models, not from the OpenAPI enum or the function calling guide, which list removed models
3. Check the model field of each response. On 11 June 2026 traffic for GLM-5 and Kimi-K2.5 was routed to successor models
4. Use response_format of json_object only where the model page says JSON Mode is supported, and keep max_tokens about 10,000 below the context length
5. Set the Claude Code environment variables by hand. The automated route pipes a script from an Amazon S3 bucket into bash