The terms governing access to audioMCP.ai's MCP-native voice-agent infrastructure. By using audioMCP.ai, customers are responsible for lawful use of voice-agent workflows, including consent for outbound calls, call recording, transcription, message content, and tool actions triggered by their agents. These terms are written for a launch-stage B2B developer platform and require counsel approval before publication.
Effective date and acceptance
Effective date: June 1, 2026. These Terms apply to access and use of audioMCP.ai, including the website, APIs, MCP server, demo tools, documentation, and related support.
A customer accepts these Terms by creating an account, requesting access, using an API key, connecting an MCP client, or otherwise using the service.
The service
audioMCP.ai provides MCP-native infrastructure that allows AI agents to create, configure, deploy, and observe voice-agent workflows. The service may include tool calls, prompts, routing, telephony integrations, speech-to-text, text-to-speech, transcripts, logs, and analytics.
Features may be released as alpha, beta, pilot, or preview functionality. Preview features may change, break, or be discontinued without the same commitments as generally available features.
Accounts and API keys
Customers are responsible for all activity under their accounts, API keys, MCP clients, and integrations. API keys must be kept confidential and may not be shared publicly, embedded in client-side code, or used by unauthorized users.
audioMCP.ai may suspend or rotate credentials if it detects abuse, compromised keys, unusual traffic, or risk to the service.
Acceptable use
Customers may not use audioMCP.ai for spam, fraud, phishing, harassment, unlawful surveillance, impersonation, deceptive calls, emergency services, regulated professional advice without appropriate controls, or any activity that violates law or third-party rights.
Customers may not bypass rate limits, probe or attack the service, scrape non-public systems, reverse engineer restricted components, or use the platform to generate or distribute harmful content.
Calling, recording, and consent
Customers are solely responsible for obtaining and documenting all consent required for outbound calls, automated calls, call recording, transcription, text messages, and follow-up communications.
Customers must comply with applicable telemarketing, consumer-protection, privacy, recording, and communications laws, including TCPA-style consent rules in the United States where applicable. audioMCP.ai may require verification, opt-out handling, rate limits, and use-case review before enabling production outbound calling.
Customer content and agent behavior
Customers control prompts, instructions, tools, workflows, data sources, and business logic supplied to their agents. Customers are responsible for testing agent behavior, monitoring outputs, and preventing unauthorized or harmful tool actions.
audioMCP.ai may process customer content only to provide, secure, support, and improve the service, and as otherwise described in the Privacy Policy or a signed agreement.
Fees and billing
Launch access may be free, pilot-based, or custom-priced. Production usage may be billed by minutes, calls, agents, phone numbers, speech usage, or another metering unit stated in an order form or pricing page.
Unless otherwise stated in writing, fees are non-refundable, exclusive of taxes, and payable according to the invoice or order terms. Customers are responsible for taxes, carrier charges, and third-party usage charges passed through or bundled into the service.
Service levels and support
Any uptime commitment, service credit, support response time, data residency commitment, or dedicated capacity obligation applies only if stated in a signed order form, enterprise agreement, or SLA addendum.
Without a signed SLA, the service is provided on a commercially reasonable efforts basis, especially during beta, pilot, or preview periods.
IP and data ownership
Customers retain ownership of their prompts, configurations, customer data, call content, transcripts, and outputs, subject to the rights needed for audioMCP.ai to provide the service.
audioMCP.ai retains ownership of the platform, software, APIs, MCP tools, documentation, models or orchestration logic owned by audioMCP.ai, trademarks, and service improvements.
Security and compliance
Customers must use reasonable security controls, restrict account access, protect API keys, and promptly notify audioMCP.ai of suspected compromise.
Customers are responsible for determining whether the service is appropriate for regulated data or regulated calling use cases. audioMCP.ai should not be used for production regulated workloads unless the required security, compliance, and contractual terms are in place.
Disclaimers and limitation of liability
Except for commitments expressly stated in a signed agreement, the service is provided as is and as available. audioMCP.ai disclaims implied warranties to the maximum extent permitted by law.
To the maximum extent permitted by law, audioMCP.ai will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, lost data, or business interruption. Any liability cap should be finalized by counsel before launch.
Suspension and termination
audioMCP.ai may suspend or terminate access for non-payment, security risk, legal risk, abuse, violation of these Terms, or conduct that could harm users, third parties, carriers, providers, or the service.
After termination, customers should stop using the service and delete credentials. Data export and deletion rights depend on the applicable plan, retention settings, legal obligations, and backup practices.
Changes and governing law
audioMCP.ai may update these Terms as the service evolves. Material changes should be posted with a new effective date and, where appropriate, notice to active customers.
Governing law, venue, dispute process, and arbitration or class-action provisions should be finalized by counsel before publication.