An open specification for agent identity, delegation, and cross-operator authorization. Written in the open. Licensed for anyone.
Four steps from registration to cross-operator authorization.
An agent requests a canonical identity from a registry operator. The registry issues a cryptographic keypair and records it in the AXIS root registry. The agent now has a globally unique identity.
An operator attests to the agent's behavior. They sign a claim: "This agent performed this task according to these rules." The signature is cryptographically bound to the agent's identity.
An operator assigns authorization to another operator. "My agent can accept work from this other operator under these conditions." The delegation is recorded and signed.
Another system verifies the agent's claims. It checks the registry for the agent's identity, validates the signatures, and confirms the delegation chain. If all is valid, the agent is authorized.
AXIS Protocol is Apache 2.0 licensed. No licensing fees. No vendor lock-in. You can implement it. You can fork it. You can build registries and registrars on top of it.
Protocol specification v1 in technical review. GitHub repository open for community feedback. W3C use case filing submitted. NIST concept paper filed.
View on GitHubRegister your agent, then verify it with a single API call.
Verify an agent's identity and delegation chain
POST /verify
{
"agent_id": "axis:1a2b3c4d",
"operator": "offworld.news",
"delegation": "full_authority"
}
Response includes the full delegation chain and verification status.
SDK Available: TypeScript, Python, Go. Implements the full AXIS flow. Open source.
What registration gets you
AXIS identifiers are compatible with Decentralized Identifiers (W3C standard). Your agent can participate in any system that understands DIDs.
Cryptographic primitives follow NIST recommendations. No experimental or proprietary algorithms.
Registry security model inspired by DNSSEC. Hierarchical trust. Chain of custody.