API
DVARA's governed HTTP surface is the Data Plane API — every LLM, MCP and A2A call flows through it, and through the same policy engine, audit trail and RBAC.
Administration is done through the Console and Portal, not a REST API: the Admin API was removed in 1.7.0 and every endpoint under /v1/admin/** returns 404.
| Surface | Port | Audience | Auth | Reference |
|---|---|---|---|---|
| Data Plane API | 8080 | Application developers, AI agents, SDKs — every system making LLM or MCP calls through the gateway | Authorization: Bearer gw_… (workspace API key issued from the DVARA Flightdeck) | Data Plane API — interactive, below |
| Console + Portal | 8090 | Platform engineers and workspace users managing configuration — workspaces, API keys, routes, policies, credentials, pricing, budgets, webhooks, MCP servers, audit, and config export/import | Browser session (built-in, OIDC or SAML); a personal access token (dvara_pat_…) for scripting | Administering DVARA |
The Data Plane API has an interactive Specifications subsection in the left sidebar, generated at build time from a committed OpenAPI spec and rendered with a request/response/schema pane and a Try it panel that sends real HTTP requests from your browser to a configurable target.
For administration, the DVARA Flightdeck docs walk through each capability in the UI — workspaces and users, routes and canary splits, budgets and chargeback, webhooks, MCP servers, audit events. Bulk provisioning is the Console's GitOps export/import.
A running DVARA platform always serves both components — the LLM Gateway on 8080 for the data plane, and the DVARA Flightdeck on 8090 for the Console and Portal. See the Quickstart for the Docker Compose setup that brings both up at once.
Which one do I start with?
If you are integrating DVARA into an application or an agent, start with the Data Plane API Overview. It walks through the prerequisites, authentication, a GET /actuator/health smoke test, and a first chat completion, then hands you off to the per-endpoint Specifications pages with their interactive Try-it panels.
If you are managing a DVARA deployment — provisioning workspaces, rotating provider credentials, setting budgets, configuring routes, or exporting the whole config for GitOps — start with Administering DVARA, then the DVARA Flightdeck docs for each capability in the UI.
The audit event stream records every mutation the same way regardless of which surface made the change.