What are the three pricing tiers?
audioMCP.ai offers three tiers. The Developer tier is the entry point, described as launch access, giving you an API key, MCP tool setup, and a sandbox demo flow so you can build and test voice-agent creation through MCP before going to production. The Scale tier is marked most popular and is positioned as an all-inclusive pilot rate that covers telephony, speech-to-text, text-to-speech, and infrastructure with no hidden fees. The Enterprise tier carries custom pricing and is designed for teams that need volume rates, an SLA review, a security review, and dedicated support.
What does the Scale tier cost per minute?
The Scale tier is presented as an all-inclusive pilot rate. The site shows a $0.10 per minute pilot price alongside a $0.15 per minute reference price, with no hidden usage fees during the pilot. To confirm the current rate for your planning, the clearest path is to request your API key and check the rate directly with the team.
What is included in the Scale tier rate?
The Scale tier is explicitly described as all-inclusive with no hidden fees. That rate covers telephony, speech-to-text, text-to-speech, and the underlying infrastructure. It also includes production call scope, usage reporting, and observability hooks so your agent can receive transcripts, outcomes, and call metadata after each call. You are not billed separately for those components.
How does the Developer tier work?
The Developer tier gives you an API key, MCP tool setup, and a sandboxed demo flow. It is designed for building and testing voice-agent creation through MCP before moving to production calls. The site positions this tier as the no-cost entry point. Specific usage caps or time limits for the sandbox are not published in the current product information. The call to action for this tier is to get your API key.
Who should talk to the team about Enterprise pricing?
The Enterprise tier is for teams that need custom volume pricing, a formal SLA review, a security review, or dedicated support. If your use case involves high call volumes, compliance requirements, or you need contractual guarantees around uptime and data handling, the right next step is to talk to an engineer. Enterprise pricing is set through that conversation, not published as a fixed rate.
Why does audioMCP.ai charge per minute instead of per seat?
audioMCP.ai is built on the premise that voice and audio are callable primitives, meaning an AI agent provisions, configures, and deploys a voice agent through MCP tool calls rather than a human developer maintaining a standing platform subscription. Seat-based pricing reflects the model where people are the primary users of a platform. Per-minute pricing reflects the model where usage is driven by automated agent activity, so you pay in proportion to what your agents actually do, not for access that sits idle.
What is the current state of pricing?
audioMCP.ai is in a pre-launch, early-access stage. Pricing is structured around sandbox testing, pilot usage, and custom enterprise terms until production metering is finalized. The figures and tier descriptions published today reflect that stage. If you are evaluating audioMCP.ai for a production deployment, confirming current rates with the team before building cost models is the right approach.
Get started or talk to the team
Developers who want to build and test can get an API key and work through the sandbox demo flow on the Developer tier. Teams evaluating Scale or Enterprise use can book a technical demo or talk to an engineer to discuss volume, compliance, and production requirements.