live · agentpki.dev verifying in production · v0.1

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 problem

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

false positives

Bot defense can't tell agents apart from scrapers.

Cloudflare, DataDome, hCaptcha, Arkose either overblock (frustrate humans whose agents are working on their behalf) or underblock (bleed data and revenue to actual abuse). They need a third bucket.

vendor lock-in

Every platform is building its own silo.

MCP, A2A, AP2 — each solves identity inside its own walls. Nobody is building the neutral cross-vendor layer the rest of the web needs to verify an agent that doesn't live in their stack.

wrong trade-off

Blockchain answers a commerce question with seconds of latency.

1–12 second finality + gas fees + an audit story that doesn't pass SOC 2 or the EU AI Act. Fine for settlement; unusable for the 90% of agent traffic that's research, scheduling, reading, automation.

The classical-PKI answer is missing. That's what AgentPKI is — open spec, edge-verified, vendor-neutral, chain-agnostic.

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.

Drop-in on every side.

Agents sign with the SDK. Sites verify with one POST. Bot-defense vendors slot in 30 lines of middleware.

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
}
Bot-defense middleware ~30 LOC drop-in
// Slot into Cloudflare / DataDome /
// hCaptcha / Arkose decision pipelines.
// SIGNAL-only — never overrides yours.

const apkiSignal = async (req) => {
  const token = req.headers
    .get('AgentPKI-Token');
  if (!token) return null;

  const r = await fetch(
    'https://verify.agentpki.dev/v1/verify',
    { method: 'POST',
      body: JSON.stringify({ token }) }
  );
  const v = await r.json();
  return { verdict: v.verdict,
           tier: v.passport?.tier };
};

// → feeds your existing score
score -= (await apkiSignal(req))
  ?.verdict === 'allow' ? 30 : 0;

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.

Claim your domain →

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.

Read the policy spec →

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.

See the 30-line drop-in →
pricing

Free forever to start. Pay only as you scale.

The protocol, SDKs, reference verifier, and bot-defense middleware are Apache 2.0 / MIT open source. We sell the hosted operational layer on top — pick the lane that matches your scale.

tier · open
Free · forever

For individual developers, OSS projects, and small teams self-serving.

T1 DNS-verified issuer — 1 domain, unlimited passports
Self-hosted reference verifier (open source)
SDKs (TS + Python), CLI, all spec docs
Bot-defense reference middleware (30 LOC)
Community support · best-effort uptime
Sign up free →

No credit card · 2-minute setup

most popular
tier · hosted
$99 /mo · per issuer

For SaaS teams shipping agents — hosted issuer, no Worker to run yourself.

Everything in Free
Hosted issuer — we run the Worker, rotate keys, ship the CRL
100k mints/mo included · $0.001/mint after
Dashboard analytics, audit log, abuse pipeline
99.9% SLA · email support · 24h response
Start 30-day trial →

No card during trial · cancel anytime

tier · enterprise
Custom

For banks, regulated industries, bot-defense vendors, and large agent fleets.

Everything in Hosted
T2 KYB + T3 hardware-attested issuers
Dedicated verifier with regional residency
SOC 2 Type II · HIPAA · EU AI Act attestation
99.99% SLA · 24/7 on-call · dedicated CSM
Bot-defense vendor rev-share available
Talk to the founder →

48h response · NDAs available

Who uses which tier

Customer type Typical scale Best-fit tier Outcome they get
Solo dev / OSS project < 10k mints/mo Free Real cryptographic identity for their agent without running infrastructure
SaaS shipping AI agents 10k–1M mints/mo Hosted $99/mo Issue + rotate keys + audit, no Worker to operate. Customers' bot-defense vendors stop blocking their agent traffic.
Website / API operator any Free verifier Distinguish legit AI agents from scrapers at the edge, set a per-route policy
Bot-defense vendor 100M+ verifies/mo Enterprise · rev share Native AgentPKI signal in their decision pipeline, false-positive reduction, co-marketing as "AgentPKI inside"
Bank / regulated enterprise 10–500 issuers Enterprise · T2/T3 KYB-verified issuance, SOC 2 / EU AI Act paper trail, hardware-attested keys, residency control
Agent marketplace / federation multi-tenant Enterprise · federation Cross-org passport scoping (vendor A's agents allowed at vendor B's API under negotiated terms)

Mints/verifies/issuers numbers are guidance, not hard caps. Need something different? Email us — we tailor.

Spin up your own issuer in 3 minutes.

Free DNS-tier (T1) signup. Verify your domain, mint Ed25519 keys, deploy a real-issuer Worker — all from a self-serve dashboard.

Bot-defense vendors, enterprise design partners, and agent platforms — reach out directly at [email protected]. Personal reply within 48 hours.