Skip to main content

Getting Started with VeriWasp

VeriWasp is an automated playtesting tool for web apps. You give it a URL and a plain-English description of a user flow ("sign up for an account," "add an item to the cart and check out," "invite a teammate") and it launches a real, headless Chrome browser that clicks, types, and navigates through your app the way an actual visitor would. Every interactive step is decided by Claude Haiku 4.5 looking at the live page, not a brittle CSS selector recorded once and left to rot the next time you ship a redesign. That's what "AI wasps crawl your app" means literally, not just as a marketing line: for every click, type, and assert step, an AI model is the thing deciding which element on the page to act on.

At the end of a run you get a shareable report: a stitched-together video replay, a screenshot after every step, any JavaScript console errors that were thrown, a WCAG accessibility scan, and a plain-English list of issues found, all on a public link you can drop into a Slack channel, a build-in-public post, or a bug tracker without asking the person on the other end to log in first.

This page walks through the absolute basics: creating an account and running your first test. Every other page in these docs goes deep on one specific part of the product. Read them in order, or jump straight to the section you need from the sidebar.

Creating an account​

VeriWasp uses magic-link email authentication, so there are no passwords to set, forget, or leak.

  1. Go to veriwasp.com/login.
  2. Enter your email address and click Send magic link.
  3. Check your inbox for an email from VeriWasp containing a sign-in link.
  4. Click the link. You'll be signed in and redirected into the app.

A few details worth knowing about how this works under the hood:

  • The magic link expires in 15 minutes. If it's expired by the time you click it, just go back to the login page and request a new one. There's no limit on how many times you can request a link, beyond a light rate limit (see below) that exists to stop someone from spamming a stranger's inbox.
  • Once you click a valid link, your session cookie lasts 30 days. You won't need to re-authenticate on that browser until it expires or you log out.
  • Login requests are rate-limited per email address (a handful of requests every few minutes) and per IP address, specifically to prevent someone from using the login form to repeatedly email an address they don't own. If you hit this limit, wait a few minutes and try again.
  • The first time an account is created, it's automatically granted a small number of free credits (currently 2) so you can run your first test or two without paying anything. See Billing & Credits for the full picture on how credits work.
  • VeriWasp never asks for or stores a password for your VeriWasp account, and it never stores login credentials for the app you're testing either. More on that distinction in Creating a Playtest Run.

Your first run, in short​

Once you're logged in:

  1. Click Start a playtest (or go to My Runs → New Playtest).
  2. Enter the URL of the app you want to test.
  3. Either pick one of the five built-in scenario templates, or write your own steps from scratch. A "step" is one action, like "click the Sign Up button" or "type the email field."
  4. Review the generated steps, edit anything that doesn't look right, and click Confirm & Create Run. This creates the run in a draft state: nothing has executed yet, and no credit has been spent.
  5. On the run's detail page, click Run this test. This is the point where a credit is deducted and the run is queued for execution.
  6. Watch the run's status update live (the page polls automatically every 2 seconds) as it moves from queued → running → completed or failed, with each step's result appearing as it finishes.
  7. Once it's done, you'll immediately see Re-run, Edit & Re-run, Download, and View shareable report buttons, with no need to navigate away and back.

The next few pages cover every part of that flow: the run creation form, the five action types a step can use, how AI element resolution actually works, what Chaos Mode does, how to read a finished report, and how credits and billing work, in much more detail than a quickstart needs. Read on.