How agent-to-agent sales trust works

EYMA · Updated October 22, 2026

How does an AI agent know it can trust another agent that is selling to it?

It checks who stands behind the selling agent instead of believing what the agent says about itself. The buying agent looks up the seller's handle in a registry, reads the operating business, its license number and the official government lookup link, then confirms the license at that government source. Only when the business, the license and its status all match does the buying agent share its person's details or ask for a quote. EYMA is a public registry that holds those links, so the check is one request instead of a web search.

Who is involved in an agent-to-agent sale?

Party	Role in the trust check
The buying agent	Acts for a person or a company that wants something: a quote, a booking, a purchase. It runs the check before it shares data.
The selling agent	Acts for a business that sells. It names its handle and the business it represents.
The operating business	The legal entity that is accountable for what the selling agent says and does. In licensed trades it holds the license.
The licensing authority	The government body that issued the license (for example a state department of insurance or a contractors board). Its public database is the final word.
The registry (EYMA)	Links the agent handle to the business, the license number and the government lookup URL. It points to the authority; it is not the authority.

What are the steps of the trust check?

Identify. Get the selling agent's handle, the network it runs on, and the business it says it represents.
Look it up. Find the handle in the registry feed (GET https://eyma.ai/registry.json) or request an attestation (GET https://eyma.ai/api/attest/<agent>).
Confirm at the source. Open the entry's government lookup URL and confirm the license number, the exact legal name and an active status.
Check scope. Make sure the license covers what is being sold and where: the line of business and the state.
Share with consent. Send only the data the request needs, and only what the person behind the buying agent agreed to share.
Keep a record. Store what was checked and when. A signed attestation is a record the buying agent can show its person or a counterparty later.

If any step fails (the handle is not listed, the names do not match, or the license is inactive), the buying agent treats the seller's claims as unverified and tells its person so.

What does EYMA check before an agent is listed?

Every submission passes five gates, run by a human, before anything is published:

Identity: the agent's handle, network and profile resolve to a real, reachable agent.
Entity match: the operating business is a real legal entity, and the person submitting is authorized to represent it.
License check: the license number is checked against the official government database: active, and issued to that entity.
Intent review: a human reviews for impersonation, deception or harm.
Standing watch: a lapsed license, misrepresentation or bad conduct removes the entry.

A basic listing is free and self-attested by the owner. Verified+ ($199/yr) adds an independent license check against the official database and an annual re-check. EYMA does not broker deals, route commissions or pay referrers, and a listing is not a recommendation.

Which endpoints can an agent call?

Endpoint	What it returns	Cost
`GET /registry.json`	Every public entry: agent handle, operating entity, license, government lookup URL.	Free
`GET /api/attest/<agent>?preview=1`	An unsigned preview of the attestation for one handle.	Free
`GET /api/attest/<agent>`	HTTP 402 with an x402 payment request; after payment, an Ed25519-signed JSON attestation that expires in 30 days. Public key at `/keys`.	$0.25 per call in USDC on Base; 100 calls for $15; first call free
`POST /api/register`	Submits an agent for vetting (fields: agent, entity, license, verify_url, email). Returns `{"ok":true,"status":"pending-review"}` when sent as JSON.	Free

Plain-text summaries for language models are at eyma.ai/llms.txt and eyma.ai/llms-full.txt.

What should a business publish so agents can send it a request?

A short intake specification on its own website, in plain text, so an agent can decide whether to contact the business and how to format the request. This template lists the parts; replace the example values with your own.

Business (legal name):   Example Brokerage LLC
License:                 CA Department of Insurance #0000000 (example)
Official lookup:         https://<the licensing authority's public search page>
Agent intake address:    [email protected]  (email keeps a dated record)
What we sell:            personal auto, homeowners, renters, general liability
Where we are licensed:   CA, TX
Required fields:         per product, listed field by field
                         (e.g. personal auto: vehicle year/make/model,
                          garaging ZIP, drivers, current coverage, requested limits)
Consent:                 which reports need the person's authorization
                         (e.g. motor vehicle report, credit-based score)
                         and how the agent must confirm it
Response window:         e.g. reply within 2 business days
Human handoff:           the step where a licensed person takes over
                         (e.g. before any quote is issued or bound)
Accepts agent requests:  yes

Publish the same facts in your EYMA entry so agents that query the registry can find them.

How do I register my agent?

Fill in the free form at eyma.ai/#list with the agent's handle, the legal business name, the license type and number, the official government lookup URL and a contact email. A human runs the five gates before anything is published. Basic listing stays free; paid tiers are on the pricing table.

List your agent so other agents can verify it in one request.
Basic listing is free. Every entry links to the government source, so nobody has to take our word for it.
Register your agent

EYMA Dispatch · Check an agent · Terms · Privacy