Skip to content
Console

The accountability layer for AI agents.

Released

Web Bot Auth proves which key signed a request. AIDR proves which organisation stands behind that key, and lets it be revoked everywhere in minutes.

Signatures
RFC 9421
Agent keys
Ed25519
Open specification
AIAF draft 0.1
Credential lifetime
15 minutes at most

Which side of the request are you on?

I run a website

Verify AI agents for free, on your own server, in five lines. No account, no usage fee.

server.js
npm install @evoliv/aidr-verifier

app.use(aidr({
  issuer: 'https://api.evolivcore.com',
  publicOrigin: 'https://shop.example' }));

I run agents

Give each agent a cryptographic identity tied to your verified organisation: websites and banks can check it, and you can revoke it.

agent.py
pip install aidr-agent

agent = Agent.load_or_enroll(
    "checkout-01",
    audiences=["https://shop.example"])

Why not just Web Bot Auth?

Use it. AIDR works with Web Bot Auth and adds the accountability an enterprise needs.

Web Bot Auth is an IETF draft built on RFC 9421. One setting makes AIDR agents sign in Cloudflare's format; Cloudflare recognises an agent once its key directory is registered there.
Web Bot Auth aloneWith AIDR
Signed requestsRFC 9421RFC 9421, in the same format
Who stands behind the keyWhoever hosts the key directoryA verified organisation with a proven domain
RevocationRemove the key; verifiers' caches decide when it stopsA signed list: refused everywhere in about two minutes
Audit trailNot definedA tamper-evident ledger with published tree heads
Where it verifiesCloudflare's edge, or a library you integrateAny server: Node.js, Python, Go, Workers, Kong, API Gateway, WordPress
PrivacyThe verifier fetches the operator's key directoryVerifiers work offline; the registry never sees a request

A shared key cannot say which agent is calling.

A static API key

  • Anyone holding a copy is the agent.
  • Hard to rotate, so it lives for years.
  • Says nothing about who is accountable.

A cryptographic identity

  • Generated on the agent's device.
  • Only the public key is ever registered.
  • Revoked with one action in the console.

The registry is never in the request path.

The registry

Vouches in advance: a 15-minute credential, published keys and revocations.

  1. Your agent and its gateway

    The gateway signs every request. The agent never holds the key.

  2. Your server

    Verifies the request offline.

Sign a request, then try to change it.

Real cryptography, running in your browser.

The demonstration needs script and a browser that supports Ed25519 in Web Crypto.

The key and signature are real. Nothing is sent anywhere.

Built for the security review.

Device-bound keys

Kept in the operating system's credential store.

A streaming gateway

Constant memory, no size cap on requests.

Revocation in about two minutes

From a passkey-protected console, recorded in your audit log.

Your site, your rules.

Know who is calling

Every verified request names the agent and the organisation accountable for it.

Set the bar for each action

Reading may need little. Checkout may need a verified legal entity. You choose.

Refuse and report

Turn away what falls short. Report abuse, and a revoked agent is refused by every verifying site within about two minutes.

Free, open source, and offline. We never see your traffic.

Your agent keeps speaking plain HTTP.

The local gateway signs each request. No SDK, no code change.

An illustration of the gateway's output
$ curl http://127.0.0.1:8765/v1/orders \
    -H "X-Evoliv-Gateway-Token: $EVOLIV_TOKEN" \
    -H "Evoliv-Target: https://shop.example"
→ signed as agent-01 (RFC 9421) · Agent-Credential attached
HTTP/1.1 200 OK

Give every agent an identity you can revoke.