H.164 is an open protocol that wraps phone numbers with structured metadata — capabilities, availability, trust, and activation methods — making every human service provider on earth discoverable, verifiable, and activatable by AI agents.
| Protocol | Layer | What It Connects | Status |
|---|---|---|---|
| MCP (Anthropic) | Agent ↔ Tool | Agents to software tools, databases, APIs | Exists |
| A2A (Google) | Agent ↔ Agent | Agent communication, delegation, coordination | Exists |
| ACP (Stripe) | Agent ↔ Commerce | Product discovery and transactions | Exists |
| H.164 | Agent ↔ Human | Real-world service provider resolution | This Project |
{
"version": "1.0-draft",
"endpoint": "+17138539885",
"entity": {
"name": "John Moore Services",
"type": "business"
},
"capabilities": {
"primary": {
"category": "plumbing",
"subcategory": ["emergency_repair", "drain_cleaning"]
}
},
"availability": {
"tier": 3,
"confidence": 0.65,
"signal_sources": ["google_listing", "published_hours"]
},
"trust": {
"composite": 0.25,
"interaction_count": 0,
"decay_rate": 0.005
},
"activation": {
"methods": [{
"type": "voice",
"endpoint": "+17138539885"
}]
},
"listing_basis": "public_listing"
}An unwrapped phone number is a dead end for an AI agent. No capabilities. No availability. No trust signal. No way to know if calling will resolve the task.
H.164 wraps it with everything an agent needs to discover, evaluate, and activate a human service provider:
Your agent can reason, plan, and use tools. But when it needs a plumber, it hits a wall. Integrate H.164 as an MCP tool and give your agent resolution capability across every service vertical — one integration, every provider.
Read the schema spec →AI agents are already looking for service providers like you. Claim your node, verify your credentials, and control how agents discover and reach you. Set your own consent thresholds — only agents with high trust scores can activate your endpoint.
Claim your node →FSM platforms, voice AI companies, carrier APIs, review platforms — your data enriches the index and the index distributes your providers. Integration means your ecosystem becomes agent-accessible overnight.
Partner with us →The specification is fully open. Anyone can implement the schema, build on the protocol, and contribute HIPs. No permission required.
Outcome events are cryptographically attested via EAS. Trust scores you don't have to take our word for — verify them on-chain.
The protocol evolves through H.164 Improvement Proposals, following the established model of BIPs and EIPs. Community-driven from day one.
Both sides of every interaction carry reputation and set consent thresholds. This isn't a directory — it's consent infrastructure for the agent economy.