Manav.id
For AI-agent platforms & agentic commerce

“My agent did it” — answered deterministically.

Your platform lets agents act. Manav adds the layer none of the agent standards own: a live human signs one scoped, time-bound, revocable delegation; the agent signs each action under it; the chain verifies back to the human’s passkey — offline, by anyone.

The receipt below was signed and checked in this tab, with zero network calls.

Never in your money pathNo biometric vaultVerify without us, forever
MANAV RECEIPT · v1 network: idle
…
Generating key & signing…
Ed25519 · WebCrypto · in this tab
actionagent.purchase amount USD delegationscope: purchase ≤ $500 · expires 2026-09-30 chain rootmanav:human:7f3a9c…e21b assurancepasskey + liveness challenge issued—
Cryptographic fields
nonce— kid— sig—
Edit the amount. Watch the signature fail.
The loss your customers are carrying
45:1

non-human identities per human employee, median enterprise — up from 17:1 in 2023.

82%

of organizations found an agent that security and IT didn’t know existed.

57.5%

of HTTP requests are now automated — bots overtook humans in 2026.

The gap in the agent stack

OAuth scopes bound what the agent may access. AP2 mandates carry payment intent. Web Bot Auth signs the request. Each proves something real — and none proves a live human authorized the scope. An authorized agent and a hijacked one emit identical traffic; the dispute that breaks agentic commerce is “my agent did it,” and today no artifact answers it across vendors.

Composes with Google AP2 (donated to FIDO, 2026), MCP 2026-07-28 authorization, and IETF Web Bot Auth — we issue the human layer they consume, not a competing protocol.
What fails without it: a hijacked or spoofed agent holds no valid delegation — or is out of scope. Rejected before money moves, with a verifiable reason.
What your platform gains: the answer to the enterprise buyer’s first governance question, portable receipts merchants and auditors verify with one public key, and human accountability without human latency on every call.
Where it sits in your product

Three integration points. Your brand, our receipt.

Delegation issuance

At agent setup, the owner signs the scope from their own device — 30 seconds, once. You store the delegation, not us.

Per-action signing

Your agent runtime signs each consequential action under the delegation. Sub-millisecond, no ceremony, no human in the hot path.

Verification at the edge

Merchants, counterparties and your own policy engine verify the chain offline — no callback to you or to us.

// Before the consequential action, from your backend:
const receipt = await manav.sign({
  action: 'agent.purchase',
  payload: { cartHash, merchant },
  delegation: delegationToken,
  assurance: 'chain→passkey',
});
if (receipt.ceremony === 'completed') proceed(receipt.id);
// Anyone verifies the receipt offline against our published JWKS — forever.
Structurally neutral. The receipt format and verifier are Apache-2.0 open source, filed at the OpenID Foundation and IETF. You embed a standard, not a competitor.
Nothing of yours flows through us. Payloads never leave your systems — only hashes. A Manav outage can’t block your product: issuance pauses, every existing receipt still verifies.
Verification is free for everyone, forever. Your customers’ auditors, banks and counterparties check receipts with one public key — that’s what makes the receipt worth issuing.
We’re early and say so. No fake logos — the mechanism runs in this page. Read the delegation-chain design — honest tradeoffs included →
Try it before you talk to us

Run the ceremony yourself. Then try to fake it.

A controlled sandbox of the exact flow above — your system asks, the enrolled human signs on their own device, a receipt is issued, and you attack it. Real Ed25519, in this tab, nothing sent anywhere.

Next step

A 30-minute integration conversation.

Bring the flow in your product where this belongs. We’ll run the ceremony on it and hand you a receipt you can verify yourself before the call ends — and a straight answer on what an embed looks like commercially.

Step 1 of 2

Talk to us about embedding

No biometrics, no tracking pixels. Your email goes to one inbox and nowhere else.
Step 2 of 2

Where would it sit?

Something went wrong. Email [email protected] and we’ll sort it.
✓

Request received.

You’ll get times from [email protected] within one business day — reply to lock one in.

We’re early, and we’d rather say so than fake logos: the receipt format and verifier are public, Apache-2.0 open source, and the mechanism above just ran in your browser. Judge it before you ever talk to us.