Head to head · LLM inference · October 2026 research run

BlockRun.AI vs OpenRouter

BlockRun.AI scores 78.9 (A) on agent readiness against OpenRouter's 69.1 (B), and leads in 5 of 7 scored categories. OpenRouter leads on security & auth. Both do llm inference. BlockRun.AI accepts x402. OpenRouter doesn't.

Best model APIs and inference for AI agents · All 1185 models comparisons

Which one, for what

BlockRun.AI A

Best for Agents that must start and pay with no human sign-up, and builders testing x402 against a real inference gateway.

Ahead on

  • Reliability, 65 against 55
  • Payments & pricing, 100 against 60

Also in its favour

  • Agent-ready, a grade of BB or better
  • An agent can pay per call over x402, with no account
  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
  • No incidents deducted, where OpenRouter loses 3 points for them

Watch for

Since 21 October 2026 prompts and completions sent through the Base, Arc and API gateways are stored with no fixed expiry

OpenRouter B

Best for Agents that need many models behind one key, provider failover and a hard price ceiling per request.

Ahead on

  • Security & auth, 67 against 61

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

No machine payment. USDC top-ups go to a prepaid balance

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing BlockRun.AI +40

BlockRun.AI 100

x402 v2 on its own gateway, USDC on Base and Solana, and since MCP 0.55.0 (28 October) on Circle's Arc through arc.blockrun.ai (40). Per-token prices per model published without a login, plus a flat $0.001 fee per wallet call on Base (20). Seven free models per the status page's menu, no card or sign-up, and a wallet costs nothing to create (20). An agent can create its own wallet and pay per request with no human sign-up (20). 40 + 20 + 20 + 20 = 100. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 40 of 40 is 10 of 10, and the other lines' 60 is 90 at 30 each, so 100 is 100.

OpenRouter 60

No machine payment protocol found in the docs index. Credits can be bought in USDC through Coinbase, but calls draw on a prepaid balance (0). Per-token prices published per model without a login (20). 25 or more free models with no card, per the listing (20). Browser sign-up for the first key (0). Management API keys and OAuth PKCE mint keys in code, but only after a person has an account. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Reliability BlockRun.AI +10

BlockRun.AI 65

Read with the local-software lines, as the listing's kind is mcp and the owner runs the server over stdio, though every paid call lands on BlockRun's gateway (the reading assymetrix-mcp and copilot-studio-mcp get). The 1 October check read it as a router. Installs from the official npm package @blockrun/mcp with Node 20.19 or later stated in engines (20). The CI workflow runs typecheck, build and tests on Node 20.19 and 22 on every push and pull request, with a required gate job. Run results weren't readable, as GitHub's pages answered 403 (20 of 25). Open issues couldn't be read. The changelog names numbered reports fixed in releases, such as #176 and #177 in 0.54.3 and 0.54.4 (10 of 25). Semver numbering with breaking changes marked BREAKING in CHANGELOG.md and shipped as minor bumps, as its own entries say (15). Version 0.55.0, pre-1.0 (0). 20 + 20 + 10 + 15 + 0 = 65. For the gateway behind it, blockrun.ai/status still shows live checks of the Base and Solana gateways and says "None recorded on this page yet" under incident history, the terms still say "We do not commit to any particular uptime", and free models are limited to 30 requests a minute and 300 an hour per IP with 429s carrying Retry-After.

OpenRouter 55

Status page at status.openrouter.ai, which rendered only in a browser with its feed and JSON paths answering 403 on 1 and 2 October. On 1 November its robots.txt answered 403 AccessDenied, so the host is treated as blocked and the page was not read (10 of 20, per the 2 October check, and 5 for the incident line, no readable history). The limits page gives 20 requests a minute on free models, 50 a day below $10 of lifetime purchases and 1,000 a day above, no platform cap on paid models, and a key endpoint that reports what's left (15). The errors page says 429, 503 and 402 responses from the in-flight spending budget carry Retry-After, tells clients to honour it, and says the official SDKs already do (15). The pricing page lists 'Contractual SLAs' for Enterprise without publishing terms, which we count as no published SLA (0). The chat completions API is GA (10). Model fallbacks through a models list soften an upstream outage, which this checklist doesn't score.

Security & auth OpenRouter +6

BlockRun.AI 61

MCP and API reading. The credential is a wallet private key, auto-created at ~/.blockrun/.session or passed in an environment variable and optionally mirrored to the OS keychain, and it controls the whole balance. blockrun_wallet can delegate a capped budget to a child agent, and an API-key route backed by account credit exists (20 of 30, as on 1 October). blockrun_polymarket_read gives read-only positions and previews apart from the trading tool, trades need confirm:true with a $25 default order cap, --profile drops whole groups of tools, and BLOCKRUN_CONFIRM_SPEND=on pauses every paid call for approval, though it's off by default (16 of 20). Search, Exa, market and RPC tools return third-party content, and no prompt-injection guidance was found in the README or docs read (5, as knock and suprsend). Every payment settles on-chain and the wallet tool reports balances and spending (10 of 15). security.txt is valid on 1 November, with an email contact, a policy link and an Expires date of 1 November 2027, and SECURITY.md takes private GitHub reports with a 72-hour acknowledgement and a 7-day plan for fund-affecting issues. No bounty or certification found (10). 20 + 16 + 5 + 10 + 10 = 61.

OpenRouter 67

Model reading. Bearer keys with per-key credit limits, Management API keys for creating and rotating keys in code, and OAuth PKCE for user-delegated keys. No permission scopes on keys (25 of 30). OpenRouter doesn't store or use prompts unless you opt in for a 1% discount, but the routing reference, re-read on 1 November 2026, still sets data_collection to 'allow' by default, which admits providers that may store and train on data. An account privacy setting can switch that off, and the docs don't say what a new account starts with (5 of 20). Prompts not stored by default and a per-request zdr filter (15). Request metadata kept for reporting, per-call logs not confirmed (10 of 15). security.txt, read on 1 November 2026, is valid to 12 August 2027 with security@openrouter.ai and a PGP key, and says reports confirmed as high-impact get an invitation to a private HackerOne bug bounty. The private bounty counts as a bounty, as other listings' invitation-only programmes do (activepieces, fireflies, mixpanel). No certification or public advisory was found, so 12, above blockrun-ai's 10 (valid security.txt, no bounty) and below activepieces' 13 (a private bounty and nine public advisories) (12 of 20).

Score by category

CategoryWeightBlockRun.AIOpenRouterEdge
Reliability16%6555BlockRun.AI +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9090even
Agent ergonomics13%8885BlockRun.AI +3
Security & auth14%6167OpenRouter +6
Payments & pricing10%10060BlockRun.AI +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8582BlockRun.AI +3
Transparency & trust7%7372BlockRun.AI +1
Negative events≤150-3
TotalA 78.9/100B 69.1/100

Facts side by side

FactBlockRun.AIOpenRouter
KindMCP serverModel router
VendorBlockRun, Inc.OpenRouter
Hosted endpointno (local only)https://openrouter.ai/api/v1
TransportsstdioHTTP
AuthOAuth or keyAPI key
PricingPay per usePay per use
x402yesno
LicenceMITApache-2.0 (SDKs)
Tools exposed19none
Read-only variant documentedyesno
llms.txtyesyes
MCP registryio.github.BlockRunAI/blockrun-mcpnot listed
Last release2026-10-282026-10-31
Terms last updated2026-09-022026-08-31
Privacy policy last updated2026-09-022026-08-31
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity5 stars, 679 PyPI/wk226 stars
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates BlockRun.AI higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

BlockRun.AI

x402 v2 on its own gateway lets an agent create a wallet and pay per call in USDC on Base, Solana or Arc with no sign-up, and every MCP tool carries a safety annotation. Since 21 October 2026 prompts sent through the Base and Arc gateways are stored with no fixed expiry, and the status page keeps no incident history.

OpenRouter

Public OpenAPI document, llms.txt with Markdown twins, and a changelog generated from the spec on every release, with SDKs in TypeScript and Python tagged on 31 October 2026. Breaking changes ship with migration notes on the day, with no notice period. No machine payment, and USDC top-ups go to a prepaid balance.

Before you call either

BlockRun.AI

  1. Fund a dedicated wallet with a small USDC balance. The balance is the spending cap
  2. Use the Solana gateway when prompts must not be stored. Base and Arc keep request content with no fixed expiry
  3. Start the server with --profile for the job (chat, research, media or trading) to cut the tool definitions
  4. Set BLOCKRUN_CONFIRM_SPEND=on to approve each paid call. It's off by default
  5. Call blockrun_models before hard-coding a model name, since models are removed without notice

OpenRouter

  1. Set provider.data_collection: "deny" or provider.zdr: true when the prompt holds anything private
  2. Pass a models list so a failed provider falls through to the next one
  3. Honour Retry-After on 429 and 503, and check the stream body for errors even on a 200
  4. Set max_price so a routed request can't land on an expensive provider
  5. Free models allow 50 requests a day until $10 of credit has been bought. Check GET /api/v1/key for what's left
  6. On /messages streams, stop at message_stop or an error event. No [DONE] frame is sent since 21 October 2026

Questions

Which is better for AI agents, BlockRun.AI or OpenRouter?

BlockRun.AI scores 78.9 (A) on agent readiness against OpenRouter's 69.1 (B), and leads in 5 of 7 scored categories. OpenRouter leads on security & auth.

Do BlockRun.AI and OpenRouter need an API key?

BlockRun.AI takes an API key or an OAuth sign-in. OpenRouter needs an API key. An agent can also pay BlockRun.AI per call over x402, with no account.

Can an agent call BlockRun.AI and OpenRouter without installing anything?

BlockRun.AI runs on your own machine, with no hosted endpoint listed. OpenRouter has a hosted endpoint at https://openrouter.ai/api/v1.

Other comparisons with BlockRun.AI or OpenRouter

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.