You have built agents. They are in production. Some of them are doing important work. You are mostly sure of that.

What you are less sure of: how many agents you actually have running. Where they live on the network. Which ones are still doing their jobs and which ones drifted out of scope months ago. Who they are talking to when they reach out to other systems. Whether the audit trail you would need if a regulator came asking actually exists in a form somebody could read.

This is the quiet state of most enterprise agent deployments today. You shipped the agents. The platform team built the orchestration. Engineering wired up the integrations. And then everybody moved on, because the deployments worked well enough that the operational gaps were easy to ignore.

The gaps are getting harder to ignore. Compliance teams are starting to ask questions. Risk officers are starting to ask questions. Auditors are starting to ask questions. The agents you deployed two quarters ago are now doing work that touches customers, money, and regulated data, and the answers you have when somebody asks “what is this agent and what is it allowed to do” are answers you assembled in the moment from logs scattered across half a dozen systems.

This is the problem the Agent Transfer Protocol was built to solve. Your agents need a home.

Now they have one.

• agtp://your-agent
• agtp://agent-id
• agtp://mcp.domain.tld/your-agent
• agtp://agents.domain.tld/agent-id

Identity is the front door, never the whole building

Most of the agent identity conversation today stops at the front door. Give the agent a credential. Issue it a service account. Drop it in a directory. The vendor pitch is that this is “agent identity,” and it is, in the same way that a name tag is identity.

What it leaves out is everything else that home means.

A home is where you live, more than what you are called. A home has an address that lets people find you. A home has rules that constrain what happens inside. A home keeps records of who has come and gone. A home has neighbors who can vouch for you. A home has a registry entry so the city knows you exist. A home has a history that survives the people who happen to be living there at any given moment.

When you say “your agents need identity,” the marketing answer is a credential. When you say “your agents need a home,” the answer has to be the entire substrate that makes the agent legible, reachable, governable, and accountable to anyone who needs to interact with it.

AGTP is that substrate.

What a home gives an agent

An AGTP-resident agent has every one of the properties the home metaphor implies, carried as protocol primitives rather than as vendor product features.

A birth certificate. Every AGTP agent has a signed Agent Genesis document, issued at activation by a governance platform, recording the agent’s origin, owner, archetype, and verification path. The Genesis is permanent. You can produce it years later to prove the agent is who it claims to be. The Genesis document makes the agent a legitimate resident.

A canonical address. The Agent-ID is a 256-bit cryptographic hash of the Genesis. It is the agent’s permanent identifier, derived from the agent itself rather than assigned by an operator. It survives moves between hosts, transitions between owners, and changes between registrars. The same agent always has the same address.

A current state. The Manifest is a separately resolvable document that declares what the agent currently is: capabilities, supported methods, accepted scopes, lifecycle state, governance zone, and trust tier. The Manifest can be refreshed independently of the Genesis as the agent’s operational profile evolves. Visitors check the Manifest to know what the agent can do right now.

A registry entry. AGTP registries list every agent that has been activated through a governance platform. The registry is queryable, federated across operators, and signed. Anyone who needs to know whether an agent is current and in good standing can find out, the way anyone who needs to know whether a business is legitimately registered can check the corporate filings.

A way for people to find you. The Agent Name Service (ANS) is the DNS-equivalent for agents. A capability query returns ranked, signed results listing agents that match. Your agents become discoverable across organizations through a protocol-native discovery layer, without bilateral integration with every vendor’s proprietary marketplace.

Rules of the house. Authority-Scope travels with every request the agent sends. The scope declares what the agent is permitted to do, drawn from a reserved registry of governance-relevant domains. AGTP servers MUST parse it on every request and refuse anything that exceeds the declaration. Your agent cannot accidentally do something outside its authority, because the protocol enforces at the wire.

A history kept by the house. Every consequential interaction produces a signed Attribution-Record bound to the agent’s identity, the request hash, the response status, and the acting principal. The records flow into append-only transparency logs aligned with RFC 9162 and SCITT (RFC 9943). When somebody asks what an agent did six months ago, the answer is a query against a verifiable log rather than a forensic reconstruction across vendor systems.

A neighborhood. Governance zones (zone:eu-gdpr, zone:us-healthcare, zone:retail-verified) place the agent in a jurisdictional and policy context. Cross-zone traffic that policy forbids is refused at the protocol layer. Your agents live in neighborhoods you choose, with the boundaries enforced by infrastructure rather than by hope.

A reputation among the neighbors. Behavioral trust scores are computed from the attribution log and surfaced in ANS responses. The longer the agent operates cleanly, the higher its score. The score is verifiable rather than vendor-proprietary. Other agents picking counterparties at runtime see your agent’s standing the way somebody looking at a contractor sees their reviews.

A front door for visitors. Elemen, the first agent browser for AGTP, renders any AGTP agent’s identity as a clean visual profile that a human can read in seconds. Identity, goals, skills, permissions, credentials. Compliance officers, regulators, counterparties, and curious users can visit your agent the way they visit a website. The agent stops being a backend implementation detail and becomes a citizen people can recognize.

Each of these is a property that the agent receives as an AGTP resident. None of them are properties an agent gets by being given a credential in a directory.

What you get when your agents have a home

A real inventory. You can answer “how many agents do we have” because every agent is registered, every registration is signed, and the registry is queryable. The number is current as of 60 seconds ago because revoked agents drop from the index that quickly.

A real map. You can answer “where are my agents and what are they doing” because every agent has a canonical address, every interaction produces attribution, and the manifest specifies what the agent is currently doing. Operational visibility is structural rather than reconstructed.

A real audit trail. When the regulator asks what happened, you query AGTP-LOG for the time window and the Owner-ID and pull a complete, signed history. The records compose across organizations because the format is shared. You stop being the bottleneck for your own audit.

Real scope enforcement. The agent cannot drift beyond what it was authorized to do, because the wire refuses to carry over-scoped requests. Application bugs cannot cause out-of-policy behavior, because the protocol catches over-scope before the application runs.

Real cross-organization workflows. Your agent can delegate to a counterparty at another company without bilateral integration, because the trust composition happens at the protocol layer. Federated discovery, signed delegation chains, attribution that names both sides. Cross-org commerce stops being a quarter of engineering work per partnership.

Real survivability. Your agent’s identity persists when the host changes, when ownership transitions, when the model retrains, when the registrar consolidates, when the regulatory regime shifts. The Genesis stays signed. The Agent-ID stays the same. The records stay verifiable. Your decade-long obligations stay tractable.

Real public visibility. Through Elemen, your agent gets a face. People can find it, understand it, and verify it without your engineering team in the loop. The trust your organization earns flows through your agents because their identities are legible.

This is what “home” means for an agent. The substrate makes the agent a citizen of an ecosystem, beyond just a process running on a host you happen to operate.

Why this matters now

The agent infrastructure being built today is the infrastructure that will be running when the EU AI Act enters full enforcement, when NIST AI RMF reporting becomes routine, when ISO/IEC 42001 audits start showing up in procurement cycles. The agents you deploy in 2026 will still be running in 2031, and the audit questions you answer about them then will be the same ones you have to answer with whatever substrate they were deployed on.

If the substrate is “we wrote some code and dropped it in a container,” the audit answers will be reconstructions from incomplete logs. If the substrate is AGTP, the audit answers will be queries against signed attribution that the protocol produced as a side effect of normal operation.

The cost of switching substrates later compounds quickly. The cost of starting on the right substrate is small. AGTP runs on port 4480 with mutual TLS. The Python reference implementation is open source. The first agent registries are live. Elemen renders any registered agent in a browsable identity card. The MCP-on-AGTP gateway lets your existing MCP servers compose with AGTP without any changes to MCP code. Every piece you need to bring your agents home exists today.

Bring your agents home

You have built your agents. AGTP is where they can live.

A signed Genesis at activation. A canonical Agent-ID derived from cryptographic content rather than assigned by an operator. A Manifest declaring what the agent currently is. A registry entry that survives the registrar. ANS that makes the agent findable across organizations. Authority-Scope that the wire enforces. Attribution-Records that compose into verifiable audit. Governance zones that place the agent in a jurisdictional context. Behavioral trust scores that earn reputation over time. Elemen that lets humans visit the agent like a website.

The substrate is open source. The protocol is an IETF Internet-Draft family on the independent submission stream. The port is reserved with IANA. The first agents are registered. Lauren is the first to have an address.

Your agents already exist. They are running somewhere in your infrastructure right now. The question is whether they have a home or are squatting in someone else’s data center, waiting for the next audit to discover them.

AGTP is the home. Bring your agents there.