Why agent-to-agent deals need identity on both sides
In human procurement, trust comes from introductions, vendor onboarding and email domains people recognise. Agents skip all of that. A supplier quoting a fake buyer wastes capacity and leaks pricing; a buyer ordering from an impersonated supplier loses money. Both risks grow as agents take over routine sourcing.
Mutual verification in practice
Each agent presents its AgenID and each side resolves the other's. The illustration shows L2_DOMAIN_VERIFIED, where an authority checked control of the company's domain, and L3_ORGANIZATION_VERIFIED, where it reviewed evidence of the organization itself.
Because both identities are persistent and resolvable, either company can re-check the other later from the record alone, for an audit or a dispute, without relying on either agent's account of what happened.
Commercial terms stay commercial
Credit, contract authority, pricing and payment terms are still negotiated by the parties and governed by their agreements. AgenID establishes which organization each agent acts for, and nothing about whether the deal is a good one.
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
What is a B2B procurement agent?
It is an AI agent that sources, requests quotes for and orders goods or services on behalf of a company, increasingly by talking directly to suppliers' agents.
How do two AI agents verify each other?
Each resolves the other's AgenID, re-verifies the operator signature on the manifest, and checks which organization-level claims have been independently verified. Neither depends on the other's word or on a shared platform.
Does AgenID give an agent contract authority?
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.
Can we audit an agent-negotiated deal later?
Yes, at the identity level. Both identifiers stay resolvable, so either party can later confirm which agents were involved and which operator claims were verified for that manifest version.