BlockRun.AI vs SambaCloud

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.

SambaCloud

Per-token prices and the model list are readable without a key at /v1/models, and a free tier needs no card. Production models get two to three weeks' notice before removal, 13 model ids left between March and June 2026, and the docs disagree with the live catalogue on MiniMax-M2.7.

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

SambaCloud

1. Call GET https://api.sambanova.ai/v1/models at start-up and use only ids it returns. The docs name models the endpoint no longer lists
2. Read x-ratelimit-remaining-requests and x-ratelimit-remaining-requests-day on every response. The free tier allows 20 requests a day per model
3. Treat 429 queue_full and 503 maintenance as retryable after a delay, and 410 model_deprecated as a signal to change model
4. Validate JSON output yourself. Schema enforcement is best effort and strict: true changes nothing
5. Check max_completion_tokens per model. DeepSeek-V3.1 caps output at 7,168 tokens and Llama 3.3 70B at 3,072