Use case
Autonomous voice agents.
With identity to spare.
Give every agent a DID-bound seat, a scoped session, a route, and a recording policy. Every word it says lands in the same ledger as the rest of your business.
At a glance
What changes for you.
Identity
OAS DID
Lineage from your organization root to the agent seat.
Scope
Per-tool
Read, dial, send, search — granted explicitly per agent.
Guardrail
Per-jurisdiction
Recording disclosure, topic limits, transcript policy.
Audit
Same ledger
An agent call sits next to a human call in the same audit row format.
MCP-native
Your agent calls a tool.
The platform writes a row.
The Dials MCP server exposes every verified path. An MCP-aware agent can search numbers, place calls, and send messages — under the same scope model as a human operator.
- dials.numbers.search
- dials.calls.dial
- dials.messages.send
- dials.agent.smoke
Subject
agent · reception
DID
did:oas:dials:agent:01HQT…
Scope
dials.read dials.dial
Last action
calls.dial.ok · 00:12 ago
Take it for a ride.
Open the console in mock mode and walk the same audited paths a paying customer runs.