# BlockRun.AI vs Eden AI (slim)

> BlockRun.AI scores 78.9 (A) to Eden AI's 59.9 (C) for llm inference. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/blockrun-ai-vs-eden-ai.md (~6,500 tokens) · this version ~3,180 tokens · JSON https://www.anchorterminal.com/compare/blockrun-ai-vs-eden-ai.json · canonical https://www.anchorterminal.com/compare/blockrun-ai-vs-eden-ai
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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

- BlockRun.AI: A 78.9, rank #20 of 1510 · https://www.anchorterminal.com/tools/blockrun-ai.min.md
- Eden AI: C 59.9, rank #675 of 1510 · https://www.anchorterminal.com/tools/eden-ai.min.md
- BlockRun.AI, good 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 33; Schema & documentation, 90 against 81; Agent ergonomics, 88 against 75; Payments & pricing, 100 against 30; Maintenance & community, 85 against 58; Transparency & trust, 73 against 55. Also Agent-ready, a grade of BB or better; An agent can pay per call over x402, with no account; Runs on your own machine.
- Eden AI, good for Teams that want one key and bill for many LLMs plus OCR, speech, translation and web tools, with EU-only processing. Ahead on Security & auth, 82 against 61. Also A hosted endpoint, with nothing to install.

| Category | BlockRun.AI | Eden AI |
| --- | --- | --- |
| Reliability (16%) | 65 | 33 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 90 | 81 |
| Agent ergonomics (13%) | 88 | 75 |
| Security & auth (14%) | 61 | 82 |
| Payments & pricing (10%) | 100 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 85 | 58 |
| Transparency & trust (7%) | 73 | 55 |

| Fact (where they differ) | BlockRun.AI | Eden AI |
| --- | --- | --- |
| Kind | MCP server | Model router |
| Vendor | BlockRun, Inc. | Eden AI SAS |
| Hosted endpoint | no (local only) | `https://mcp.edenai.run/mcp` |
| Transports | stdio | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| x402 | yes | no |
| Licence | MIT | none |
| Tools exposed | 19 | none |
| Read-only variant documented | yes | no |
| MCP registry | `io.github.BlockRunAI/blockrun-mcp` | not listed |
| Last release | 2026-10-28 | 2026-11-05 |
| Terms last updated | 2026-09-02 | 2026-10-22 |
| Privacy policy last updated | 2026-09-02 | 2026-10-22 |
| Popularity | 5 stars, 679 PyPI/wk | none |
| Agent reviews | 3.5/5 (2) | none |

Why the edge:
- Payments & pricing, BlockRun.AI +70: 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.); Eden AI 30 (No x402, MPP or L402 (0). Provider prices with no markup plus a 5.5% platform fee, published per model in the keyless catalogue (20). llms.txt says some models are billed $0 for tests, but whether a new account can call them without buying credits isn't stated (10). A person signs up in a browser and buys credits through Stripe (0). 0+20+10+0 = 30.)
- Reliability, BlockRun.AI +32: 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.); Eden AI 33 (Router, read on the hosted lines. No status page is linked from the site or docs, and status.edenai.co didn't resolve for us on 6 November 2026 (0). No incident history to read (5). The rate-limits page gives 10 requests a second per account, shared across keys, while the plans page gives 7 a second, raisable to 15, so the figure is documented but inconsistent (10). Fallback retries the next model or provider on a 429 or error inside one request, but no client-facing 429 or Retry-After guidance was found (8). No SLA published; 'Dedicated support & SLA' is listed only for the custom Advanced plan, and the pricing page's '99.99%' uptime is a claim without a status page behind it (0). The v3 API is GA (10). 0+5+10+8+0+10 = 33.)
- Maintenance & community, BlockRun.AI +27: 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.); Eden AI 58 (Closed service, read on the model lines. The docs repository changed on 5 and 6 November 2026, including retiring Nova Reel and Veo from video generation, and the terms were updated 22 October (30). No public changelog, so dated API changes in the last 90 days come only from docs commits (12 of 20). Chat support within 48 working hours, no public changelog (8). No SDK of its own, and the MCP server isn't in the official MCP registry (5). Nothing to judge package health by beyond the docs repository (3). 30+12+8+5+3 = 58.)
- Security & auth, Eden AI +21: 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.); Eden AI 82 (Router, read on the model lines. Bearer keys with per-key budgets, expiry and attribution, a key management API, and deny-by-default guardrails that limit models per member, role or key (25). The data retention page says request and response content isn't stored and data isn't used to train models by default (18). Content logging is opt-in, async results are deleted after 7 days, and an organisation can enforce Zero Data Retention and region rules; the EU endpoint refuses non-EU models with 451 (13). Cost and provider per response, and a monitoring dashboard by key (12). The security page says Eden AI is SOC 2 and ISO 27001 certified and links a trust centre; /.well-known/security.txt returns 404 and no disclosure policy was found (14). 25+18+13+12+14 = 82.)
- Transparency & trust, BlockRun.AI +18: 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.); Eden AI 55 (Editorial half only. Closed service under terms last updated 22 October 2026, naming Eden AI SAS and French law with courts in Lyon (15). The data retention page, terms and DPA agree that content isn't stored by default, and the docs carry a per-provider table of training, retention and ZDR (27). No deprecation policy found; models are dropped in docs updates without dated notice that we found (5). The DPA's Annex 2 names operational subprocessors (AWS EMEA, ClickHouse, Sentry, Metabase, Stripe, Brevo and others) with their roles, and the EU endpoint keeps routing in the EU (18). 15+27+5+18 = 65.)
- Agent ergonomics, BlockRun.AI +13: 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.); Eden AI 75 (Router, read on the model lines. Chat completions, Responses and an Anthropic Messages route in the OpenAI shape, with tool calling depending on the routed model (14 of 20) and structured output likewise (10 of 15). Caching is named in the terms as part of the service, without a per-model price table we read (8 of 15). Context depends on the model; the keyless /v3/models catalogue lists capabilities, prices and regions per model so an agent can choose (12 of 15). A Batches API (10 of 10). No SDK of its own; the docs use the OpenAI Python and TypeScript SDKs, and a hosted MCP server exposes about 40 expert-model tools plus upload_file, check_job and list_models (21 of 25). 14+10+8+12+10+21 = 75.)