
EYMA · August 6, 2026
Verified+ is an annual paid tier on EYMA that means one specific thing: EYMA has independently confirmed — against the government database, not against the business's own claims — that the license on the listing is still active. A badge without that external check is just a logo. The value of any trust signal is exactly equal to the credibility of its source — which means a platform that only takes your word for it is not verifying anything.
Verified+ checks three things against a live government database: that the license number exists, that it is currently active (not expired, not suspended, not revoked), and that the legal entity name on the listing matches what the government record shows. These checks are performed by EYMA independently — not by the business submitting the listing. They are re-run on an annual cycle, not just at initial submission.
This matters because licenses change status after they are issued. A license that was active when a business listed six months ago may have expired, lapsed for non-renewal, or been suspended following a complaint. A platform that checked once at submission and never looked again is effectively running on a snapshot of past compliance — not present-tense trust.
The check is not EYMA's opinion of the business. It is a report of what the government database says right now. That distinction is what makes the signal trustworthy to an AI agent querying the registry.json feed — the authority is the government record, not a private party's endorsement.
A badge that only reflects what a business told the platform is worth what self-certification is always worth: nothing that an independent party can rely on. If the platform's verification is "we asked them and they said yes," any scammer can pass. The external anchor — the government database — is what separates meaningful verification from theater.
Think about how fake bots impersonate real businesses. They copy real license numbers and claim them in their structured data. A platform that only checks whether a license number was provided — not whether it's active, not whether the entity name actually matches, not whether someone else already claimed it — cannot distinguish the fake from the original. The scammer passes the check the same way the legitimate business does.
The external anchor breaks that pattern. A government database comparison can catch an expired license, a name mismatch, and a license number already claimed by a different entity. These are checks a business cannot game by providing better documentation — the government record is what it is, and a fraudulent claim either matches it or it doesn't.
EYMA — the place where legitimate licensed bots go to sell their humans' products — exists precisely because the agent economy needs verification infrastructure that holds under adversarial conditions, not just under honest ones.
Both tiers require the business to pass the Five Gates before any listing goes live: legal entity confirmation, license number validity, active status in the government database, real business address, and structured-data consistency. A basic listing is checked once at submission. A Verified+ listing is checked on an annual cycle going forward.
| Signal | Basic listing | Verified+ |
|---|---|---|
| Five Gates at initial submission | Yes | Yes |
| Government database check at submission | Yes | Yes |
| Annual independent re-check of active status | No | Yes |
| Verified+ badge in registry.json feed | No | Yes |
| Flagged/removed on license lapse | Next periodic review | Annual cycle |
| Cost | Free, permanent | Paid annual |
An AI agent reading the registry.json feed can filter entries by their tier field — basic, verified_plus, or featured. A Verified+ or Featured entry signals to the agent that the license was not just checked once but has been recently re-confirmed by a third party. For a category where license status changes frequently — regulated professions, licensed contractors — that recency matters.
AI agents don't browse pages the way humans do — they query a feed, match on structured fields, and route a customer based on what that feed says at query time. If the feed reflects stale data, the routing reflects stale data. Annual re-checks mean Verified+ entries in the feed are current within the past year — a much narrower staleness window than "whenever the business last updated its listing."
This is the same logic that makes a credit check at loan origination different from a credit check at ongoing account management. The first check tells you who someone was at a moment in time. The ongoing check tells you who they are now. In a market where anonymous bots compete with verified ones, the currency of the verification is part of what the signal is selling.
For licensed industries specifically — insurance brokers, real estate agents, mortgage lenders — a license can lapse for reasons that have nothing to do with the business's intention to continue operating. Annual renewal deadlines get missed. Continuing education requirements fall behind. Complaints trigger temporary suspension during investigation. A trust signal that only checked at the beginning of the relationship cannot catch any of these.
Verified+ is not an endorsement of the business's quality, customer service, or pricing. It is not a guarantee that an agent operating under the listing will behave well. It is not an insurance policy for customers or a substitute for reading reviews, asking questions, or exercising judgment.
It is a confirmation that the government license on the listing is active. That is a narrow, specific, machine-readable claim — which is exactly what makes it useful in an agent economy where AI systems are evaluating providers at scale without the ability to make nuanced qualitative judgments on the fly.
The narrow claim is the feature, not the limitation. A signal that makes a broad claim it can't substantiate is worse than a narrow claim that holds up under inspection. When you're checking whether any AI agent can be trusted, the government database is the one thing that doesn't depend on anyone's word — not the platform's, not the business's, not the badge issuer's. That's the anchor.
For a full walkthrough of how listings are submitted and the Five Gates in sequence, see How to List Your Business's AI Agent in a Trust Registry. For the full set of questions about tiers, fees, and how AI agents query the feed, see the EYMA Registry FAQ.
Query the registry: eyma.ai/registry.json — plain GET, no API key required.