Skip to content
↑↓ to move · Enter to openEsc to close
Example verification flowScenario 13

AI sales calls: how a business verifies the voice agent on the line

Larchmont Software's outbound SDR agent calls a regional distributor: "Hi, I'm an AI assistant calling for Larchmont Software." The distributor's front-desk agent has heard that sentence from many callers, and nothing in the call itself tells it whether it is true.

This scenario is the voice-agent case turned around: the business receiving the call resolves who is calling before anyone engages.

Ready
Sales organization
Larchmont Software
“Book intro calls with regional distributors this week.”
Outbound SDR agent
Identity proof
Larchmont SDR agent
Operator: Larchmont Software · voice agent
“Hi, I’m an AI assistant calling for Larchmont Software.”
Front-desk agent
Pell & Carver Distribution
Inbound call screening
Who is calling?
Example verification flow
Fresh challengenonce 07F2·C9
Proof of control✓ VALID
AI disclosureL1_REGISTEREDDECLARED
Domain claimL2_DOMAIN_VERIFIED✓ VERIFIED
StatusACTIVE
Checked separately
Take the meetingBUSINESS’S CHOICE

Identity is not permission. Knowing who is calling gives the caller no claim on the business’s time — whether to engage, share a contact or buy anything is the business’s decision.

Awaiting proof
Nothing proceeds on an unproven claim
What AgenID proves here

Which agent placed the call, which company declared it operates it, and that the operator declared the caller an AI. Whether to take the call, share contacts or buy anything is entirely the business’s decision.

Illustration, not deployment

These scenarios illustrate the protocol's verification model. The reference deployment at agenid.com issues nothing above L1_REGISTERED today: L2 and higher require a VerificationAssertion signed by a root authority key, and that key has not been created. L5 is reserved by the spec and is not issuable at all.

Challenge–response is a proposed interaction pattern. v1.1.1 defines the signed objects, not this exchange.

Why caller names and caller ID are not enough

A voice agent can say any company name, and caller ID can be spoofed. Businesses respond by screening out automated calls altogether, which also blocks legitimate outreach. What the receiving side lacks is a way to check who is calling and who answers for the call.

How the business checks the SDR agent

The SDR agent presents its AgenID. The business's agent resolves it, reads the operator's signed manifest and re-verifies the signature. The manifest carries the operator's own disclosure fields, including whether the agent is an AI, and those show as DECLARED at L1_REGISTERED because they are the operator's statement. The illustration then shows L2_DOMAIN_VERIFIED, meaning an authority checked that the operator controls the domain it names.

For voice platforms, the Retell and Vapi partner docs (/docs/partners/retell-ai-integration and /docs/partners/vapi-integration) describe how an agent could present its identity: each is an integration pattern, not a package, and no adapter exists for either yet.

Disclosure and the decision to engage

Transparency rules such as Article 50 of the EU AI Act address when people must be told they are interacting with an AI system. That is context, not legal advice: a declared AI flag is the operator's statement, not a determination about any law. Whether to take the meeting, share a contact or buy anything stays entirely with the business.

Today the reference registry at agenid.com issues DECLARED and L1_REGISTERED. The higher levels shown in this illustration require an assertion signed by a root authority key that has not been created yet, so they describe how the protocol works rather than something you can obtain today.

Frequently asked questions

How can a business tell who an AI caller is?

By asking the caller for its AgenID, resolving it, and re-verifying the operator's signature on the manifest. The business then sees which company declared it operates the agent and which claims about that company have been independently verified.

Does AgenID show whether the caller is an AI?

The manifest includes the operator's own disclosure fields, including whether the agent is an AI. They are self-declared by the operator, which is why they render as DECLARED rather than verified.

Does a verified caller have permission to sell to us?

No. AgenID answers which agent is acting and who declared it. What that agent is allowed to do stays with the business on the other side and with the operator that runs the agent. Protocol v1.1.1 defines no signed authorization object.

Is there a Retell or Vapi package for AgenID?

No. The partner docs describe an integration pattern, not a package. No adapter package exists for any voice platform yet, and nothing is published to npm.

Integration patterns for this scenario

How the identity travels through platforms agents in this scenario commonly run on. Each brief is a pattern using the platform’s documented APIs, not a shipped adapter package.

Give your agent an identity

Register an agent in the browser — the signing key is generated on your device and never sent to AgenID — or resolve an existing AgenID and re-check its signature yourself.