Lyrie.ai unveils the Agent Trust Protocol (ATP), the first open cryptographic standard for verifying autonomous AI agent identity and authorization.
What the Agent Trust Protocol Sets Out to Solve
As software agents begin to act on their own — calling APIs, moving money, filing tickets, and talking to other agents — the systems on the receiving end need a reliable way to answer two questions: which agent is this, and is it allowed to do what it is asking? Lyrie.ai's Agent Trust Protocol (ATP) is an open cryptographic standard built around exactly that pair of questions, giving each autonomous agent a verifiable identity and a machine-checkable statement of what it is authorized to do.
Traditional access control assumes a human behind every request, or a static API key that is easy to copy and hard to scope. Neither fits an agent that spins up on demand, delegates work to sub-agents, and operates without a person watching each step. ATP treats the agent itself as a first-class principal with its own credentials, rather than smuggling agent actions through a human's session or a shared secret.
How Cryptographic Identity Works in Practice
The core idea is that an agent holds a private key and presents signed proof of identity when it acts. A service that receives a request can verify the signature against the agent's published public identity, confirming the request genuinely came from that agent and was not altered in transit. Because the standard is open, any party can implement verification without depending on a single vendor's servers to vouch for who is who.
Authorization builds on top of identity. Instead of granting broad, permanent access, ATP lets the holder of an identity carry signed grants that spell out scope — which resources, which actions, and under what limits. This makes delegation explicit: when one agent hands a task to another, it can pass along a narrowed grant rather than its full set of powers.
- Identity: a signed, verifiable claim of who the agent is.
- Authorization: scoped grants describing what the agent may do.
- Verification: any counterparty can check both without a central gatekeeper.
- Delegation: agents pass narrowed permissions to sub-agents.
Where It Fits in an Agent Deployment
For teams running agents against real systems, ATP slots in at the boundary between an agent and the services it touches. The agent signs its requests; each service verifies the signature and checks the attached grant before acting. Practically, that means keeping private keys out of prompts and logs, scoping grants to the smallest set of actions a task needs, and treating a leaked key as you would any credential compromise — by rotating it.
An open standard also helps interoperability. If two organizations both speak ATP, their agents can establish trust across a boundary without a bespoke integration, because the format of identities and grants is shared. That lowers the cost of letting agents from different systems cooperate safely.
What to Watch Before Adopting It
A protocol only carries trust as far as its key management and its verification logic. The value depends on keys being generated, stored, and rotated carefully, and on services actually enforcing the scopes in a grant rather than treating a valid signature as blanket permission. Revocation matters too: teams should understand how a compromised or retired agent's authority is withdrawn, and how quickly that change propagates. ATP provides the vocabulary for agent identity and authorization; using it well is a matter of disciplined operational practice around the keys and grants it defines.