Separate runtime and admin access
Use bearer keys for tenant runtime calls and x-admin-key for platform automation.
voice.stateset.app
StateSet Voice API for Voice AI Agents.
A clean, production API for inbound and outbound phone agents with realtime AI, signed telephony webhooks, human handoff, call logs, evaluations, and tenant governance.
Bearer auth
Admin keys
Twilio signatures
OpenAPI 3.1
Tenant runtime APIMake calls, inspect call logs, retrieve sessions, and integrate operator workflows.
Admin APIManage tenants, API keys, agent versions, phone routes, rollout policy, and diagnostics.
Webhook endpointsReceive inbound calls and status callbacks with Twilio signature verification.
OpenAPI 3.1 specsGenerate clients from scoped public, admin, and full contracts.
Implementation blueprint
A production path from first request to governed phone agent.
StateSet Voice is documented around the sequence engineering, operations, and business owners need to align on before customer traffic moves through an AI agent.
Design
Define the agent contract
Map intents, allowed tools, escalation rules, identity requirements, and business outcomes before coding.
Integrate
Wire calls and webhooks
Use runtime bearer auth for outbound calls and signed Twilio callbacks for inbound traffic.
Observe
Review sessions and logs
Inspect transcripts, function calls, call logs, evaluations, and callback queues before scaling.
Govern
Stage the rollout
Approve credentials, phone routes, agent versions, telemetry, launch owners, and rollback paths.
Integration path
Build the agent, connect the phone line, and operate the workflow.
The documentation is organized around the sequence a business integration team actually follows: authenticate, make calls, handle inbound traffic, observe sessions, and govern launch.
Create outbound calls
POST to /api/v1/make-call with a tenant key, phone numbers, and an agent route.
Handle inbound calls
Point Twilio at /api/v1/incoming-call, verify the signature, and return the correct media stream setup.
Inspect sessions and outcomes
Use call logs, voice sessions, active sessions, transcripts, function calls, and evaluations.
Escalate work safely
Create callback tasks, operator queues, follow-up notifications, and handoff workflows from agent outcomes.
Launch with controls
Stage agent versions, phone routes, rollout policy, credentials, and approval gates before production traffic.
Docs map
Reference material for teams shipping voice agents.
Start with the quickstart, then move into endpoint guides, security, examples, and production readiness as the integration matures.
| Need | Document | Path |
|---|---|---|
| First call | Quickstart and launch checklist | /getting-started |
| API key access | Request provisioning from the StateSet team | /request-access |
| Endpoint behavior | Calls, sessions, admin, and operations guides | /docs/api-reference |
| Client generation | Scoped OpenAPI documents | /api-docs/public.json |
| Webhook security | Twilio signature verification | /docs/webhook-signatures |
| Launch control | Production readiness review | /docs/production-readiness |
Enterprise controls
Designed for governed business workflows.
Voice agents need clear boundaries because phone calls can create obligations. StateSet keeps credentials, routing, observability, and launch approvals explicit.
- Tenant bearer tokens and admin API keys are documented as separate credential surfaces.
- Inbound telephony uses
X-Twilio-Signatureverification before tenant routing. - Runtime activity is reviewable through call logs, voice sessions, evaluations, and callback queues.
- Agent versions, phone routes, rollout policy, and readiness checks support staged production launch.
Build with the API
Start building a production Voice AI Agent.
Use the quickstart for the first call, endpoint guides for integration details, and scoped OpenAPI specs for generated clients.