Run your first check
Follow the setup, authorize a target, and run one concrete browser claim from the terminal.
Find the guide for your next task: run a browser check, connect a test service, or give a coding agent a result it can read.
Follow the setup, authorize a target, and run one concrete browser claim from the terminal.
Clone references show how to control payment, email, auth, SMS, and storage behavior in a test.
MCP and JSON references show how an agent can discover a tool, wait for the result, and open the cited run files.
Install the CLI and check a page. Add the relevant clone for payment, email, or storage. Then read the Guard guide to put the scenario in CI.
$ molar verify "login works" --url http://localhost:3000 --jsontask status · trace referencescreenshots · browser steps inspect and rerunOpen the payment guide for checkout, identity guide for sign-in, or MCP reference for a coding agent. Each link takes you to the next setup step.
Each Clone implements specific service behavior. Confirm the API paths your app uses.
Setup, credentials, and the complete reference.
Testing approaches you can put to work.
Follow what is changing across the product.
Connect the CLI or your MCP client.
Watch a real add-and-remove check with its observed result.
Have a specific workflow in mind?
Talk to us
Open Documentation from the Resources menu for setup instructions and the current CLI, API, and MCP reference.
Verify one concrete browser claim against localhost, or run one scenario backed by the relevant service clone.
Molar is free during the beta, with up to 25 hosted runs a day per organization and no card. The pricing page lists every limit.
Create a free workspace and describe the first flow to test. Or check a public page first, no account needed.
Free during the beta. No card.