Molar’s AI agents test your web app in a real browser, from sign-in and checkout to the emails, payments and webhooks behind them, and show you the step that broke.
Free during the beta · Up to 25 hosted runs a day · No card
A browser, a test account, and a real user goal.
A declined card. A wrong code. An interrupted upload. See what your app should do when a service behaves differently.
payment_intent.succeeded observedThe customer gets access because the test followed the state change all the way through.
Explore the examples, then set up Clones for your own app.
Test those calls with service clones.
Browse 5 stateful clones and 23 API clonesMolar is one browser platform with a product for each job. Cartographer explores your app and records each step. Clones stand in for Stripe, email, SMS and sign-in. Guard runs your checks on pull requests and on a schedule. Trace shows the step behind a failure. Mender, in preview, suggests a fix.
Start with your app’s URL. Explore signup, checkout, and the screens behind them, then inspect the map of what Molar reached.
Explore CartographerDecline a card. Delay a webhook. Read the email in a test inbox. Reset the supported services and run the same case again.
Explore Clones
requires_payment_methodattempt: 21 messageRestore the snapshot. Try the next case.
Run your scenarios against each pull request’s preview, or on a schedule against your live site. Open the failed check to see which customer action broke.
Explore Guardpull/52Follow the recorded steps, screenshots and network log. See the response beside the failed check to understand what to fix.
Explore Trace{
"status": 401,
"error": "code_expired",
"sent_at": "10:02:11",
"entered_at": "10:12:40"
}The code expired before the app accepted it.
Let your coding agent run a browser check, read the result and test its next change.
molar verify "login works" --url http://localhost:3000 --jsonPaste this into Claude Code, Codex, or Cursor from your project.
Set up Molar for this project using https://docs.molar.it/docs/getting-started/for-agents and https://docs.molar.it/docs/getting-started/install. Run npx molar-agent init --json from the project root. Inspect existing configuration before editing it. Follow the documented CLI installation and authentication steps; ask me for any credentials or access you need and never put secrets in source files. Once configured, check that this app loads at its local development URL. Use the documented execution mode that can reach that URL. Read the actual result and captured steps, report any failure or setup blocker, and suggest the next check. Do not claim a check passed without a completed result.
Setup details and testing approaches for the problems your team is working on.
Browse all guidesPayment state, callbacks and the customer’s access—checked together.
Read guideConnect a failed test to the release decision it should change.
Read guideRun the app in a browser, read what happened, and check the next change.
Read guideEnter a URL and describe what should appear. Molar opens the page in a browser and returns its verdict with a screenshot.
Check a public page No signup · Read-only · Public pagesA page you own or have permission to check. Use the supplied example to explore first.
Use the supplied example, or name a heading on your own public page. Molar opens a browser and checks.
See whether the check passed and inspect the captured page. Use the result controls to save or share a completed check.
We’ll help set up the test account, connected services, and checks your app needs during beta.
Have a specific workflow in mind?
Talk to us
Molar opens your app in a real browser and checks tasks such as signing in, submitting a form, or completing checkout. Clones provide test versions of payment, email, SMS, authentication, and storage services for the supported integrations behind those tasks.
You can start with a simple form or page check. Add Clones when you need to test what happens after a payment, verification email, or file upload.
A mock usually returns a prepared response. A clone remembers the records your test creates. For example, create a subscription, advance its clock, and inspect the renewal event. Each clone supports a documented set of service behavior.
Yes. Keep your existing Playwright tests and run Molar browser checks alongside them. Exported tests are plain Playwright and in beta, so review each one before adding it to your suite.
Yes. Molar exposes CLI commands and MCP tools for browser tasks, verification, extraction, and trace inspection. Your agent can read the run status, captured screenshots, and trace details before trying again.
Create a free workspace and describe the first flow to test. Molar is free during the beta, with up to 25 hosted runs a day per organization. We can help you connect your app on a call. To try it without an account, run a check on a public page.
Create a free workspace and describe the flow to test. We can help you set up sign-up, checkout or another test on a call.
Free during the beta. No card.