Start with the docs
The public quickstart shows the current CLI path: initialize, point at an app, run a scenario, and connect CI.
Use these resources to choose a journey, model its service boundaries, and decide which evidence belongs in CI. Molar's docs and examples are aimed at the moments where a happy path crosses a vendor API and becomes a real product responsibility.
The public quickstart shows the current CLI path: initialize, point at an app, run a scenario, and connect CI.
Clone references explain how payment, email, auth, SMS, and storage behavior can be controlled for tests.
MCP and JSON output references help coding agents discover tools, poll tasks, and inspect evidence.
Begin with one journey, read the relevant clone behavior, then wire the smallest useful run into CI. Expand only after the result is clear.
- status: pending + status: confirmed + receipt: attachedcommit 8e4c · 3 files changed
preview.acme.testSignup and verificationPassed
Invite a teammatePassed
Payment confirmationFailed
Use the docs to choose a journey, understand the relevant clone, and decide which evidence belongs in CI. Contact us when you need help mapping a larger workflow.
Talk through your use casepayment_intent.succeededOpen checkoutScreenshot captured200
Confirm paymentPOST /webhooks/payment200
Receive receiptTest inbox matchedready
Have a specific workflow in mind?
Let’s talk it through
The current docs entry point is https://molar.it/docs, with the hosted product at https://app.molar.it.
Verify one concrete browser claim against localhost, or run one scenario backed by the relevant service clone.
Molar is in private beta. Contact us for current commercial details and a plan matched to your workflow.
Choose a concrete workflow. We’ll help you get the right setup for your application.