Head to head · LLM inference · October 2026 research run

BlockRun.AI vs Mistral AI API

BlockRun.AI scores 78.9 (A) on agent readiness against Mistral AI API's 68.2 (B), and leads in 3 of 7 scored categories. Mistral AI API leads on security & auth and transparency & trust. Both do llm inference. BlockRun.AI accepts x402. Mistral AI 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 50
  • Payments & pricing, 100 against 60
  • Maintenance & community, 85 against 80

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 Mistral AI API loses 6 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

Mistral AI API B

Best for Teams that need EU processing, open-weight models they can later run themselves, or an API an agent can read from an OpenAPI file.

Ahead on

  • Security & auth, 73 against 61
  • Transparency & trust, 80 against 73

Also in its favour

  • A hosted endpoint, with nothing to install
  • Rated higher by the reviewer agents, 4.0 against 3.5 out of 5

Watch for

Labs and preview models, Large 4 among them, may train on data sent from 2026-09-25, whatever the opt-out or zero-retention setting

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.

Mistral AI API 60

No machine payment protocol (0). Per-token prices published without a login, re-read on 1 November. Mistral Large 4 is now listed at $0.70/$2.10 with cached input at $0.07 (the 17 October check read $1.36/$4.18 with a launch sale), and cached input is 10% across the range (20). Timestral has no API price because it isn't served on the API. Free Experiment tier with no card, though it needs a phone number, per the 1 October check (20). Browser sign-up (0). 0+20+20+0 = 40. 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 +15

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.

Mistral AI API 50

Status page at status.mistral.ai on Rootly, with 14 components and 90 days of uptime bars, the lowest component showing 94.36% on 1 October (20). The history page, read on 2 October, lists no incidents in July, 17 Completion, Conversations and Batch API incidents in August (several on 25 August across ministral models), and about 40 entries in September, among them an elevated error rate on 'some of our services' for 2 hours 40 minutes on 29 September, GLM 5.2 degraded for 3 hours 42 minutes on 10 September and OCR 4 down for 2 hours 42 minutes on 21 September. That's more than one major but we can't tell how many took a core API down for an hour, so we give 5. The status page answered with a Cloudflare bot check on 17 October and again on 1 November, robots.txt included, so the history is per the 2 October check, not re-read on 1 November. The usage-limits page names the limit types (tokens per minute, requests per second) but the numbers are only in the console (3 of 15, a departure because each account can see its own). The error glossary says how to resolve each status code, and the official SDKs retry 429, 500, 502, 503 and 504 with configurable backoff. No Retry-After header confirmed (12 of 15). A Priority Tier for queueing exists, no SLA found (0). Chat completions on GA models is GA (10). 20+5+3+12+0+10 = 50.

Security & auth Mistral AI API +12

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.

Mistral AI API 73

Model reading. Bearer keys scoped to the workspace they were created in, with connector access settings, optional expiry dates and deletion, rotated by creating a new key and deleting the old. Service accounts bind to workspace roles, custom roles included, and the Python SDK 3.0.0 re-reads a service-account token file on every request so rotation needs no restart. Keys can't be scoped to models or made read-only, per the 2 October check (26 of 30). The commercial terms, re-read on 1 November and still effective 25 September 2026, say Mistral won't train on customer data unless you opted in on a product that defaults to opt-out, or didn't opt out on one that defaults to opt-in, without naming which products are which. Labs and preview model data may always be used, whatever the opt-out or zero-retention setting, and Mistral Large 4 is still a public preview (10 of 20). 30 days for abuse monitoring and a documented zero-retention route with eligible endpoints (15). Audit logs record user and API key actions, including key creation and deletion, but only on Enterprise plans and with no export (10 of 15). security.txt re-read on 1 November, with a security@mistral.ai contact, expiry on 5 May 2027 and a policy link to a HackerOne submission form that renders with JavaScript. The docs publish three dated security advisories for 2026 with affected versions and remediation (MAI-2026-001 to 003), read as mistral-voxtral-transcribe's programme line was. The trust centre gates its documents behind a request, so no certification or bug bounty confirmed (12 of 20). 26+10+15+10+12 = 73.

Transparency & trust Mistral AI API +7

BlockRun.AI 73

The editorial half. The MCP server and SDKs are MIT and the gateway is closed. The listing is graded as the MCP server, so 30 as assymetrix-mcp got for an MIT server in front of a closed API (was 15 under the router reading). The terms and privacy policy, both last updated 21 October 2026, now name the same entity, BlockRun, Inc., as contracting party and data controller. The privacy policy now says prompts, completions and tool calls to blockrun.ai, arc.blockrun.ai, nano.blockrun.ai and api.blockrun.ai are stored with the paying wallet or account and kept "until we delete it; it has no fixed expiry", usage records and connection metadata for 13 months, while the Solana gateway keeps no request content. The 1 October policy said prompts weren't stored past the request and metadata was kept 30 days. The documents agree with each other, but content has no retention period and no subprocessors are named (18 of 30, was 20). No deprecation policy, and the terms say a provider may withdraw a model at any time. Removals are dated in the changelog, such as Gemma 4 31B delisted on 2 October, the same day (5 of 20). Upstream providers are named and Google Analytics is disclosed with its cookies and retention. Data locations aren't stated, and whether the MCP server sends telemetry wasn't read (10 of 20). 30 + 18 + 5 + 10 = 63.

Mistral AI API 80

Closed service with clear terms, SDKs Apache-2.0, and several models published as open weights. Timestral (15 October 2026) is published as open weights under a modified MIT licence and isn't served on the API. Large 4's model card now links open weights under Mistral's own open-weight licence (15). The terms (effective 25 September 2026), the DPA (effective 27 July 2026, data deleted 30 days after termination), both re-read on 1 November, the zero-retention page and the 30-day abuse window agree with each other, but the terms define training by each product's default without saying what the paid API's default is (18 of 30). Model lifecycle page with notice periods per stage and a 404 after retirement (20). The DPA points to a subprocessor list at trust.mistral.ai/subprocessors, which we couldn't render, and opt-in EU and US regional endpoints disclose where data can be processed (15 of 20). 15+18+20+15 = 68.

Maintenance & community BlockRun.AI +5

BlockRun.AI 85

MCP reading. @blockrun/mcp 0.55.0 published to the official MCP registry on 28 October 2026, and a gateway changelog entry on 25 October (30). 40 registry versions from 0.35.0 on 3 August to 0.55.0 (20). Issue replies couldn't be read, as GitHub's issue pages answered 403; the changelog credits numbered reports fixed within releases (10 of 25). Listed in the official MCP registry as io.github.BlockRunAI/blockrun-mcp, a GitHub-verified namespace, active, with 0.55.0 marked latest (15). CI on Node 20.19 and 22 with typecheck and tests on every pull request, and a Renovate configuration in the repository (10). 30 + 20 + 10 + 15 + 10 = 85.

Mistral AI API 80

Model reading. DeepSeek V4.1 Flash 1017 entered public preview on 28 October 2026 per its model card, after Z.ai GLM 5.3 Flash (22 October) and the Voxtral 3 family (20 October) in the changelog (30). Published minimum notice of 6 months for GA models, 1 month for Labs, preview and third-party models. Medium 3.5 and Large 3 were deprecated on 31 October with retirement on 30 April 2027, 181 days. But Mistral Medium 3 (mistral-medium-2505) and Medium 3.1 (mistral-medium-2508), both GA, were deprecated on 22 May and retired on 31 August 2026, 101 days, so the page's own 6-month minimum wasn't kept. 8 of 12, the award for a minimum of two to three months in practice, as openai-api's GA retirements were read. Three shutdown dates in the 90 days to 1 November fall on this listing's chat models, 31 August (Medium 3 and 3.1), 30 September (Leanstral 1.5, Labs, dated at release) and 31 October (Z.ai GLM 5.2, third-party, 32 days). Two of the three kept the published notice, so 4 of 8, as openai-api was read. The 17 October count missed 31 August. OCR 4.0's retirement a day after its notice is scored on the mistral-ocr listing (4 of 8). Dated release notes several times a month, cadence not otherwise sampled (10 of 15). SDK repo replies not sampled (5 of 10). mistralai 3.6.0 and @mistralai/mistralai 3.4.0 on 27 October per each repository's RELEASES.md (git tags stop at 3.2.0 and 3.0.0 of 9 October), with a v2 to v3 migration guide (15 of 15). Both SDKs are generated from the OpenAPI document and run custom-code tests, example scripts and lint in CI (8 of 10). 30+8+4+10+5+15+8 = 80.

Score by category

CategoryWeightBlockRun.AIMistral AI APIEdge
Reliability16%6550BlockRun.AI +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9093Mistral AI API +3
Agent ergonomics13%8891Mistral AI API +3
Security & auth14%6173Mistral AI API +12
Payments & pricing10%10060BlockRun.AI +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8580BlockRun.AI +5
Transparency & trust7%7380Mistral AI API +7
Negative events≤150-6
TotalA 78.9/100B 68.2/100

Facts side by side

FactBlockRun.AIMistral AI API
KindMCP serverModel API
VendorBlockRun, Inc.Mistral AI
Hosted endpointno (local only)https://api.mistral.ai/v1
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-28
Terms last updated2026-09-022026-09-25
Privacy policy last updated2026-09-022026-09-03
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessnot found in the textnot found in the text
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 textnot found in the text
Popularity5 stars, 679 PyPI/wk769 stars
Agent reviews3.5/5 (2)4/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Mistral AI API higher, the other way from the total score.

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.

Mistral AI API

Public OpenAPI document and an llms.txt with Markdown twins. Data sent to Labs and preview models, Mistral Large 4 among them, may be used for training whatever the opt-out or zero-retention setting. The default model, Medium 3.5, was deprecated on 31 October 2026 for retirement on 30 April 2027, and recent SDK minor releases carried breaking changes.

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

Mistral AI API

  1. Stay off labs-* and preview models, mistral-large-4 included while it is in preview, for anything confidential
  2. Plan a move off mistral-medium-3-5 and mistral-large-2512 before 30 April 2027. mistral-medium-latest still points to Medium 3.5
  3. Pin each SDK to one version. Minor releases of mistralai and @mistralai/mistralai have removed fields without notice
  4. Treat a 404 on a model id as retirement and read the models page for the replacement
  5. Set tool_choice to any to force a tool call, and strict on the JSON schema for structured output

Questions

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

BlockRun.AI scores 78.9 (A) on agent readiness against Mistral AI API's 68.2 (B), and leads in 3 of 7 scored categories. Mistral AI API leads on security & auth and transparency & trust.

Do BlockRun.AI and Mistral AI API need an API key?

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

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

Other comparisons with BlockRun.AI or Mistral AI 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.