Integration

Test Vercel preview deployments with AI agents

Vercel gives every branch a preview. Mimiq sends agents through it when it is ready, including protected previews, and leaves what they hit on the pull request.

5 agents try to .

First test freeRun it from your coding agent

How do I test Vercel preview deployments automatically?

Vercel reports each finished preview to GitHub as a deployment_status event. The Mimiq preview check GitHub Action listens for it, sends AI agents through the preview URL in real browsers, and keeps one comment on the pull request with what broke, failed or slow requests, and where agents got stuck. For protected previews, pass your Protection Bypass for Automation secret.

Protected previews keep testers out

Vercel Deployment Protection is on by default for previews, so outside tools see a login page. Mimiq takes the bypass secret for the run only, sends it as the header Vercel expects, and never shows it in results.

Triggers on Vercel's deployment_status event.
Deployment Protection: pass vercel-bypass-secret.
One pull request comment, updated on each push.
Agents sign in with a test account if pages need it.
Works the same on production URLs.

How it works

01
Create a Mimiq key
Free account, Settings, "Create a key". Save it as the repository secret MIMIQ_API_KEY.
02
Copy your bypass secret
In the Vercel project: Settings, Deployment Protection, Protection Bypass for Automation. Save it as VERCEL_AUTOMATION_BYPASS_SECRET.
03
Add the workflow
Below. Then open a pull request.

The workflow

Vercel previews with Deployment Protection on:

on: deployment_status
permissions:
  pull-requests: write
jobs:
  mimiq:
    if: github.event.deployment_status.state == 'success'
    runs-on: ubuntu-latest
    steps:
      - uses: victorgulchenko/mimiq-preview-check@v1
        with:
          api-key: ${{ secrets.MIMIQ_API_KEY }}
          goal: Sign up and reach the dashboard
          people: 3
          vercel-bypass-secret: ${{ secrets.VERCEL_AUTOMATION_BYPASS_SECRET }}

Without GitHub

Paste the preview URL into the app and add the bypass secret under Access, or let your coding agent pass it to test_flow as access.vercel_bypass.

40steps at most for each agent, each in its own real browser. Every step comes with a screenshot and what the agent was thinking at the time.

20agents at once, each acting as a different one of your users. The browser also records every error, failed request and request slower than 3 seconds on your site, on the step it happened. Agents find problems; they do not forecast how many people will convert.

$0for your first test, with a free account (Google sign-in, no card). It includes 50 credits, enough for 10 agents. After that an agent uses 5 credits, and packs start at $9 for 120 credits.

See a sample report

Questions

Is the bypass secret stored?

It is sealed apart from the test, used for that run only, filled in by the browser, and deleted when the run ends. It never appears in results or reports.

Does it need paid credits?

With paid credits, agents can sign in with a test account you give them and open protected previews (a Vercel bypass secret or a site password). The secrets are filled in only in the browser and deleted when the run ends. Test accounts and protected previews come with paid credits: the $9 Starter or a plan from $19 a month.

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.