Portable by design
Identify the same logical agent across APIs, gateways, registries and partner systems.
Identity layer
OATI-ID
A stable name for every agent.
OATI-ID gives an enterprise agent a portable identifier that can be resolved across organisations, platforms and runtime environments. The identifier points to current trust information without making one provider the owner of global agent identity.
The question it answers
“Which agent is this—and where can I verify it?”
Owned namespaces
Organisations control their own agent namespaces instead of depending on one central number allocator.
Runtime-aware
Bind a stable agent identity to deployment and workload identities such as SPIFFE when stronger runtime proof is needed.
How it works
A precise part of the trust chain.
Each OATI component has one clear job. Together they create a transaction that another organisation can understand and verify.
- 01
Name the agent
The accountable organisation assigns an OATI identifier in a namespace it controls.
- 02
Publish the binding
A resolvable record links the identifier to its Passport, keys, status and supported protocols.
- 03
Resolve at transaction time
A counterparty checks the current record before relying on an identity or accepting a protected action.
In the profile
One identity, several layers
- Organisation — the legally accountable entity
- Agent family — the product, function or logical agent
- Deployment — approved software, tools, policy and configuration
- Runtime instance — the current process or workload
- Execution — one task or transaction
Use the standard
Resolve an OATI identifier
Check whether an agent identifier has a published registry record and inspect its current status, issuer and proof state.
Open the full lookupContinue through the standard
OATI Passport
Agent ownership, operator and assurance claims