Eridian

Authentication

Bearer keys, scopes, rotation, and request identity.

All API requests require a valid API key. Pass it in the Authorization header using Bearer authentication. Keys are project-scoped secrets - treat them like production database credentials.

Authorization: Bearer eridian_sk_...

API Keys

Each Eridian project has its own set of API keys. Keys are scoped to the project and can be granted granular permissions:

ScopeDescription
inference:readRead inference responses and status
inference:writeCreate inference requests
models:readList available models
usage:readRead usage and cost data
keys:manageCreate, rotate, and revoke API keys
budgets:manageCreate and modify budgets
rag:writeUpload and manage RAG documents
templates:manageCreate and modify prompt templates
audit:readExport audit log events
governance:manageModify webhooks and policy settings
dev:read / dev:writeEridian Dev repositories, reviews, Q&A, tests
legal:read / legal:writeEridian Legal matters, contracts, mappings, redlines
ops:read / ops:writeEridian Ops incidents, logs, post-mortems, connectors
risk:read / risk:writeEridian Risk cases, evidence, assessments, reports
risk:approveApprove gated Risk actions (Enterprise alias of dual control)

Vertical keys should carry the matching *:write scope plus inference:write. A Dev CI key does not need legal:write. See Eridian Dev, Eridian Legal, Eridian Ops, and Eridian Risk.

Create Key

POST /v1/keys
Authorization: Bearer eridian_sk_...
Content-Type: application/json
{
  "project_id": "prj_legal_001",
  "name": "production-inference",
  "scopes": ["inference:write", "models:read"],
  "budget_usd": 10000
}

The full key is returned once at creation. Store it securely - it cannot be retrieved again.

Key Rotation

Rotate your API key without downtime:

  1. Create a new key with the same scopes.
  2. Update your application to use the new key.
  3. Verify the new key works against a canary project.
  4. Revoke the old key.

Rotated keys maintain a 24-hour overlap window when configured, allowing zero-downtime rotation across distributed services.

Key Lifecycle Audit Events

ActionScope requiredAudit event
Create keykeys:managekey.create
Rotate keykeys:managekey.rotate
Revoke keykeys:managekey.revoke
List keyskeys:managekey.list

Rate Limits

Default rate limits by plan:

PlanRequests/minTokens/min
Starter60100,000
Growth300500,000
EnterpriseCustomCustom

Rate limit headers are included in every response:

X-Eridian-RateLimit-Limit: 300
X-Eridian-RateLimit-Remaining: 247
X-Eridian-RateLimit-Reset: 1718400000

Budget-Scoped Keys

Assign monthly budget ceilings per key. When a key approaches 80% or 95% of budget, webhook and email alerts fire. Hard-stop keys return HTTP 429 with error.code: budget_exceeded.

Base URL

EnvironmentBase URL
Productionhttps://api.geteridian.com
API Versionv1

SSO and Dashboard Access

Enterprise tenants authenticate operators via SAML 2.0 (Okta, Azure AD, Google Workspace, OneLogin). SCIM provisioning synchronizes users and group memberships. Dashboard sessions honor configurable timeout policies and optional IP allowlists.

Error Codes

HTTPCodeMeaning
401invalid_api_keyKey missing, revoked, or malformed
403insufficient_scopeValid key lacking required scope
429rate_limit_exceededPer-minute request or token limit hit
429budget_exceededKey or project budget hard stop

See API Keys for create/rotate/revoke, Governance for budget configuration, and Quickstart for the first authenticated call.

Production API credentials are issued with an institution workspace. Contact sales if you need access.