API
DVARA is an AI governance platform with two governed HTTP surfaces. Both flow through the same policy engine, the same audit trail, and the same RBAC — they differ in who they are for, which data plane they sit in front of, and how clients authenticate.
| 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_… (tenant API key issued from the DVARA Flightdeck) | Data Plane API — interactive, below |
| Admin API | 8090 | Platform engineers, DevOps, automation pipelines managing gateway configuration — tenants, API keys, routes, policies, credentials, pricing, budgets, webhooks, MCP servers, audit, and config export/import | Personal access token (dvara_pat_…), OIDC JWT, or SAML session | Admin API — interactive, below |
Both surfaces get their own interactive Specifications subsection in the left sidebar, generated at build time from committed OpenAPI specs and rendered with a request/response/schema pane on the left and a Try it panel on the right that sends real HTTP requests from your browser to a configurable target.
The Admin API is also the surface the DVARA Flightdeck calls under the hood, so every admin capability has both a machine-readable contract in the reference below and an end-to-end walkthrough on the matching Console feature page (tenants and users, routes and canary splits, budgets and chargeback, webhooks, MCP servers, audit events, and so on). Use the DVARA Flightdeck docs to see the API in context; use the Specifications pages to inspect schemas and try calls directly from your browser.
There is no separate licensing or activation for the two surfaces. A running DVARA governance platform always serves both — the LLM Gateway component listens on 8080 for the data plane, and the DVARA Flightdeck listens on 8090 for the Admin API plus the DVARA Flightdeck web UI. 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 tenants, rotating provider credentials, setting budgets, configuring routes, or exporting the whole config for GitOps — start with the Admin API Overview. It shows the minimal four-call sequence to stand up a tenant + API key + route from scratch, then hands you off to the Admin Specifications pages organized by resource (Tenants, Routes, Policies, Budgets, Credentials, Webhooks, MCP Servers, Audit, Config).
The Admin API and the DVARA Flightdeck expose the same capabilities on top of the same tenants, routes, policies, and audit trail — you can provision interactively from DVARA Flightdeck and automate the same actions over the Admin API from CI/CD. The Console docs walk through each capability in the UI; the Admin API reference is the machine-readable contract for the same surface; and the audit event stream records every mutation the same way, whichever surface made the change.