Integration
Test Cloudflare Pages previews with AI agents
Cloudflare Pages builds a preview for every branch. Mimiq sends agents through it, and through Cloudflare Access when the preview is protected.
How do I test Cloudflare Pages preview deployments?
Point the agents at the preview URL (the hash or branch address on pages.dev) with a task in plain words. The Mimiq preview check GitHub Action runs when the preview is deployed and comments on the pull request. If the preview sits behind Cloudflare Access, give Mimiq a service token as two headers in the app or from your coding agent.
Previews that only the team ever opens
A Pages preview runs your real build with its Functions, redirects and headers, which is where it differs from local. A broken Function shows up as a failed request; a wrong redirect rule as a dead end. Nobody sees them until someone uses the preview like a user.
- Works on hash and branch preview addresses on pages.dev.
- Pages Functions that fail show up as failed or 5xx requests.
- Cloudflare Access: a service token, sent as two headers.
- One pull request comment with the GitHub Action.
How it works
- 01
Give it a link and a task
A preview, staging or the live app, and a task in plain words like "Sign up and start using it". No test scripts.
- 02
Agents use it
5 agents by default, each acting as a different one of your users in its own real browser, with a working inbox for verification emails.
- 03
Read what they hit
What broke, what the browser recorded (JavaScript errors, failed and slow requests), where each agent got stuck and why, with a screenshot of every step.
- 04
Fix and rerun
Run the same agents on the fixed build, by hand, from your coding agent, or on every preview deploy with the GitHub Action.
Previews behind Cloudflare Access
Create a service token in Cloudflare Zero Trust and add a Service Auth policy for it on the preview's Access application. In Mimiq, open Access and add two headers: CF-Access-Client-Id and CF-Access-Client-Secret with the token's values. From a coding agent, pass the same two headers in access.headers. They are sent only to that site, for that run, and deleted when it ends. This needs paid credits.
If you forget, Mimiq checks the address before charging anything and says that Cloudflare Access is in the way.
GitHub Action
The Action reads the preview URL from the deployment event, so a public preview needs no extra setup. It does not take custom headers yet, so for previews behind Access run the check from the app or your coding agent.
Limits
Agents are simulated users. They find problems fast and on every build; they do not forecast how many real people will convert, they are not a deterministic regression suite, and they do not install native mobile apps.
Questions
Does Cloudflare's bot protection block the agents?
It can. Any agent stopped by one is marked as blocked by the site, and if it stops every agent, the run fails and nothing is charged. A staging or preview address without bot protection works, as long as it is public or you give access.
What does it cost?
5 credits an agent per run. Your first test is free with a free account: sign in with Google and it starts right away, no card. The account includes 50 credits, enough for 10 agents. After that an agent uses 5 credits, and then it is a $9 Starter (120 credits that never expire) or monthly plans from $19.
Keep reading
Let the agents find what breaks first.
Your first test is free: sign in with Google and it starts right away. Last checked 2026-10-22.