What Is Eden AI and What Does Its AI Gateway Do?

Eden AI is a European AI gateway that gives developers one OpenAI-compatible API to around 1,000 models from 50+ providers, while giving finance and admins a single console for cost tracking and governance. It fits teams that already call multiple model providers (or plan to) and want one integration point, per-team budgets, and EU data controls without building that layer themselves. Pricing follows a no-subscription model: provider prices with no markup, plus a 5.5% fee only when you buy credits.

The core idea: one API, many providers

Instead of integrating each provider separately, you send requests in one request shape to Eden AI and it routes them to the underlying model. The platform advertises around 1,000 LLMs and expert models across 50+ providers, including specialized models such as document OCR alongside general chat models.

The practical benefit is integration cost: your application code targets one endpoint and one key, and swapping or adding models doesn't require a new SDK or auth flow. Eden AI describes the API as OpenAI-compatible, so existing OpenAI-style client code is the natural starting point.

Gateway features that change how you operate

Beyond simple proxying, the gateway adds routing and reliability behavior:

• Smart routing — send a request and let the gateway pick a model based on rules, including cost-based routing.
• Fallbacks — if a model fails, the request can be retried on another model. The console example shows fallbacks used 142 times in a 30-day window, with the fallback "billed once."
• Caching — repeated requests can be served from cache, which the platform counts toward savings alongside routing and fallbacks.
• Cost in the response — each request returns its cost, so you can attribute spend programmatically rather than reconciling invoices after the fact.

A concrete scenario: a support product sends a prompt, the primary model is unavailable, and the gateway falls back to an alternate model. The caller gets one answer, finance sees one billed request, and the fallback event is visible in the console.

Cost tracking and governance for teams

The console is built around three questions the platform says most companies can only partly answer: what teams are calling, what it costs, and who decides. Eden AI addresses all three in one dashboard:

Admins can set budgets, roles, and model access per team, and track or cap spend per team, per product, or per end user for products they ship. The dashboard example shows attributed spend at 93%, with the remainder untagged and flagged — a useful signal that tagging discipline matters if you want clean cost attribution.

European hosting and compliance posture

Eden AI positions itself for European procurement: it states it is made in the EU, is SOC 2 and ISO 27001 certified, and operates with zero data retention. A dedicated EU endpoint (https://api.eu.edenai.run/v3) uses the same API, and non-EU models are refused rather than billed when EU-only rules apply. The console example shows a team rule set to "EU only" with data staying in Europe.

This matters if your organization requires EU data residency or has procurement gates around certifications. Verify the specific certifications and data-retention terms against your own compliance requirements before relying on them.

When Eden AI is a good fit — and when it isn't

It likely fits if you:

• Use or plan to use multiple model providers and want one integration and one key.
• Need per-team budgets, model access rules, and cost attribution without building internal tooling.
• Require EU hosting, EU-only routing, and recognized security certifications.
• Want fallbacks and caching handled at the gateway rather than in application code.

Consider alternatives if you:

• Use a single provider and have no multi-model or governance needs — a direct integration may be simpler.
• Need full control over routing logic at a low level; a gateway abstracts some of that away.
• Have procurement constraints that the 5.5% credit-purchase fee or the credit model doesn't satisfy.

Getting started

1. Get an API key from Eden AI (the site offers a "Get your API key" path and a contact option for sales).
2. Point your client at the gateway using the OpenAI-compatible request shape; use the EU endpoint if you need EU-only routing.
3. Send a test request and confirm the response includes cost information.
4. Configure teams and rules in the console: budgets, allowed/denied model patterns, and EU-only restrictions where needed.
5. Verify behavior: check that a denied model is refused, that a fallback triggers when a primary model fails, and that spend appears attributed to the right team.

Common snags to watch: untagged requests show up as unattributed spend, so tag requests by team or product from the start; and EU-only rules will refuse non-EU models, so confirm your model choices are available on the EU endpoint before rolling out.