Eden AI vs Meta Model API

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.

Meta Model API 60

No OpenAPI or similar machine-readable contract found. The reference is Markdown pages with schema sections, and /openapi.json paths on dev.meta.ai return 404 (0). llms.txt at dev.meta.ai/llms.txt, and every docs page has a Markdown copy (10). The models page says when to choose Muse Wonder and when Muse Spark, and the tool-calling and structured-output guides state their limits, such as tool_choice only accepting auto and which schema keywords strict allows (16 of 20). JSON Schema tools and output, reasoning_effort an enum from minimal to max, a strict subset that returns 400 when violated, though tool_choice has one value (12 of 15). Curl, Python and TypeScript examples on each page and an error guide covering 400 to 504 with the error envelope, codes and a fix for each (15). Versioned model IDs (muse-spark-1.1 to 1.3, muse-wonder-1.0) and dated launch posts on the developer blog, but no API changelog (7 of 15). 0 + 10 + 16 + 12 + 15 + 7 = 60.

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.

Meta Model API 64

Model reading. Bearer keys per team, named, shown once and revoked by deletion, with rotation advice. No scopes, read-only keys or per-key limits found (20 of 30). The terms say Meta will not use Content submitted to the Standard Services to train Meta Models, and training applies only to the -contributor model IDs a caller picks. Content may still be used to develop and improve safety and security systems (17 of 20). Retention is 'as needed' for the service, the law, flagged violations and safety review, with no period stated. Zero data retention for qualified accounts through sales, with flagged content kept up to 2 years (10 of 15). The usage dashboard shows tokens and requests per day by model, with no per-key or per-call log found (5 of 15). No security.txt on dev.meta.ai. Meta's bug bounty at bugbounty.meta.com is named in the Muse Code SDK's security policy, and a security commitments page describes TLS 1.2 or later, PCI-DSS card handling and an ISMS, with no named certification for the API (12 of 20). 20 + 17 + 10 + 5 + 12 = 64.

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.

Meta Model API 46

Model reading. Muse Wonder launched on 12 October 2026 (30). No deprecation policy or notice period found. All three Muse Spark versions are still served, so no retirement has tested one (0 of 12). Dated launches on the API since 6 August that we read, Muse Image on 25 August, Muse Voice Transcribe on 3 September and Muse Wonder on 12 October (8 of 8). Muse Code leaving beta on 31 August is a separate product and isn't counted. No Model API changelog. A help centre with support tickets, answered 'typically within two business days' by Meta's own account, which we didn't test (8 of 15). No SDK of Meta's own for the API (0 of 15, 0 of 10). 30 + 0 + 8 + 8 + 0 = 46.

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.

Meta Model API 20

No machine payment protocol (0). Per-token prices for Muse Wonder and Muse Spark, and per-image, per-hour and per-frame prices for the other models, published without a login (20). No free API allowance found. Billing needs a card, and Playground requests count towards usage (0). Browser sign-up with email, phone, Facebook, Google or GitHub (0). 0 + 20 + 0 + 0 = 20.

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.

Meta Model API 40

No status page with readable component history. The error guide's dev.meta.ai/status link now opens a Model API Status page, which showed "Status information is unavailable" to our reader on 4 November, its content drawn by script that we don't request, and the documented GET /v1/status reports only the current state (0). No readable incident history (5). Rate limits published per team and per model, 3,000 RPM and 4,000,000 TPM for muse-wonder-1.0, 150 RPM and 3,000,000 TPM for the contributor variants, 600 background submissions a minute (15). 429 and 503 carry Retry-After (60 seconds for service_overloaded and backend_unavailable), with backoff-with-jitter guidance, rate-limit headers on every token response and a documented mid-stream server_shutting_down event to retry, a generation call read as stateless as gemini-api's (15). No SLA found, and the terms let Meta throttle or suspend access without notice (0). Muse Wonder is labelled a preview. Muse Spark 1.3 carries no preview label, but the API opened on 8 July 2026 as a public preview and we found no general-availability notice, so half (5 of 10, the 12 October partial, kept). 0 + 5 + 15 + 15 + 0 + 5 = 40.