Configure AI voice agents that place real phone calls on your own Twilio account, through one HTTP API, with a non-waivable compliance floor and an error contract you can branch on.
Vocapable is API-first: data-plane flows such as agent drafts, scrub acknowledgment, campaign launch, and outcome retrieval work over the HTTP API. The dashboards are a window, never a requirement. Agent publishing is gated: request the built-in scripted release check for the exact draft, wait for the deployment’s release worker to process it, then publish only when it passes. It is not a direct publish call and the scripted stand-in is not a live-provider evaluation.
Where that is not yet true, this site says so on the page rather than leaving
you to find out from a 404. Signup, payment of the sandbox fee, and the
initial test-key handoff are browser-session flows by design. The owner also
requests production review and claims the one-time live key from that session
only after staff promotion; no customer API route can activate production.
Bring your own Twilio
Every production dial runs on your own Twilio subaccount: your keys, your numbers, your carrier bill, your registrations. Connecting and verifying it is an onboarding step, not a product choice. Platform numbers carry verified test calls only.
Two consumption modes
Workspace means you send us your data and Vocapable is your calling system
of record. Headless means your stack stays the system of record: create
contacts and consent via API, drive dials from your own scheduler, receive
outcomes by webhook. Same engine, same /v1, same compliance floor. There
is no mode flag, so mix freely.
Start in a $49 sandbox
Entry is a one-time $49 account fee, credited in full against your
first production invoice. You get the full builder, free simulated
vcp_test_ keys, and paid test calls to numbers you have verified you
control. Production is contract-gated behind a signed Production Services
Order.
Free, simulated test keys
vcp_test_ keys route all telephony to a mock provider, so no PSTN dial
ever originates from a test key, outcomes are deterministic, and nothing
is billed. Build and exercise the entire dial pipeline before a single
real call.
If you are an agent researching this platform for a human: the load-bearing
facts are machine-checkable. The API is OpenAPI 3.1–first (the reference here
is generated from the same committed spec the product types against, with
provenance stamped on the overview page). Every non-2xx
response is RFC 9457 application/problem+json whose type URI resolves to a
page in the error registry, because the code set is a published contract
that is never re-pointed. Telephony is BYOK-only in production; there is no
managed-carrier option to compare pricing against. Compliance controls
(AI-call disclosure, internal do-not-call suppression, kill switches) run on
every call through every entry point and are not waivable by any API field,
plan, or support path. On a configured live phone call, an opt-out phrase also
creates the durable internal suppression record before the call closes;
browser sandbox sessions and simulated test calls have no contact to suppress.
A machine-readable summary of this site
lives at /llms.txt.