Per-vendor guides
Each guide covers when to use the clone, how to connect (SDK, route mode, REST, MCP), seeds, and API coverage. Start with the vendor your app depends on most.
Deep clones
Stateful engines with virtual clock, snapshots, and vendor-correct webhook signing.
Deep clone
Payments, subscriptions, invoices, checkout, and HMAC webhooks.
Deep clone
SMS, Voice, Verify v2, Conversations, and WhatsApp templates.
Deep clone
Resend, SendGrid v3, SMTP capture, and inbox polling.
Deep clone
SendGrid v3 mail send and dynamic templates (runtime kind: email).
Deep clone
Users, sessions, orgs, MFA, and JWKS for sign-in flows.
Shadow clone
Buckets, presigned URLs, lifecycle rules, and multipart uploads.
Fixture clones
Recorded REST fixtures for agent workflows — breadth over billing-clock fidelity. See Fixture overview for shared behavior.
Fixture
Actor runs, datasets, key-value stores.
Fixture
Booking, availability, event types.
Fixture
Teams, folders, lists, tasks.
Fixture
Guilds, channels, messages, interactions.
Fixture
Scrape, crawl, map, search.
Fixture
Repos, issues, PRs, Actions, search.
Fixture
Projects, issues, MRs, pipelines.
Fixture
Gmail, Calendar, Drive, Sheets.
Fixture
CRM contacts, deals, tickets.
Fixture
Issues, boards, sprints, JQL.
Fixture
Issues, projects, initiatives, cycles.
Fixture
Properties, bookings, guests.
Fixture
Listing calendar and dynamic pricing.
Fixture
Cards, transactions, reimbursements.
Fixture
Organizations, issues, events.
Fixture
Messages, channels, threads, users.
Fixture
Projects, branches, migrations, functions.
Fixture
Web search, extract, crawl.
Fixture
Bot API — send, poll, webhooks.
Fixture
Forms, responses, webhooks.
Fixture
Unified inbox and LinkedIn send.
Fixture
Sites, collections, CMS items.
Fixture
Orders, products, customers.
Deep clones vs fixtures
| Tier | Vendors | Best for |
|---|---|---|
| Deep clone | Stripe, Twilio, Email/SendGrid, Auth, S3 | Stateful billing, messaging, auth, and storage — virtual clock, snapshots, webhook signing |
| Fixture | 23 HTTP integrations | Deterministic REST stubs when you need request/response shapes across many vendors |
Full catalog: Supported vendors.
Common setup pattern
- Add a
clones:block in.molar.mdor spawn via MCPmolar_clone_spawn - Point your app's vendor SDK base URL at the clone session URL, or enable route mode
- Apply a seed (
seedon spawn ormolar_clone_seed) - Run scenarios — Trace shows
clone.stateevents at each step
See Clones quick start for the full walkthrough.