Eden AI vs OpenAI API

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.

OpenAI API 75

Status page at status.openai.com with component history (20). Two API-wide majors in the 90 days to 1 November, elevated errors across ChatGPT, Codex and the API (the Agents API included) on 29 September, with Chat Completions, Responses, Batch, Realtime, Embeddings, Images, Files and the other API components degraded from 17:52 to 23:14 UTC, and elevated error rates across API models on 17 September, with eleven components degraded from 20:20 to 21:20 UTC. Two majors give 5 of 30. The 25 July incident is now outside the window. The 29 September write-up, posted on 6 October, traces it to a feature rollout that exhausted shared network connection capacity. Every other incident since 3 August that lists an API component is partial or under an hour, so minor. Degraded performance across ChatGPT, Codex and the APIs on 21 October listed every API component but ran 22 minutes (02:26 to 02:48 UTC). Single-model incidents were GPT-5.6 Sol errors on 11 September (09:08 to 11:21 UTC), gpt-5.6-luna errors on 21 October (70 minutes) and GPT-6.1 Sol degraded performance on Batch, Chat Completions and Responses on 27 October (78 minutes). Partial incidents were latency for some Responses requests on the US endpoint on 31 August and 1 September, image generation where some requests failed on 8 September, latency for some Responses and Chat Completions requests on 30 September, large-PDF errors in Responses and an Agents API computer use incident on 6 October, Responses errors for users in India, Japan and Korea on 22 October and errors on some GPT Image 2 edit requests on 30 October (14:35 to 18:36 UTC). Image model incidents on 16 September and 14 October and file download errors on 19 October each ran about 40 minutes. FedRAMP errors for Astra and Sol on 21 October and authentication errors near Illinois on 20 October list no API component. Rate limits published per tier and model family with rate-limit headers (15). 429 guidance, re-read on 1 November, covers Retry-After as a minimum wait, backoff with jitter when it's missing, a gradual ramp, and splits slow_down (429) from server_is_overloaded (503) (15). Scale Tier carries a 99.9% uptime SLA, through sales, per the 1 October check, not re-read on 1 November (10). Responses and Chat Completions are GA (10). 20 + 5 + 15 + 15 + 10 + 10 = 75.

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.

OpenAI API 90

Closed service with clear terms, SDKs Apache-2.0 (15). The data-controls guide, re-read on 1 November, gives retention periods per endpoint, the training default and the ZDR route. The DPA, effective 1 January 2026, commits to return or deletion of customer data on termination, 30 days to object to a new subprocessor, and SCCs with the UK Addendum for transfers, and nothing in it conflicts with the guide, per the 4 October check, not re-read on 1 November (30). Deprecations page with announcement and shutdown dates, and GET /v1/models returns each model's shutdown_date (20). The subprocessor list, updated 9 July 2026, names its third-party subprocessors and OpenAI affiliates with the processing countries for each and a form to get notice of new ones, and data residency regions are listed, per the 4 October check, not re-read on 1 November (20).

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.

OpenAI API 87

Model reading. GPT-6 Rosalind, a life-sciences model for approved organisations, launched on 30 October, after GPT-6.1 Terra on 26 October and the Decisions API GA on 22 October (30). Published minimum notice of 6 months for GA models, 3 months for specialised variants, as little as 2 weeks for previews. On 14 October GPT-4o (gpt-4o-2024-08-06, gpt-4o-2024-11-20), GPT-4o mini, GPT-4.1 and GPT-4.1 mini were given a shutdown date of 14 January 2027, 92 days, with no safety or compliance reason stated. These are GA models, so the page's own 6-month minimum wasn't kept, as with gpt-5.4-cyber's 20 days in September. 8 of 12, the award for a minimum of two to three months in practice. Five shutdown dates in the 90 days to 1 November, the Assistants API on 26 August (announced in August 2025), gpt-5.2-chat-latest and gpt-5.3-chat-latest on 10 August (announced 8 May), gpt-3.5-turbo-instruct, babbage-002, davinci-002 and gpt-3.5-turbo-1106 on 28 September (announced 26 September 2025, missed in the 27 October count), gpt-5.4-cyber on 1 October and the legacy snapshots on 23 October (announced 22 April). Sora 2 and the Videos API (24 September) are scored on the openai-sora listing. Four of the five kept the published notice, so 4 of 8 as before, as amazon-bedrock has for four dates after full notice. Dated changelog several times a month and a help centre (15 of 15). openai-python had 215 open issues per the 1 October check, replies not sampled (5 of 10). Current official SDKs, openai 3.42.0 on PyPI (31 October) and npm openai 7.47.0 (15). Supported runtimes stated, Python 3.10 or later and Node 22 or later, the npm package's engines re-read on 1 November (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.

OpenAI API 98

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool use with parallel calls and forced tool choice, 18 of 20 because GPT-6 Astra, GPT-6.1 Sol and GPT-6.1 Terra call tools only through the Responses API (18). Strict structured outputs (15). Automatic prompt caching with cached input at 0.1x on Astra and Luna ($0.01 per million on Luna) and 0.05x on GPT-6.1 Sol ($0.10) and GPT-6.1 Terra ($0.05), and a 12-hour cache lifetime in the Responses API since 20 October (15). 1.05M context on Astra, GPT-6.1 Sol, GPT-6.1 Terra and Luna (15). Batch at half price (10). Official SDKs in Python, JavaScript and more (10). Documented error codes with retry guidance (15).

Eden AI 81

Router, scored on the API lines. OpenAPI 3.1 document for v3 (version 3.0.0, 46 paths) at api.edenai.run/v3/docs/openapi.json, plus a management API spec (25). llms.txt on the site and in the docs, llms-full.txt and Markdown pages (10). llms.txt states when to use Eden AI and when not to, and the docs separate chat models from expert models (17). Requests follow the OpenAI shape, and expert-model tools on the MCP server carry JSON Schema inputs (12). Examples throughout, but the spec documents only 200, 201, 202, 302 and 422, while llms.txt names 401 and 451 for region refusals (10). Versioned /v3 path, but no public changelog was found (7). 25+10+17+12+10+7 = 81.

OpenAI API 100

Official OpenAPI document (openapi.yaml and openapi.json) in the openai/openai-openapi repository, whose openapi.yaml (version 2.3.0, updated 31 October) lists gpt-6.1-terra (25). llms.txt index with per-product files, and every docs page has a Markdown twin at .md (10). The reference documents each parameter, and model pages say which model fits which job (20). Structured outputs with strict: true on schemas and function tools (15). Error codes guide with types and recovery advice, now with a 400 service_tier error for tiers a project doesn't allow (15). Dated model snapshots and a dated changelog, last entry 30 October (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.

OpenAI API 100

Model reading. Project keys with All, Restricted (per-endpoint None, Read or Write) and Read Only permissions, service accounts, and mutual TLS with X.509 workload identity GA since 26 August, per the 1 October check. The changelog adds project key expiry dates on 10 September, key-creation controls on 15 September and, on 21 October, organisation and project settings that limit which service tiers a project may use (30). API data not used for training unless the customer opts in, since 1 March 2023 (20). Abuse-monitoring logs kept up to 30 days, and Zero Data Retention or Modified Abuse Monitoring by approval. The data-controls guide re-read on 1 November lists Chat Completions, Responses, Decisions and ten other endpoints as ZDR-eligible; /v1/agents, Conversations, Files and vector stores aren't (15). Usage and Costs filter by API key since 4 August, with Admin APIs to match, and audit logs for enterprise (15). SOC 2 Type 2, ISO 27001, 27017, 27018, 27701 and 42001 per the 1 October check, not re-read on 1 November, a Bugcrowd bug bounty and a coordinated disclosure policy, both linked from a signed security.txt. That security.txt had no Expires field on 27 October, which RFC 9116 requires, so the disclosure policy carries this line. It wasn't re-read on 1 November (20).