AgentPKI

v0.1 draft · published 2026-05-21

Cryptographic identity for
AI agents.

An open protocol and edge-verified PKI for the agentic web. Stateless, sub-50 ms, vendor-neutral, chain-agnostic — built so legitimate agents pass bot-defense and the rest stay blocked.

Apache 2.0 · open spec · interop with MCP, A2A, Kite, SPIFFE, OWASP ANS

The trust flow · live
ISSUER anthropic.com Ed25519 · T2 KYB PASSPORT v4.public.eyJpc3MiOi JhbnRocm9waWMuY29t read:* tier: 2 Ed25519 · 24h max VERIFIER verify.agentpki.dev < 50ms p99 · edge mint PASETO v4.public verify RFC 9421 Mode B verdict: allow tier: 2 · abuse: 0.02 cached_until: +60s issuer key kid: anthropic-2026-q2 HSM-resident · rotates 90d

Issuer signs a passport. Agent presents it. Verifier validates it. All in under 50 milliseconds — globally, at the edge.

<50 ms

p99 verify · edge global

Ed25519

RFC 8032 signing throughout

24 h max

passport lifetime · short-lived

3 tiers

DNS · KYB · hardware-attested

The agentic web needs an identity layer it doesn't have yet.

Bot-defense systems — Cloudflare, DataDome, hCaptcha, Arkose — cannot tell a legitimate Anthropic, OpenAI, or Mistral agent apart from a scraper. They either overblock (and frustrate human users whose agents are doing benign work on their behalf) or underblock (and bleed data and revenue to actual abuse).

Every major agent platform is solving identity inside its own ecosystem — MCP authentication, A2A, AP2. None of them are building the cross-vendor neutral layer that the rest of the web needs.

Blockchain-anchored approaches solve the commerce case at the cost of 1–12 second finality, gas fees, and an audit story that won't pass SOC 2 or the EU AI Act. The 90% of agent traffic that isn't commerce — research, scheduling, automation, reading — needs a classical-PKI answer.

Designed to compose.

AgentPKI is the cross-vendor edge identity layer. It plugs into the protocols you already care about — and stays out of the way of the ones you don't.

Each adjacent protocol owns a piece. AgentPKI is the piece that lets any system verify "this agent is who it says it is" without trusting any single vendor — the same role TLS plays for service-to-service trust on the rest of the web.

MCP A2A Kite SPIFFE OWASP ANS
MCP Anthropic A2A Google Kite commerce SPIFFE workloads OWASP ANS discovery AgentPKI cross-vendor edge identity PASETO · Ed25519

How it works

Three participants, one verification path.

STEP 01

Issuer mints

The agent platform signs a short-lived passport with Ed25519 — PASETO v4 envelope, 24h max lifetime, agent identity plus capability scope plus trust tier. Keys live in a managed HSM or hardware-attested enclave.

STEP 02

Agent presents

The SDK attaches the passport to every outbound request — either as a bearer header for simple flows, or via RFC 9421 HTTP Message Signatures bound to the request body. Two lines of integration.

STEP 03

Verifier validates

A Cloudflare Workers edge resolves the issuer public key, verifies the signature, checks the revocation Bloom filter, applies site policy, and returns a verdict — all in under 50 milliseconds, globally.

Built on open standards.

No proprietary crypto. No bespoke tokens. Just the well-vetted primitives the rest of the internet runs on.

See all references →
token
PASETO v4

Platform-Agnostic Security Tokens. Modern alternative to JWT — no algorithm-confusion footgun.

RFC 8032
Ed25519

EdDSA curve. Fast, deterministic, side-channel resistant. The crypto every modern stack agrees on.

RFC 9421
HTTP Message Signatures

Mode B binds the passport to method, URL, and body — kills replay attacks within the signature window.

RFC 8410
Ed25519 SPKI

Standard X.509 public-key envelope. Drop into existing PKI tooling without translation.

license
Apache 2.0 / MIT

Spec under Apache 2.0 (patent grant). SDKs and reference verifier under MIT. Forkable, embeddable, no rug-pull.

planned
W3C VC ready

Credential-envelope abstraction in the spec lets a Verifiable-Credential mode slot in backward-compatibly.

Two lines on each side.

Agents sign with the SDK. Sites verify with a single POST.

Agent side · TypeScript npm: @agentpki/sdk
import { AgentPKI } from '@agentpki/sdk';

const agent = new AgentPKI({
  issuer: 'anthropic.com',
  agentId: 'agent:anthropic.com/research-bot-v3',
  scope: ['read:articles', 'read:public-data'],
});

// Auto-signs every outbound request
// (RFC 9421 Mode B by default)
const res = await agent.fetch(
  'https://reuters.com/api/article/123'
);
Site side · POST to verifier verify.agentpki.dev
POST https://verify.agentpki.dev/v1/verify
Content-Type: application/json

{
  "token": "v4.public.eyJpc3M...",
  "mode": "B",
  "request": {
    "method": "GET",
    "url": "https://reuters.com/..."
  }
}

→ HTTP 200  (21ms warm · 50ms cold)
{
  "verdict": "allow",
  "passport": {
    "issuer": "anthropic.com",
    "tier": 2,
    "scopes": ["read:articles"]
  },
  "abuse_score": 0.02,
  "crl_fresh": true,
  "replay_checked": true
}

live on production infrastructure

Try it live.

Run the mint → verify pipeline against the deployed Workers right now. No signup, no install — one click in your browser.

demo.agentpki.dev/mint verify.agentpki.dev/v1/verify

Runs entirely in your browser. CORS-enabled on both Workers — the page itself has no backend. The demo issuer uses a hardcoded keypair clearly labeled DEMO-ONLY in source; production issuers use HSM-resident keys per spec §5.3.

Who it's for

Agent platforms

Mint passports for your agent fleet. T1 DNS-verified is free. T2 KYB-verified unlocks paid scopes and commerce flows. T3 hardware-attested for high-stakes financial and healthcare use.

Websites & APIs

Verify agents at the edge before serving. Set a policy (minimum tier, required scopes, abuse threshold) and let the verifier decide. Allow, throttle, or deny — your call.

Bot-defense vendors

Drop-in trust signal for your decision pipeline. Native modules planned for Cloudflare, DataDome, hCaptcha, Arkose. Stops false positives on real agent traffic without weakening anti-abuse.

Early access is open.

We're working with a small set of agent platforms, bot-defense vendors, and design partners on the v0.1 spec and reference implementations. Tell us who you are.

We'll respond personally within 48 hours.