APIFleet Sign in

HTTP tools.
In your voice stack.

Let an assistant call your application for availability, records or other explicit actions.

Where it fits

Business actions

A spoken instruction is not proof of authorization. Your endpoint remains responsible for permission checks and safe retries.

Configure the connection

Create a tool with a JSON parameter schema and your HTTP endpoint, attach it to the assistant, and describe when it should be called. Store sensitive credentials through the documented credential workflow.

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

Test valid results, empty results, timeout and server errors. Give write operations their own idempotency and authorization rules.

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.

Calculate your scenario · HTTP tools documentation

Bring your next conversation.

Explore the API, or sign in to your existing workspace. New workspace access is currently limited; contact us to discuss your project.