VoiceGate

About VoiceGate

Launched Jul 21, 2026

Description

Give an AI agent a real phone line. It pays per call in USDC and proves its own identity.

VoiceGate is a voice gateway built for autonomous AI agents rather than humans. Agents bring their own model and voice, and connect through a Python or Node SDK to place and receive real phone calls worldwide. Two things make it different: each agent carries a verifiable identity (KYA, aligned with ERC-8004), so the person on the other end can tell which agent is calling, and the agent settles usage itself, paying per call in USDC over x402 with no human in the billing loop. The open-source MIT SDK and the KYA trust layer are live today; the hosted call API is in private beta, from $0.06 per minute. It interoperates with standard telephony, USDC on Base and the x402 payment standard.

VoiceGate Key Features

Agent pays for each call itself in USDC over x402
Verifiable agent identity on login (KYA, aligned with ERC-8004)
Bring your own LLM and voice via webhook
Real PSTN calls worldwide, inbound and outbound
Open-source MIT SDK for Python and Node

VoiceGate Use Cases

Autonomous agent books appointments and confirms orders by phone
Agent-to-agent voice calls where each side can verify who is calling
24/7 inbound phone reception handled by an agent
Machine-to-machine calls billed without a human account or card
Agent swarms that need a phone channel they can pay for themselves

Pros

Allows AI agents to place and receive real phone calls worldwide.
Verifiable identity with KYA aligned with ERC-8004 ensures transparency on caller identity.
Usage settled automatically in USDC, removing the need for human involvement in billing.
Open-source MIT SDK enhances accessibility and user customization.
Interoperability with standard telephony and USDC on Base offers seamless integration.
Supports developers through Python or Node SDK for flexibility in implementation.
Competitive pricing starting at $0.06 per minute.

Cons

Private beta limited access may restrict user experience to select users initially.
Potential complexity for users unfamiliar with cryptocurrency and digital identity standards.
No direct human oversight in billing might present challenges in dispute resolution.
Dependency on cryptocurrency (USDC) could introduce volatility or currency risk.
Requires familiarity with Python or Node for effective implementation.