> ## Documentation Index
> Fetch the complete documentation index at: https://support.configview.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Eden AI setup

ConfigView reads your Eden AI (AI gateway) organization through the Eden AI **v3 Management API** (`https://api.edenai.run/v3/manage`), using a **management key** limited to the `manage:read` scope. ConfigView sends only `GET` requests. It never creates, changes, rotates or revokes anything in Eden AI.

You will end up with **1 required secret** (`EDENAI_MANAGEMENT_KEY`) in ConfigView when setup is complete.

> **Scope of this integration today.** ConfigView reads who is in your Eden AI organization (members with work email, name, role, guardrail and status), the roles and their permissions, SCIM directory groups, guardrails, the organization settings (role-based access, SSO requirement, data retention), inference-key metadata (name, owner, balance, expiry, revoked or not), usage and cost totals per key and per member for the last 30 days, and the credit balance. It does **not** read prompts, completions, request logs, key secrets, invoices or billing contacts.

***

## What you need

* An Eden AI organization owner, or a member granted **Manage API keys**
* A management key. Management keys are a different kind from inference keys: they start `mgmt-eden-`, while inference keys start `sk-eden-` and are refused (HTTP 401) on the management API.

***

## Step 1: Open the Eden AI page in ConfigView

Open ConfigView in a second browser tab and leave it open:

`https://{companyname}.configview.com/admin/integrations/eden-ai`

***

## Step 2: Create the management key

1. In the Eden AI dashboard open **Account > Management Keys**
2. Create a key with **only the `manage:read` scope**. Do not add `manage:write` or `manage:mint`.
3. Copy the key now. Eden AI shows it once.
4. In the ConfigView tab paste it into `EDENAI_MANAGEMENT_KEY` under **Credentials** and save

If you already hold an issuer key, you can mint the read-only key by calling `POST /v3/manage/auth-keys` with `{"name": "ConfigView", "scopes": ["manage:read"]}`. The key is permanent unless you set an expiry, and Eden AI does not rotate it. Revoke it in the same page to cut ConfigView off.

***

## Step 3: Connect and verify

1. Click **Connect**. ConfigView creates its tables and schedules every collector at your default run time:

| Script | Notes |
| - | - |
| **Organization** | Name, role-based access, SSO requirement, data retention, allowed regions. |
| **Members** | Everyone in the organization with role, guardrail, groups and key count. |
| **Roles** | Built-in and custom roles with their permissions. |
| **Groups** | SCIM directory groups and the role each maps to. |
| **Guardrails** | Spend and rate guardrails that members, roles and keys point at. |
| **Inference keys** | Key metadata: owner, balance, expiry, tags, revoked. Never the key. |
| **Usage by key** | Daily cost and call counts per key and feature, last 30 days. |
| **Usage by member** | Total cost per member, last 30 days. |
| **Billing** | Prepaid or postpaid, credit balance, auto-refill. |

2. Click **Verify now**. The health check reads the secret, then calls `whoami` and the organization endpoint.

If a check fails:

* **401.** The key is wrong, revoked, expired, or it is an inference key (`sk-eden-`) instead of a management key (`mgmt-eden-`).
* **403 or 404.** The key lacks `manage:read`, or your plan does not include that area (directory groups, for example, need SCIM). That collector is skipped and the others still run.

***

## Data Tables

Each table has a `run_at` column and keeps only the newest run.

| Table | Source | Key Columns |
| - | - | - |
| `edenai_organization` | `GET /organization` | organization\_id, name, rbac\_enabled, sso\_required, zero\_data\_retention, data\_retention, default\_guardrail, allowed\_regions |
| `edenai_members` | `GET /members` | email, name, role, status, guardrail, rate\_limit, group\_names, active\_key\_count |
| `edenai_roles` | `GET /roles` | role\_id, name, is\_system\_role, permission\_count, permissions |
| `edenai_groups` | `GET /groups` | group\_id, name, role, member\_count, member\_emails |
| `edenai_guardrails` | `GET /guardrails` | guardrail\_id, name, is\_active, budget\_limit, rate\_limit |
| `edenai_keys` | `GET /keys` | key\_id, name, token\_type, owner\_email, key\_hint (last 4), balance, expire\_time, revoked |
| `edenai_usage_by_key` | `GET /usage/` | key\_name, usage\_date, feature, subfeature, total\_cost, call\_count |
| `edenai_usage_by_member` | `GET /usage/?group_by=user` | member\_email, total\_cost, window\_begin, window\_end |
| `edenai_billing` | `GET /billing` | billing\_mode, currency, balance, auto\_refill\_\* |

Every table except usage also keeps `response_keys`: the names (never the values) of the fields Eden AI returned, so you can see what the API really sends.

***

## Things worth knowing

**Field names are not all published.** Eden AI documents the management endpoints but names few response fields. ConfigView tries several likely names per column, so the first run may leave some columns empty (for example SSO or retention flags, member role, guardrail). Check `response_keys` and report empty columns so the mapping can be fixed.

**Usage is keyed by key name.** The usage endpoint identifies a key by its name, not its id, so two keys with the same name cannot be told apart. Calls without a key appear as `base_token`.

**Currency.** `total_cost` is whatever unit Eden AI reports (assumed USD or credits). Billing carries its own currency field.

**Window.** Usage covers the last 30 days; Eden AI has data only from 2026-09-03 and caches answers for 60 seconds. ConfigView asks for usage billed through Eden AI and through your own provider keys.

**Audit log.** Eden AI lists audit logging as a feature but the Management API has no audit endpoint, so none is collected.

**Plan.** Management API availability by plan, and SSO, role-based access and SCIM groups, are not confirmed for every plan. A 403 or 404 skips that collector.

**Rate limit.** Eden AI allows 10 requests per second per account, shared across all keys, and answers HTTP 429 beyond that. ConfigView paces itself at 120 requests a minute and waits as long as Eden AI asks.

## What isn't collected

* Prompts, completions and model outputs; request logs and their export (`/usage/requests`, `/usage/llm`)
* Inference key values; only the last four characters of the masked hint are kept
* Management key inventory (needs `manage:mint`)
* Invoices, statements and billing contacts


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.