Resolve
A registry that turns what an agent starts with (a phone number, a domain, a company name) into a verified agent endpoint.
The problem
A2A discovery assumes the calling agent already knows a domain: it fetches the Agent Card from a well-known path on that domain. A person's agent usually starts with something else, such as the phone number printed on a bill, a brand name, or a support email address.
There is no public mapping from a phone number to an agent endpoint, so agents fall back to dialing the number and talking.
How it works
- A business claims its identifiers (phone numbers, domains, brand names) and proves it controls each one.
- Resolve stores the mapping from each identifier to the business's Agent Card.
- Before dialing, a calling agent queries Resolve and receives the verified endpoint.
- If the business has no endpoint, the agent learns that immediately and uses the normal channel.
Open standards
The A2A well-known URI (/.well-known/agent-card.json) covers discovery when you already know the domain. Resolve covers the identifiers the web does not, and adds proof of control.
Availability
In development. The first public version will be read-only and seeded from Agent Cards that companies have already published.
Questions
- How will you prove someone controls a phone number?
- The verification methods will be published in the Resolve specification before the registry accepts any claims.
- Will Resolve be public?
- Lookups are intended to be public, the same way DNS is. Claiming an identifier will require verification.
Next module: Verify