⚡ TL;DR ChatGPT Work’s cloud browser signs requests with RFC 9421 message signatures. Allow it as ChatGPT Agent in Akamai or HUMAN, or detection ID 129220581 in Cloudflare; Vercel works automatically.
Let AI agents reach your site without weakening your security.
🛡️ How Verification Works
The cloud browser signs requests with Web Bot Auth (RFC 9421), adding Signature, Signature-Input and a Signature-Agent of https://chatgpt.com. Public keys are at chatgpt.com/.well-known/http-message-signatures-directory.
🌐 Provider Settings
Per CDN:
- ✅ Akamai: allow ChatGPT Agent in a custom category
- ✅ Cloudflare: WAF rule for detection ID 129220581
- ✅ HUMAN: allow ChatGPT Agent in Known Bots
- ✅ Vercel: nothing to set up
🔧 Other CDNs
Check that Signature-Agent matches exactly, fetch the public key, verify per RFC 9421 and allow only verified requests.
ℹ️ Capabilities
At launch, the cloud browser cannot sign in to websites or complete payments.
💡 Pro tip Make sure proxies pass the three signature headers through; stripping them is the top cause of blocks.
Want your site ready for AI agents? Lord of the Wix can help. ✨
❓ ChatGPT cloud browser allowlisting FAQ
How are requests verified?
With RFC 9421 HTTP message signatures.
What is the Cloudflare detection ID?
129220581.
Does Vercel need setup?
No.
Which headers must proxies keep?
Signature, Signature-Input and Signature-Agent.
Can the cloud browser log in?
Not at launch.
🙏 Credit: Based on public information from the OpenAI Help Center. ChatGPT is a product of OpenAI. Source: help.openai.com. Lord of the Wix is an independent agency and is not affiliated with OpenAI.