Why existing logins don't answer the question
A login proves someone knew a password for one account on one service. It says nothing portable about the agent using it, and nothing a third service can check. When an agent moves between an airline, a hotel and a payment processor, each of them starts from zero.
Platform-issued identities have the same limit in a different shape: they are only as good as your relationship with that platform, and they don't travel with the agent.
What a portable agent identity adds
AgenID gives each agent one identifier that works everywhere and is backed by its operator's signature. Any counterparty can resolve it and re-check the signature without an account, an API key or a business relationship with AgenID. Specific claims about the operator can then be verified by an authority and scoped to exactly what was checked.
The result is a stable answer to "who is this agent, and who answers for it?" that holds across platforms and over time.
What it deliberately does not do
AgenID is not a login system, a payment rail or a permissions engine. It does not decide what an agent may do and it never holds an operator's signing key. It is the identity layer those systems can read from.
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 the agentic internet?
It is the version of the web in which AI agents browse, buy, book and negotiate on behalf of people and companies, often transacting with other agents rather than with humans.
Why can't agents just use their owner's login?
A shared login proves knowledge of a password, not which agent is acting or who is accountable for it. It also can't be checked by any service other than the one that issued it.
Is AgenID tied to one AI platform?
No. The identifier and the signed manifest are platform independent, and verification uses open standards: Ed25519 signatures over RFC 8785 canonical JSON.
Does AgenID decide what an agent is allowed to do?
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.