The AEN runs inside your own stack, not as a reverse proxy. Bluemoon is never in the path of your human traffic. See Supported platforms.
What happens on each request
1
Recognise AI crawlers
The AEN checks whether the request comes from a known AI crawler. Bluemoon maintains the list, and your install picks up changes without a redeploy. Anything else gets your normal page, unchanged.
2
Protect your search ranking
Classic search crawlers (Googlebot, Bingbot and Applebot) always get your normal page. See Cloaking firewall.
3
Verify the crawler
The AEN checks that the request comes from an IP address the AI vendor publishes for its crawler. Verified requests are labelled
IP_VERIFIED (Verified in Agent Analytics). A request that only claims to be a crawler is labelled UA_ONLY (Unverified) and always gets your normal page. See Detection and verification.4
Serve, or pass through
If the crawler is verified, its purpose is enabled, your serve mode is
default, and the page has an optimized version, the crawler gets that version. In every other case it gets your normal page.5
Report the visit
The visit is reported to Bluemoon in the background and appears in Agent Analytics. Reporting never delays or breaks the response.
Optimized pages are prepared in advance. Nothing is generated while a crawler waits. If Bluemoon cannot be reached, your install falls back to your normal page.
Authentication
Your install authenticates with an edge token: a secret for one site, which you can revoke without affecting your account or other sites.AEN_EDGE_TOKEN in your host’s environment (for example, in your Vercel project settings). See the Quickstart.
Endpoints
Every install talks to Bluemoon athttps://app.trybluemoon.com/api/v1/edge/, sending the edge token on each call. You only need these if you build a custom integration; the official installs already call them for you.
Supported platforms
- Next.js / Vercel: a self-contained
middleware.tsor the@trybluemoon/aenpackage. See the Next.js Middleware guide. - Cloudflare: a drop-in Worker that runs on your own zone.
- WordPress / PHP: a plugin you upload and activate.
- Any other stack: Node, PHP, Ruby, nginx or Apache through the custom integration snippets.
shadow mode.
Serve modes
New installs start inshadow (Testing in the app): your install logs AI crawler visits but serves your normal page to everyone. Once you see verified hits in Agent Analytics, switch to default (Live) to start serving the optimized version.
See Serve modes for how to switch, and for the
off and canary:<pct> values.