AgentKit human verification is only required for x402 sessions. If you’re using the standard Browserbase SDK with API keys, verified browsers are available directly through your plan.
How it works
Register your wallet
Register your EVM wallet address in the AgentBook smart contract on World Chain. This is a one-time setup that links your wallet to a verified human identity.
Sign a proof header
Before each session request, your agent signs an EIP-191 message proving it controls a registered wallet. The signed message includes the target URL, a nonce, and a short TTL for replay protection.
Send with your x402 payment
Include the signed proof as an
agentkit HTTP header alongside your X-PAYMENT header. The gateway verifies the signature, checks AgentBook registration, and upgrades your session.Get a premium browser
If verification succeeds, your session gets Browserbase’s Verified browser — purpose-built Chromium recognized by bot protection partners — the same premium feature available to Scale plan customers.
Session behavior
| Scenario | Browser |
|---|---|
x402 payment, no agentkit header | Standard |
| x402 payment, invalid or expired proof | Standard |
| x402 payment, valid proof from registered human | Verified |
Setup
1. Install dependencies
2. Register in AgentBook
You need a wallet registered in AgentBook on World Chain. Registration requires the wallet holder to be a verified human (Orb-verified via World App).Registration is a one-time on-chain transaction on World Chain (chain ID
eip155:480). Once registered, any agent signing with this wallet’s private key can prove human backing.3. Sign the AgentKit header
Your agent signs a SIWE-formatted message before each request:4. Create a verified x402 session
Combine theagentkit header with your x402 payment:
Server-side verification
The x402 gateway verifies AgentKit proofs in four steps:- Decode — Base64-decode the
agentkitheader and parse the JSON payload - Validate — Check the SIWE message fields, TTL (must not be expired), and target URI
- Recover — ECRECOVER the signer’s address from the EIP-191 signature
- Lookup — Query the AgentBook contract on World Chain (
eip155:480) to confirm the address belongs to a registered human
FAQ
Do I need to be Orb-verified?
Do I need to be Orb-verified?
Yes. AgentBook registration requires the wallet holder to be verified through World App’s Orb verification. This is what makes the proof meaningful — it’s not just a wallet, it’s a wallet linked to a unique human.
Can I use different wallets for payment and identity?
Can I use different wallets for payment and identity?
Yes. The x402 payment wallet (USDC on Base) and the AgentKit signing wallet (registered on World Chain) are independent. You can use the same wallet for both or separate them.
What happens if my proof expires mid-session?
What happens if my proof expires mid-session?
Nothing. The AgentKit proof is only checked at session creation time. Once your session is created as Verified, it stays that way for the session’s lifetime.
Is my identity revealed to websites I visit?
Is my identity revealed to websites I visit?
No. The AgentKit proof is between your agent and the x402 gateway. Websites see a Verified Browserbase browser — they don’t see your wallet address or World ID.
What if I don't include the agentkit header?
What if I don't include the agentkit header?
You still get a working browser session (you paid for it via x402). It just won’t have Verified browser fingerprints. The gateway never rejects a paid request over a missing proof.
Further reading
x402 Quickstart
Set up x402 payments for browser sessions
AgentKit
AgentKit SDK documentation
Agent Identity
How Browserbase handles agent authentication