# Eden AI vs xAI API (Grok) (slim)

> xAI scores 71.7 (BB) 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/eden-ai-vs-xai-api.md (~6,300 tokens) · this version ~3,080 tokens · JSON https://www.anchorterminal.com/compare/eden-ai-vs-xai-api.json · canonical https://www.anchorterminal.com/compare/eden-ai-vs-xai-api
- 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)

xAI API (Grok) scores 71.7 (BB) on agent readiness against Eden AI's 59.9 (C), and leads in 6 of 7 scored categories. Eden AI leads on payments & pricing. Both do llm inference.

- Eden AI: C 59.9, rank #675 of 1510 · https://www.anchorterminal.com/tools/eden-ai.min.md
- xAI API (Grok): BB 71.7, rank #152 of 1510 · https://www.anchorterminal.com/tools/xai-api.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 Payments & pricing, 30 against 20.
- xAI API (Grok), good for Agents that want a capable model at a low per-token price with built-in web and X search, remote MCP and voice, and teams that need self-serve ZDR or US-only processing. Ahead on Reliability, 55 against 33; Schema & documentation, 88 against 81; Agent ergonomics, 90 against 75; Security & auth, 97 against 82; Maintenance & community, 77 against 58; Transparency & trust, 63 against 55. Also Agent-ready, a grade of BB or better.

| Category | Eden AI | xAI API (Grok) |
| --- | --- | --- |
| Reliability (16%) | 33 | 55 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 88 |
| Agent ergonomics (13%) | 75 | 90 |
| Security & auth (14%) | 82 | 97 |
| Payments & pricing (10%) | 30 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 58 | 77 |
| Transparency & trust (7%) | 55 | 63 |

| Fact (where they differ) | Eden AI | xAI API (Grok) |
| --- | --- | --- |
| Kind | Model router | Model API |
| Vendor | Eden AI SAS | SpaceXSI (xAI) |
| Hosted endpoint | `https://mcp.edenai.run/mcp` | `https://api.x.ai/v1` |
| Transports | HTTP, Streamable HTTP | HTTP |
| Licence | none | Proprietary service under xAI's enterprise terms of service. The Python SDK is Apache-2.0 |
| Last release | 2026-11-05 | 2026-11-02 |
| Terms last updated | 2026-10-22 | 2026-10-27 |
| Privacy policy last updated | 2026-10-22 | 2026-10-27 |
| Customer content may train models | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 597 stars, 912k PyPI/wk |

Why the edge:
- Reliability, xAI API (Grok) +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.); xAI API (Grok) 55 (Status page at status.x.ai with components for the global and US API endpoints, voice, the consumer apps and, since the Cursor merger, Cursor's services, with an RSS feed (20). The feed, read on 6 November, now holds 267 incidents back to 11 August, so the whole 90-day window is readable. On the API components there were high error rates on grok-4.6 and grok-4.5 from 21:57 to 23:28 UTC on 17 August (about 90 minutes) and a models outage on the global and US endpoints from 13:30 to 17:09 UTC on 3 September (about 3 hours 40 minutes), so several majors. A 26-minute datacenter outage across the API on 22 September, voice disruptions of 12 and 28 minutes on 10 September and 6 October, a 63-minute voice and Imagine degradation on 30 October and a 37-second model degradation on 24 October add to the record (0). Rate limits published per model and tier, grok-4.7 at Tier 0 is 150 requests a second and 50M TPM, with the per-second cap derived as RPM divided by 48 (15). The rate-limits page shows exponential backoff on 429, but no Retry-After header or overload guidance was found (10 of 15). No SLA found in the docs or llms.txt (0). The Responses API has been GA since September 2025 and grok-4.7 carries no preview label (10).)
- Maintenance & community, xAI API (Grok) +19: 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.); xAI API (Grok) 77 (Model reading. grok-imagine-image-quality and grok-imagine-image-pro retired on 2 November 2026 as announced in September, Grok Voice 3.0 and custom moderation controls in October, Grok 4.7 on 21 September (30). No minimum notice period found. Retirements come as dated migration guides, retired slugs redirect to a replacement rather than failing, billed at the replacement's price, and grok-voice-2.0 was deprecated in October with no end date (4 of 12). Shutdowns in the last 90 days with dates given in advance, `grok-voice-transcribe-1.0` on 2 October and `grok-imagine-image-quality` on 2 November (8 of 8). Release notes several times a month but dated only by month, support by email and a Discord #help channel, not tested. On xai-sdk-python a collaborator commented on 2 of the 16 most recent threads with replies, and most outside pull requests since 23 October are open without a maintainer reply (10 of 15, down from 12). The repository has CI, release and version-bump workflows (5 of 10). One current first-party SDK, `xai-sdk` 1.21.0 tagged on 23 October, Python only (10 of 15). Supported runtimes stated, Python 3.10 or later (10).)
- Agent ergonomics, xAI API (Grok) +15: 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.); xAI API (Grok) 90 (Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Function calling with parallel calls on by default and `tool_choice` of auto, required, none or a named function (20). Guaranteed structured outputs (15). Automatic prompt caching, cached input at 0.25x on grok-4.7 ($0.50 per million) and 0.16x on grok-4.3 (15). 500,000-token context on grok-4.7 and 1,000,000 on grok-4.3, 13 of 15 for the default model's 500K. The Batch API is now 20% off on grok-4.7, 4.6 and 4.5 as well as the older models, with batch requests outside the rate limits (10 of 10, up from 5 on 6 October). One first-party SDK, `xai-sdk` for Python, with the OpenAI SDKs and Vercel's AI SDK documented as alternatives (5 of 10). Status codes documented with fixes, no Retry-After header found (12 of 15).)
- Security & auth, xAI API (Grok) +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.); xAI API (Grok) 97 (Model reading. Team API keys with ACLs per endpoint and per model, QPM and TPM caps, expiry, and create, rotate, disable and delete through the Management API, plus documented mTLS. GitHub secret scanning disables leaked keys and emails the owner (30). The security FAQ says SpaceXSI never trains on API inputs or outputs without explicit permission (20). Requests and responses are kept 30 days for abuse auditing, then deleted, and team admins can switch on zero data retention themselves, confirmed by an `x-zero-data-retention` header on every response (15). Console audit log and a Management API audit-events endpoint, plus optional per-key request logging (15). security.txt valid to 2027-06-29 with a HackerOne bug bounty and a separate safety contact for prompt-injection issues. SOC 2 Type 2 is claimed in the security FAQ with the reports behind an NDA in the trust centre, so 17 of 20. Remote MCP doesn't support `require_approval`, which the model checklist doesn't score but reviewers should see. New in October, a `guidelines` array lets the caller make the model decline nsfw, violence or profanity content, which the checklist doesn't score.)
- Payments & pricing, Eden AI +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.); xAI API (Grok) 20 (No x402, MPP or L402 (0). Per-token and per-call prices published without a login on docs.x.ai/developers/pricing (20). No free tier found for the text API, and the quickstart says to load the account with credits (0). Sign-up is in the browser at console.x.ai. The Management API can create keys and top up prepaid credit, but only with a management key made by a person in the console, so no line credit (0).)
- Transparency & trust, xAI API (Grok) +8: 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.); xAI API (Grok) 63 (Closed service under xAI's enterprise terms, with the Python SDK under Apache-2.0 (15). The docs agree with each other on no training, 30-day abuse retention, 30-day storage of stateful responses and the ZDR route, but the privacy policy, enterprise terms and DPA at x.ai/legal answered a Cloudflare block page on 6 October and again on 6 November, so they couldn't be compared (15 of 30). Dated migration guides and redirect tables for each retirement, but no written deprecation policy, and Chat Completions, Anthropic compatibility and grok-voice-2.0 are labelled deprecated with no date (12 of 20). The US regional endpoint states what stays in the US, the global endpoint guarantees no region, and no subprocessor list was readable (10 of 20).)