Where it fits
Telephone carrier
Carrier-side scenario deployment is a separate step. Existing carrier applications do not migrate automatically when an assistant is created.
Configure the connection
Configure the Voximplant application/scenario and account credentials, then associate the carrier route with an APIFleet assistant.
Use the workspace API reference for resource schemas and the configuration guide for carrier and event setup.
Keep provider secrets in workspace credentials. The public MCP provider matrix describes capabilities; it does not connect your provider account.
Test this boundary first
Verify the scenario delivers the expected call identity and audio. Check answer, disconnect and failed-call handling against the call log.
Save a known working configuration and move one test route first. Inspect the call log before increasing traffic. Follow the staged migration guide.
Understand the bill
APIFleet adds $0.03 per connected AI minute, billed per second. Provider and carrier usage are additional. With your own keys, provider charges go directly to the provider. No monthly subscription or free call credits; prepaid top-ups start at $10.