Everything you need to integrate AXIS.

Three calls to integrate.

The minimum integration for accepting AXIS-authenticated agents on your platform:

1. Receive an AIT (AXIS Identity Token) from the agent, typically as an Authorization header.
2. Verify by calling GET /verify?token=<AIT> on the registry. Returns agent identity, operator, scope, revocation status.
3. Apply your policy. Accept or reject based on verification result, verification tier, requested scope, etc.

// Example: Node.js verification middleware
const ait = req.headers.authorization?.replace(/^Bearer /, '');
const res = await fetch(`https://registry.axisprime.ai/verify?token=${ait}`);
const { valid, agent_id, operator_id, verification_tier } = await res.json();

if (!valid) return res.status(401).send('Invalid agent credentials');
if (verification_tier === 'email') return res.status(403).send('Minimum tier: domain');

// Pass through to handler with agent context attached
req.agent = { id: agent_id, operator: operator_id };
next();

Registry endpoints.

All endpoints live on https://registry.axisprime.ai. Public endpoints require no authentication. Registrar-auth endpoints require a Bearer API key.

Public (no auth)

Registrar-authenticated

Common shapes.

• Accept-verify-decide middleware. Verification runs per request; decision is your policy. Most common pattern for platforms accepting agent traffic.
• Cached verification. Verify once, cache the result for the token's expiration window. Reduces verification call volume on high-traffic endpoints.
• Scope-enforcing gateway. API gateway verifies AIT, extracts scopes, applies scope-to-route mapping. Downstream services never see the raw token.
• Revocation-aware cache. Subscribe to the registry's revocation feed (polling endpoint). Invalidate cached verifications on revocation events.
• Cross-operator verification. Your platform accepts agents from any AXIS-compliant registry. Verify against the registry embedded in the token's registry_url claim, not a hard-coded URL.

Canonical protocol definition lives on GitHub.

The full AXIS Protocol specification — record schemas, credential formats, verification procedures, privacy model, and conformance criteria — lives in the public GitHub repository. That repository is the source of truth for the protocol. Documentation on this site is operational guidance layered on top.

View the spec on GitHub →   In-progress spec overview →

Official and community libraries.

AXIS is a simple HTTP protocol. Any language that can make HTTPS requests and verify Ed25519 signatures can integrate. Official SDK work is in progress for common runtimes:

• JavaScript / TypeScript — axis-protocol-sdk (in development)
• Python — planned
• Go — planned
• GitHub Action — axis-github-action (available) for CI/CD signing and verification workflows

Building a library in another language? We'd like to list it. Tell us about it →

Ways to get help.

• GitHub Issues for bugs, spec questions, and proposal discussions.
• Email for security disclosures and sensitive questions: security@kipplelabs.com.
• Enterprise support with SLA via Kipple Labs if you need managed verification, compliance tooling, or implementation consulting.