Who vouches for this AI agent?
Fight impersonating and compromised agents.
Cross-Organizational Agent Verification. A neutral layer where any organization can independently verify another company’s AI agents: who they are and whether they’ve been revoked.
Even when companies integrate, they still can’t tell which agent is acting.
Payments
A company’s payments agent asks its payment provider to change a supplier’s bank details and release a payment.
Trading
A hedge fund’s execution agent requests access to an exchange.
Passport control for AI agents
Check which agent is at your door, not just which company. Checking is a cheap first control, and a public revocation check shows every organization the same answer.
Check an agent yourself
The public verifier reads Meashra’s public registry (Ethereum Sepolia testnet) directly. It calls no Meashra server and needs no account or key of ours. It shows whether an agent is registered, whether it was revoked, and whether a presented DID document matches the chain. Agents not registered with Meashra show as unregistered.
Try it with a demo agent:did:nhim:11155111:0xfccca2b4fde138479d3972fe63f57453002f1456
From agent identity to cross-organization verification
Five steps. Agent identity and revocation can be independently verified by any organization, with the record kept on a public chain. As SSL did for websites, every agent that crosses a company line will need a check anyone can verify.
- ProvisionUnique DID anchored on Ethereum
- CredentialAgent self-signs a verifiable credential
- Policy checkTime and risk rules enforced at the OIDC layer
- AWS accessShort-lived STS credentials issued
- VerifyAny organization checks the agent, no account
What another organization can check
Two checks are live on testnet; authorization and attribution come next.
Who the agent is
Cryptographic proof that the agent presenting itself controls its identity key (its DID), and that it is registered, with block and time. Live on testnet.
Whether it has been revoked
Public, final revocation, with block and time shown. Live on testnet.
Coming next: authorization and attribution
Spending limits and scope per agent, enforced outside the agent, so a manipulated agent can do only so much. Keys held with MPC, first the registry’s signing key, then agent keys, so no single stolen key can sign. Access events anchored on the public chain, so a disputed action can be traced to an agent. KYB linkage to the verified business behind each agent.
Join the early-access list
Independently verify the AI agents other companies send to you. Add your organization for early access to Meashra’s cross-organizational agent verification platform, with a direct line to the founders and a say in how it works. Joining is non-binding, with no fee. The list is open to organizations that receive AI-agent traffic from other companies, such as banks and financial institutions, fintech and crypto platforms, and payment providers.
How it is meant to work: the organization running an agent registers it with Meashra. Organizations that receive its traffic can verify without an account, and can ask their agent partners to register theirs.