Organization management

Know who spent what on AI, down to the call

Tag every request with the client, project, team or employee it belongs to. Charge clients back with detailed statements, give each team a budget it cannot overrun, and decide which models each team is allowed to call. One organization, one invoice, full visibility.

Talk to us
Start building
ROLES & PERMISSIONS • BUDGETS PER KEY • MODEL ALLOW-LISTS • SOC 2 & ISO 27001 CERTIFIED
Monitoring · Usage by client
Platform
Models
Monitoring
API keys
Organization
Members
Guardrails
Tags
Billing
Sep 1 – Sep 30, 2026Filter tag:client = acmetag:env = prod
Spend
$4,128
Sep 1 – 30
Tagged
93%
of spend attributed
Clients
12
4 projects on average
Untagged
$273
7% · review
Daily spend by client
Sep 1Sep 8Sep 15Sep 22Sep 30
acmeglobexinitechumbrella
By project · acme
support-bot
$1,204
invoices-ocr
$388
search
$320
By member · acme
J. Martin
$1,051
A. Silva
$592
Service key
$269
ClientProjectsRequestsCostShare of total
acme3812,400$1,912.1846%
globex2540,112$1,240.0230%
initech4301,870$702.9017%
umbrella19,830$0.00BYOK
Untagged—64,201$273.307% · review
Guardrail · EU-regulated teams
allowmistral/*openai/*@eu
deny*/*
100 / minute$500 / week

Built for agencies, platforms and enterprise AI teams.

Seats per organization
Unlimited
Tags per request
Up to 10
Budget reset periods
Daily to monthly
Invoice for all providers
One
Roles and permissions
Budgets per API key
Model allow-lists
One invoice for every provider
How it fits together

One organization, many clients, every token accounted for

Members, keys and tags give you four levels of attribution without creating a separate account per client.

Attribute spend

Every token attributed to a client, a project, a team or a person

Eden AI records the cost of every request together with the API key, the member and the tags behind it, so you can split your AI spend the way your business is organized.

Tags on every call

Add key/value labels to any request with the X-EdenAI-Tags header. Up to ten tags per call, counted once the header and the body are merged, on every endpoint, LLM or expert model.

Default tags on API keys

Set default tags when you create a key and every call made with it inherits them. One key per client means zero code changes for your developers.

API keyDefault tagsBudget
acme-prodclient=acme env=prod$500 / mo
globex-botclient=globex$1,000 / mo
sandboxenv=test$50 / wk

Filter on any dimension

Filter cost by tag, API key, member, model, provider or feature, and combine them to answer what the support bot cost for Acme in September.

Untagged spend stays visible

Whatever is not tagged lands in its own row, so you see the gap and fix the key or the call that caused it.

One row per tag combination

The usage table carries the date, the tags and the cost in US dollars of every slice, with one column per tag key. A client, a project or an environment is one filter away.

datetag:clienttag:projectcost_usd
2026-09-30acmeinvoices-ocr12.18
2026-09-30acmesupport-bot40.02
2026-09-30globexsearch9.90
One column per tag key, dated, with the cost in US dollars

Management API

Query the same usage data over HTTP, by period, by API key and grouped by member, and feed your own billing or chargeback system.

Built-in Guardrails

Charge back, budget and restrict, from one place

Tagged usage is the raw material. From there you bill your clients, cap what each team can spend, and decide which models they are allowed to call.

01 · Chargeback

Charge your clients back, with the detail to back it up

Filter a period on one client tag and you have a breakdown split by project, team or employee. Build the client-facing statement from it, while you keep one consolidated Eden AI invoice covering every provider. Talk to us about custom billing and invoicing structures.

Talk to us
Acme Corp
Draft
Usage statement · September 2026 · No. 2026-09-ACME
client=acmeenv=prod
Prepared by
Your company
Oct 1, 2026 · from Eden AI usage
ProjectRequestsCost
support-bot812,400$1,204.18
invoices-ocr96,210$388.40
search301,870$319.60
Total · September 2026$1,912.18
02 · Budgets

Give every team a budget it cannot overrun

Each API key carries a spending cap that resets daily, weekly or monthly. When a key reaches $0 it stops working until the next period. Guardrails add spend caps and rate limits per role, member or key, and the whole organization shares one credit balance with billing rights reserved to the roles you choose.

Read about API keys
03 · Compliance

Limit which models each team can call

Allow or deny models and providers with patterns such as anthropic/* or */*, scope rules per feature, and attach them to roles, members or API keys. Pin regulated teams to the EU endpoint, where non-EU models return HTTP 451 and never spend credits. Zero Data Retention and no training on your data by default.

Read about guardrails
Customer stories

One contract, one bill, many providers

Nikola Komes, CEO at InsiderCX

We are implementing a combination of sentiment analysis and topic extraction into our platform, which handles a big load of patient comments coming through a survey. It would be a hassle to setup an infrastructure to compare all the AI providers and their output, so that's why we decided for Eden AI, along with the fact that it provides us with an unified billing as opposed to maintaining an account on each of the providers.

Nikola Komes

CEO @ InsiderCX

Alain Mielle, Innovation Manager at the Council of Europe

I believe in accessing AI services through a one-stop shop that brings together major providers like Amazon and Azure, as well as emerging specialists. Eden AI is the right solution for our first ‘laboratory’ stage, giving us a portal with multiple services we can use depending on each project.

Alain Mielle

Innovation Manager @ Council of Europe

Govern teams

One organization, with the roles and controls of an enterprise

Invite your whole company under one organization and one shared credit balance, then decide who can see, who can manage and who can pay.

Roles and permissions

Manager, Billing and Member roles out of the box, plus custom roles that combine organization, members and billing permissions.

MemberRole
JM Julia MartinManager
KO Karim OumarBilling
AS Ana SilvaMember
CR Chris RoyCustom · Auditor

SSO, SCIM and audit logs

Sign in through Okta, Azure AD or WorkOS, sync your directory with SCIM and keep an administrative audit log. Contact the Eden AI team to set it up.

SSO · OktaConnected
SCIM provisioningSynced 2 min ago
Audit log
WhenWhoWhat
14:02J. MartinBudget acme-prod → $1,000
13:40K. OumarGuardrail EU → role Analyst
09:12SCIM3 members from Okta

Guardrails that stack

Reusable usage policies that set which models a team can call, how often, and how much a member can spend, attached at the level you choose.

Talk to us
Read about organizations
Comparative table

One account per client vs. tags on one organization

Separate accounts per client

Eden AI organization

One account, one invoice and one set of keys per client to maintain.

One organization and one invoice; clients, projects and teams are tags.

Spend can be split by a single dimension: the account.

Split by client, project, team, member, model or feature, combined.

Budgets live in each provider's console, if they exist at all.

Budgets per API key with daily, weekly or monthly resets, enforced at the gateway.

Model restrictions enforced by code review.

Model allow-lists and rate limits attached to roles, members or keys.

Chargeback assembled by hand from several provider exports.

Per-client breakdowns built from tagged usage, one row per tag combination.

Developer experience

Tag once, attribute everywhere

Tags travel as a header on any endpoint, or as defaults on the API key. The cost of each request comes back in the response and feeds the filters in the dashboard.

PYTHON · DEFAULT TAGS FOR A WHOLE CLIENT
# One client, one set of tags, zero changes in your call sites
from openai import OpenAI

client = OpenAI(
    base_url="https://api.edenai.run/v3",
    api_key=EDENAI_API_KEY,
    default_headers={
        "X-EdenAI-Tags": "client=acme,project=support-bot,team=cx"
    },
)

# Or set default tags on the API key itself in the dashboard:
# every call made with that key inherits them.
CURL · TAGS ON A SINGLE CALL
# Tag a single call, on any endpoint
curl https://api.edenai.run/v3/chat/completions \
  -H "Authorization: Bearer $EDENAI_API_KEY" \
  -H "X-EdenAI-Tags: client=acme,project=invoices,env=prod" \
  -d '{"model": "openai/gpt-5.4-nano", "messages": [...]}'

# Response
{
  "usage": { "total_tokens": 508 },
  "cost": 0.000202
}

# Then, in Monitoring: filter by tag and read the cost
# per client, per project or per environment.

Questions we're usually asked

Get your API key
Read the docs

Can I split my AI bill per client?

Yes. Tag each request with a client value, or set that tag as a default on the API key you give that client's project. Monitoring then filters usage on the tag, so a per-client breakdown is one filter away, with one row per tag combination.

Do I need a separate account or project per client?

No. One organization is enough. Clients, projects, teams and environments are tags, and you can combine them. If you prefer a physical separation, create one API key per client with its own budget and default tags.

Can I invoice each client separately?

You receive one consolidated Eden AI invoice covering every provider. From the tagged usage you build the detailed per-client statements you send for chargeback. Talk to us about custom billing and invoicing structures.

How do budgets work?

Each API key can carry a spending cap that resets daily, weekly or monthly. When the cap reaches $0 the key stops working until the next period. Guardrails add spend caps and rate limits per role, member or key, and the strictest applicable rule wins.

Can I restrict which models a team uses?

Yes. Guardrails allow or deny models and providers with patterns such as anthropic/* or */*, scoped per feature and attached to roles, members or API keys. For data residency, use the EU endpoint: non-EU models are refused with HTTP 451 and never spend credits.

Who can see costs and manage billing?

Organization roles decide. Managers see everything, Billing roles manage credits and invoices, and Members use the API with the keys and budgets they are given. Custom roles let you compose permissions.

Are tags personal data?

Tags are billing metadata kept with usage data. Use identifiers such as client codes or project names and keep personal data out of them. Zero Data Retention for prompts and outputs is unaffected.

Which plan includes organization management?

Members, roles, multiple API keys with budgets and tags are available to every organization. For guardrails, SSO, SCIM, audit logging and custom billing, contact the Eden AI team to have them set up.

How many tags can I send per request?

Up to ten per call, counted once the header and the request body are merged. Six tags in the header and six in the body put the call over the limit, so plan the budget across both.

Can I keep a regulated team inside Europe?

Yes. Point that team's calls at the EU endpoint and only models eligible for European processing will serve them. A model that is not eligible is refused with HTTP 451 before the provider is contacted, so the request never spends credits and never leaves the European boundary.

What is the rate limit?

A per-second rate limit applies by default and can be raised on request. Advanced plans get a higher custom limit, and guardrails can set a lower one per role, member or key.

Does Eden AI mark up provider prices?

No. The prices in the model catalog are the providers' exact prices. The only additional cost is a 5.5% platform fee applied when you buy credits. There is no subscription and no API call limit.

let’s start

Run AI for every client and team from one organization.

Attribute every token, charge back with confidence, and keep each team inside its budget and its approved models.

Talk to us
Start building

ROLES & PERMISSIONS • BUDGETS PER KEY • ONE INVOICE FOR EVERY PROVIDER