ChatGPT.
Ready for voice.

Connect in your client

1. Open the custom MCP server setup available in your ChatGPT account or workspace.
2. Enter the URL below, select No Authentication and review the tool list.
3. Start with provider discovery or a cost estimate. APIFleet does not provide OAuth for private workspace execution; use a Bearer-capable client for that tier.

https://apifleet.dev/mcp

Client setup reference: official documentation. Reviewed 22 October 2026. Client versions and account controls may differ; these are connection recipes, not marketplace listings.

Try one useful request

Estimate the cost of 600 connected AI seconds with $0.04/minute providers and $0.01/minute carrier using apifleet_estimate_call_cost.

The illustrative ten-minute workload returns $0.30 platform + $0.40 providers + $0.10 carrier = $0.80 estimated total. Provider and carrier rates are example inputs, not vendor quotes.

• apifleet_get_provider_matrix: Public, no key: discover implemented voice and carrier integrations, setup boundaries, platform pricing and documentation. No provider request or call is made.
• apifleet_estimate_call_cost: Public, no key: calculate USD platform fees plus caller-supplied blended provider/carrier rates. An estimate, not a provider quote or invoice. Does not place a call.
• apifleet_check_assistant_config: Public, no key: seven static configuration checks. Send a redacted configuration without secrets or customer data. No save, credential verification, full API validation or call-quality certification occurs.

Move into your workspace

Create a key in API keys, then configure Authorization: Bearer <key> privately in a compatible client. A key grants full workspace access. Cookies do not authenticate MCP requests.

Without a key, private tools return ERR_API_KEY_REQUIRED with the key and funding paths. Paid calls retain the prepaid billing checks: $0.03 per connected AI minute plus providers and carrier, minimum $10 funding, no subscription or trial credits.

Read the protocol and authenticated examples. Do not auto-approve paid calls, destructive changes or live route changes.

If the connection fails

Check that the transport is Streamable HTTP and the URL ends in /mcp. A 405 on a browser GET is expected: tools use POST. A 401 with a configured key means the key needs checking; an expired key does not fall back to anonymous access. If your client only supports OAuth or legacy SSE, choose a compatible client or transport.