API portal
Console coming soon
Browse documentation

Developer docs

Start from a live reference page.

Phone layout stays search-first: pick a page here, then read it in a full single-column view.

Getting Started

OverviewPlatform map, live routes, auth model, and API quick links.QuickstartMake the first live request and inspect the response shape.AuthenticationBearer keys, scopes, rotation, and account-bound access.

Models

EvaEsi InstantByte-native chat with live evidence retrieval. The default model.Instant FastInstant with a shorter evidence gather, for latency-bound work.EvaEsi ReasoningEvidence-gather plus Elements synthesis for harder questions.Reasoning DeepA longer deliberation budget and the widest evidence sweep.Reasoning VerifyChecks claims against evidence and reports what it cannot support.Reasoning FastReasoning held to an interactive latency budget.ElementsCoding and Studio model. Routes directly without the evidence-gather pass.Elements FastSingle-file edits and short-range changes, tuned for latency.Elements CodebaseRepository-wide context for migrations and cross-file work.

API Reference

Responses APICanonical inference route for synchronous requests and output.Sources APIFetch evidence bundles and provenance for prior responses.Usage APICurrent period totals, history windows, and live limits envelopes.Models CatalogEvery model version, its canonical ID and its published rates.Batch APIDurable batches of up to 100 requests: submit, poll, collect.WebhooksSigned event deliveries: envelope, headers, and verification.StreamingServer sent events, frame shapes and handling failures mid stream.SchemaOpenAPI and JSON Schema documents, and generating a client from them.Error CodesOperational error contract, retry semantics, and failure classes.

Operations

Developer ConsoleThe console surfaces that open at launch, mapped honestly.Rungs & PricingBilling units, plan allowances, project budgets, and spend model.Rate LimitsHeaders, envelopes, throttling behavior, and budget enforcement.

Enterprise

EnterpriseReserved and dedicated deployments, isolation, data handling and controls.

Console

API keysIssue, scope and rotate API keys. Opens at launch.UsageRungs consumed, per model and per key. Opens at launch.BillingBudgets, invoices and payment. Opens at launch.SettingsOrganisation, members and security. Opens at launch.

Policies

Terms of ServiceOperational policy, legal terms, or support guidance.Privacy PolicyOperational policy, legal terms, or support guidance.Cookie PolicyOperational policy, legal terms, or support guidance.Community GuidelinesOperational policy, legal terms, or support guidance.Acceptable Use PolicyOperational policy, legal terms, or support guidance.Refund PolicyOperational policy, legal terms, or support guidance.Billing & TiersOperational policy, legal terms, or support guidance.HelpOperational policy, legal terms, or support guidance.API TermsOperational policy, legal terms, or support guidance.AI Use and Output SafetyOperational policy, legal terms, or support guidance.Accessibility StatementOperational policy, legal terms, or support guidance.SecurityOperational policy, legal terms, or support guidance.Service CommitmentsOperational policy, legal terms, or support guidance.SupportOperational policy, legal terms, or support guidance.ContactOperational policy, legal terms, or support guidance.

Console

Where you will run your integration: keys, usage, budgets, webhooks and the record of who changed what. It opens with the platform. Until then every console link shows the coming soon screen, and this page is an honest map of what sits behind it.

Before launch

The documentation you are reading is live and current. The console itself, along with sign-in and account creation on this domain, is closed until launch: visiting /console, any console section, or an auth route shows the EvaEsi coming-soon screen. No waitlist, no placeholder forms. The surfaces open when the platform does. Everything described below is built and behind that gate.

Workspace & Projects

Signing in provisions a developer workspace: an organization holding one or more projects. A project is the unit everything else attaches to. API keys belong to a project, usage is metered per project, budgets cap a project, and webhook endpoints notify about a project. The workspace.provisioned webhook event fires when this structure is first created.

API keys

Keys are issued per project and carry the esi_dev_ prefix documented in Authentication. The console shows each key's prefix, creation time, and last use; the full secret is shown once, at creation. Keys can be rotated (old secret stops working, replacement issued) and revoked. Every issue, rotation, and revocation lands in the audit log and can fire a webhook.

Playground

The playground runs real requests against the Responses API with your project's key, so what you see is exactly what your integration will get. It uses the same models, the same limits and the same billing. It is a test bench, not a simulator: playground requests meter usage like any other request.

The model catalog page beside it lists the live models with their canonical IDs and per-model rung multipliers, matching the Models Catalog API.

Usage Ledger

The usage section shows current-period totals, request history, and the live limit envelopes for your tier. This is the browsable view of what the Usage API returns programmatically. Rungs are the billing unit throughout; see Rungs & Pricing for how they are counted.

Billing and budgets

Billing shows your plan, invoices, and payment method, and holds the project budget controls. A project budget is a hard cap: a request that would exceed it is refused with BUDGET_EXCEEDED rather than billed past the line, and if enforcement cannot be verified the API fails closed with BUDGET_UNAVAILABLE. The cap is never waved through on error. Budget changes fire the budget.updated webhook event.

Webhooks

The webhooks section manages signed event notifications to your own endpoints: create and edit endpoints, choose event subscriptions, rotate signing secrets, send test deliveries, and browse per-attempt delivery history. The full delivery contract. The envelope, headers and signature verification are documented in the Webhooks reference.

Security & Logs

The security section shows the posture of your workspace: active sessions, key hygiene (age, last use), and recent security-relevant events. The logs section holds two records side by side. The audit log records who did what in the console, covering key operations, budget changes and webhook changes. The request log records recent API requests with their status and rung cost. Between them they answer both "what changed in my workspace" and "what is my integration actually doing".