Version 2
Dvaarik Developer Platform
Voice AI agents API — bring your own AI keys and your own phone line; Dvaarik operates the realtime voice infrastructure. Every credential, machine key, limit, agent, call, and webhook belongs to one project.
- API origin:
https://api.developers.dvaarik.com - Console auth:
Authorization: Bearer <account-access-token> - Machine auth:
X-Api-Key: <project-api-key> - Voice orchestration: $0.005 per connected minute — half a cent — rounded up to the next minute, prepaid in USD
- Pay as you go: no monthly platform fee, no minimum spend, no seat fee, no contract
- Provider and carrier usage: billed directly by the accounts you bring
- Release scope: voice only; this platform publishes no developer messaging-channel API
> Release status: projects, scoped keys, provider accounts, agents, browser and outbound voice sessions, carrier connections and numbers, webhooks, and USD billing are all served on two doors — a machine door that takes a project key from your server, and a console door that takes your account session from the browser. The console never holds a project key. The full contract is on the API reference page, derived from the backend's OpenAPI document.
Ownership model#
Dvaarik separates three responsibilities:
1. You own AI providers. Connect credentials to one project. The API never returns the secret after save, and a call is admitted only against accounts the provider has confirmed. 2. You own telephony. Keep the carrier account, numbers, routing, compliance, and carrier bill. Twilio, Plivo, Exotel, FreJun/Teler, and Telnyx connect with your own credentials; Dvaarik hands you the URL each number must point at. 3. Dvaarik owns infrastructure. Realtime voice orchestration, interruption handling, project admission, exact per-minute (rounded up) metering, and signed, retried event delivery live here.
A missing or invalid project credential is an error. Runtime code does not silently use a shared Dvaarik credential.
Resource map#
| Resource | Machine door (project key) | Console door (account JWT) |
|---|---|---|
| Projects and keys | — | /v2/projects, /v2/api-keys |
| Provider catalogue | — | /v2/provider-catalog |
| Provider accounts | /v2/provider-accounts | /console/v2/projects/{project_id}/provider-accounts |
| Agents | /v2/agents | /console/v2/projects/{project_id}/agents |
| Voice sessions | /v2/voice/sessions (+ /outbound) | /console/v2/projects/{project_id}/voice/sessions (+ /outbound) |
| Carriers and numbers | /v2/carriers | /console/v2/projects/{project_id}/carriers |
| Webhooks | /v2/projects/{project_id}/webhooks | /console/v2/projects/{project_id}/webhooks |
| Billing | — | /console/v2/billing |
Both doors call the same service and return the same shapes, so what the console shows is exactly what your server sees.
Commercial and launch status#
The active voice rate has no plan ladder or provider bundle. Connected seconds are charged with fixed-point integer arithmetic against a prepaid USD wallet. AI and carrier providers charge you separately under your own accounts.
This release is voice only: there is no developer messaging-channel API, and the console exposes no messaging surface.
Reference sections
Start with the quickstart; the API reference is derived from the backend's OpenAPI document. Search with /.
Providers
Delivery
Billing
Reference
API reference
Start at the security boundary
Create a project, connect only its providers, and issue a narrowly scoped server key.