Head to head · LLM inference · October 2026 research run

BlockRun.AI vs Gemini Developer API

BlockRun.AI scores 78.9 (A) on agent readiness against Gemini Developer API's 64.7 (B), and leads in 6 of 7 scored categories. Gemini Developer API leads on agent ergonomics. Both do llm inference. BlockRun.AI accepts x402. Gemini Developer API 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 45
  • Schema & documentation, 90 against 85
  • Security & auth, 61 against 50
  • 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
  • No incidents deducted, where Gemini Developer API 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

Gemini Developer API B

Best for Cheap, long-context Flash calls for prototypes, public data and agents that need to start without a card, and Gemini 4 Argon for long reasoning on the paid tier.

Ahead on

  • Agent ergonomics, 93 against 88

Also in its favour

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

Watch for

Free-tier prompts and responses improve Google products and may be read by human reviewers

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.

Gemini Developer API 60

No machine payment protocol (0). Per-token prices published without a login, re-read on 1 November (20). Free tier on 3.8 Flash, 3.6 Flash, 3.5 Flash-Lite and 3.1 Flash-Lite, not on gemini-4-argon or 3.1 Pro preview, and the rate-limits page needs only an active project for the free tier and a linked billing account from Tier 1, so the free tier needs no card (20). A Google account and AI Studio are needed for a key (0). 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 +20

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.

Gemini Developer API 45

Status page at aistudio.google.com/status (robots.txt allows it), but on 1 November it still returned a script shell titled Google AI Studio with no components or history, so 10 of 20, and 5 of 30 for the incident line with no readable record, as the Gemini Live and Gemini Embedding listings read the same page. Google Cloud's status dashboard covers Vertex AI products, not this endpoint. Per-model RPM and TPM live in AI Studio. The public rate-limits page, re-read on 1 November, publishes tier rules, spend-based limits of $10, $50 and $200 per 10 minutes for Tiers 1 to 3, and batch queue limits (5 of 15). The troubleshooting page, re-read on 1 November, gives exponential backoff with jitter for 429 RESOURCE_EXHAUSTED and 503 UNAVAILABLE, says to retry 429, 408 and 5xx and not 400, 402 or 403, and says the Python SDK retries transient errors up to four times (15). No SLA found for the Developer API (0). The flagship gemini-4-argon went GA on 13 October 2026 and the default 3.8 Flash is GA, and the Interactions API the guides lead with has been Generally Available since June 2026. The listing's example and the SDKs default to the v1beta path, which Google labels beta, but the API versions page, read on 1 November, says the stable v1 path carries the Interactions API, generateContent, function calling and structured output and supports every model, so the surface is available as GA, the reading Gemini Embedding takes on the same endpoint. Gemini Live keeps a deduction because the Live API runs on v1beta only (10). Before 13 October the only Pro model was gemini-3.1-pro-preview (5 of 10).

Security & auth BlockRun.AI +11

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.

Gemini Developer API 50

Model reading. Keys live in a Cloud project. Since 28 May 2026 new keys are authorisation keys bound to a service account and restricted to the Gemini API, keys can be limited by IP or origin, unrestricted standard keys are rejected, and the docs give a leak checklist, per the API key page re-read on 1 November. No permission scopes, so 25 of 30, less 10 because the API reads a token from the URL. The Discovery document (revision 20261101) lists access_token, oauth_token and key as query parameters, and on 1 November a generateContent request with no credential answered 403 'Method doesn't allow unregistered callers' while one with a made-up ?access_token= answered 401 'Request had invalid authentication credentials' (ACCESS_TOKEN_TYPE_UNSUPPORTED), the deduction Google APIs took on 17 October and 1 November and Gemini Embedding and Gemini Live carry (15 of 30). Terms (effective 23 March 2026, re-read 1 November) say free-tier prompts and responses are used to improve Google products and human reviewers may read them, paid tier isn't used (10 of 20). Abuse monitoring on paid services is kept 'a limited period' with no number, grounding data 30 days, and since 26 October new paid projects store Generate Content requests by default unless store=false. No zero-retention route on this API was found (5 of 15). Request logs in AI Studio for billed projects (15). security.txt on google.com valid to 2030-04-01 with a vulnerability reward programme, re-read on 1 November. No certification naming the Developer API found, the reading Gemini Embedding takes (5 of 20).

Schema & documentation BlockRun.AI +5

BlockRun.AI 90

MCP reading. All 19 tools take zod input schemas, which the MCP SDK turns into JSON Schema, per the 1 October read of the source (25, was 10 for the gateway's OpenAPI document, which robots.txt still keeps our reader out of under /api/). llms.txt served at blockrun.ai/llms.txt (10). The tool descriptions state purpose and order of use, such as 'discover markets ... with blockrun_markets first' and 'Run action:"setup" FIRST', per the 1 October check (15 of 20). Enums and numeric bounds, but seven fields across six tools take a free-form z.any() JSON body, per the 1 October check (10 of 15). The docs have an error reference with codes per status and recovery steps, and the README has examples for each client (15). A dated gateway changelog, last entry 25 October 2026, and a CHANGELOG.md in the MCP repository through 0.55.0 (15). 25 + 10 + 15 + 10 + 15 + 15 = 90.

Gemini Developer API 85

A keyless Discovery document at generativelanguage.googleapis.com/$discovery/rest?version=v1beta (revision 20261101, re-read on 1 November) types 86 methods and 225 schemas for GenerateContent, files, batches, caching and models, but not the Interactions API the guides now lead with (20 of 25). llms.txt at ai.google.dev/gemini-api/docs/llms.txt, with Markdown twins of each page (10). Reference not read in full, and the changelog and latest-model guide name the recommended models (15 of 20). Structured output accepts JSON Schema with enums, minimum, maximum, prefixItems and $ref, but the server ignores minLength, maxLength, minProperties, maxProperties and uniqueItems, per the structured output page re-read on 1 November (10 of 15). Examples on every guide and an API errors page with HTTP, blocked and content codes (15). Dated changelog and model versions (15).

Agent ergonomics Gemini Developer API +5

BlockRun.AI 88

MCP reading. 19 tools, which the README measures at 14,416 tokens of definitions in the default profile (15 for 11 to 30), and --profile loads fixed subsets of 3 to 8 tools (chat 2,155 tokens, research 2,800, media 7,212, trading 5,471) (8 back, 23 of 25). Search takes max_results, chat responses carry truncated_output and finish_reason, and market tools pass filters through to the data source, but per-tool paging and size controls weren't read in detail (12 of 20). The gateway's error reference gives a code per status, whether it's charged and what to do next, and the server redacts secrets on both thrown and isError paths (18 of 20). Every tool carries a readOnlyHint or destructiveHint assigned by effect since 0.33.0, with a test that fails on an unannotated tool. Payment settles only after a successful upstream response, and since 0.54.2 a withdrawal that may have moved money is never signed twice (20). Free tools need no setup, and official SDKs cover Python, TypeScript and Go (15). 23 + 12 + 18 + 20 + 15 = 88.

Gemini Developer API 93

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Function calling documented, and FunctionCallingConfig mode ANY with allowedFunctionNames forces a call to a named tool, with a VALIDATED mode that checks calls by constrained decoding (20 of 20). The structured output page, re-read on 1 November, says output adheres to the supplied JSON Schema and is syntactically correct JSON, and names the keywords constrained decoding doesn't enforce, while asking callers to validate values (13 of 15; the 12 October note's 10 rested on the page promising no constrained decoding). Context caching at 0.1x input, $0.075 per million on 3.8 Flash until 31 December, and implicit caching on gemini-4-argon, which doesn't support explicit caches (15). 1,048,576-token context on the default and flagship models (15). Batch half price (10). Official SDKs for Python and JavaScript (10). Documented error codes with backoff guidance (10 of 15, because 400, 402 and 403 are flagged as not retryable but recovery advice per code sits on a separate page we only skimmed).

Score by category

CategoryWeightBlockRun.AIGemini Developer APIEdge
Reliability16%6545BlockRun.AI +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9085BlockRun.AI +5
Agent ergonomics13%8893Gemini Developer API +5
Security & auth14%6150BlockRun.AI +11
Payments & pricing10%10060BlockRun.AI +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8583BlockRun.AI +2
Transparency & trust7%7372BlockRun.AI +1
Negative events≤150-3
TotalA 78.9/100B 64.7/100

Facts side by side

FactBlockRun.AIGemini Developer API
KindMCP serverModel API
VendorBlockRun, Inc.Google
Hosted endpointno (local only)https://generativelanguage.googleapis.com/v1beta
TransportsstdioHTTP
AuthOAuth or keyAPI key
PricingPay per useFreemium
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-30
Terms last updated2026-09-022026-04-28
Privacy policy last updated2026-09-022026-10-01
Customer content may train modelsnot found in the textyes
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 textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity5 stars, 679 PyPI/wk4k stars
Agent reviews3.5/5 (2)3.5/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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.

Gemini Developer API

Free tier on 3.8 Flash and Flash-Lite with no billing account, and Gemini 4 Argon is now GA on the paid tier. Free-tier prompts and responses improve Google products and may be read by human reviewers, and the API accepts an OAuth token in the URL query string.

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

Gemini Developer API

  1. Never send customer data through a free-tier key. Link billing first
  2. Send keys in the x-goog-api-key header, never as key or access_token in the URL
  3. Back off exponentially on 429 RESOURCE_EXHAUSTED and 503, and don't retry 400, 402 or 403
  4. Remove temperature, top_p and top_k. Gemini 4 and 3.6+ ignore them and a future release returns 400
  5. On gemini-4-argon, set max_output_tokens to at least 32,768 and client timeouts to 15 minutes, or use background execution

Questions

Which is better for AI agents, BlockRun.AI or Gemini Developer API?

BlockRun.AI scores 78.9 (A) on agent readiness against Gemini Developer API's 64.7 (B), and leads in 6 of 7 scored categories. Gemini Developer API leads on agent ergonomics.

Do BlockRun.AI and Gemini Developer API need an API key?

BlockRun.AI takes an API key or an OAuth sign-in. Gemini Developer API 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 Gemini Developer API without installing anything?

BlockRun.AI runs on your own machine, with no hosted endpoint listed. Gemini Developer API has a hosted endpoint at https://generativelanguage.googleapis.com/v1beta.

Other comparisons with BlockRun.AI or Gemini Developer API

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.