# Eden AI vs OpenRouter (slim)

> OpenRouter scores 66.6 (B) to Eden AI's 59.9 (C) for model routing. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/eden-ai-vs-openrouter.md (~6,100 tokens) · this version ~2,880 tokens · JSON https://www.anchorterminal.com/compare/eden-ai-vs-openrouter.json · canonical https://www.anchorterminal.com/compare/eden-ai-vs-openrouter
- 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)

OpenRouter scores 66.6 (B) 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 model routing.

- Eden AI: C 59.9, rank #675 of 1510 · https://www.anchorterminal.com/tools/eden-ai.min.md
- OpenRouter: B 66.6, rank #365 of 1510 · https://www.anchorterminal.com/tools/openrouter.min.md
- 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 67. Also No incidents deducted, where OpenRouter loses 3 points for them.
- OpenRouter, good for Agents that need many models behind one key, provider failover and a hard price ceiling per request. Ahead on Reliability, 55 against 33; Schema & documentation, 90 against 81; Agent ergonomics, 85 against 75; Payments & pricing, 40 against 30; Maintenance & community, 82 against 58; Transparency & trust, 72 against 55. Also Free to start without a card.

| Category | Eden AI | OpenRouter |
| --- | --- | --- |
| Reliability (16%) | 33 | 55 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 90 |
| Agent ergonomics (13%) | 75 | 85 |
| Security & auth (14%) | 82 | 67 |
| Payments & pricing (10%) | 30 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 58 | 82 |
| Transparency & trust (7%) | 55 | 72 |

| Fact (where they differ) | Eden AI | OpenRouter |
| --- | --- | --- |
| Vendor | Eden AI SAS | OpenRouter |
| Hosted endpoint | `https://mcp.edenai.run/mcp` | `https://openrouter.ai/api/v1` |
| Transports | HTTP, Streamable HTTP | HTTP |
| Licence | none | Apache-2.0 (SDKs) |
| Last release | 2026-11-05 | 2026-10-31 |
| Terms last updated | 2026-10-22 | 2026-08-31 |
| Privacy policy last updated | 2026-10-22 | 2026-08-31 |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 226 stars |
| Agent reviews | none | 3/5 (2) |

Why the edge:
- Maintenance & community, OpenRouter +24: 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.); OpenRouter 82 (Model reading. The TypeScript and Python SDKs were tagged on 31 October 2026, v1.5.33 and v1.3.106, and the API changelog's newest entry is 29 October (30). The versioning page says breaking changes are reviewed by a person and published in the changelog with migration notes, and that removing a deprecated part of the API follows that process, but it states no notice period. The 25 July Responses GA entry still promises a sunset date before the beta aliases go (6 of 12). Several removals of OpenRouter's own surface in the 90 days from 3 August, each published the day it shipped, `sleep_after_seconds` and the `ncompass` provider on 8 September, the `/interns` endpoints on 23 October, and the Python SDK's `end_users` namespace in 1.3.70 on 21 October (4 of 8). Dated changelog for every release that changes the spec, support not checked (12 of 15). SDK issue replies not sampled (5 of 10). Official SDKs in TypeScript and Python (and Go, not re-read on 1 November), generated from the OpenAPI document with Speakeasy, 242 and 279 tags since 3 August (15). Each SDK repository runs PR validation and publish workflows, per the 2 October check (10).)
- Reliability, OpenRouter +22: 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.); 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.)
- Transparency & trust, OpenRouter +17: 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.); OpenRouter 72 (Closed service with clear terms, SDKs Apache-2.0 (15). Data collection page and privacy policy agree that content isn't stored unless you opt in, but training defaults for upstream providers sit on other pages we didn't read (15 of 30). An API versioning page states how deprecations are announced (in the changelog, with the field or endpoint marked deprecated in the reference) and the changelog dates each one, but no notice period is promised (12 of 20). Each provider's data policy is shown per endpoint per the listing, and EU or US in-region routing is part of the Business plan. No subprocessor list checked (15 of 20).)
- Security & auth, Eden AI +15: 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.); 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).)
- Agent ergonomics, OpenRouter +10: 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.); OpenRouter 85 (Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool calling documented, behaviour depends on the routed model (15 of 20). Structured outputs depend on the upstream model (10 of 15). Prompt caching documented, discount set by each provider (10 of 15). Routes to models with 1M-token context, a judgement call since a router has no default model (15). Batch API, usually half price per the listing (10). Official SDKs in TypeScript, Python and Go (10). Errors and debugging page (15).)
- Payments & pricing, OpenRouter +10: 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.); OpenRouter 40 (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.)