Per-vendor guides

Deep-clone and fixture vendor documentation for all 28 Molar clone integrations.

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.

Fixture clones

Recorded REST fixtures for agent workflows — breadth over billing-clock fidelity. See Fixture overview for shared behavior.

Deep clones vs fixtures

TierVendorsBest for
Deep cloneStripe, Twilio, Email/SendGrid, Auth, S3Stateful billing, messaging, auth, and storage — virtual clock, snapshots, webhook signing
Fixture23 HTTP integrationsDeterministic REST stubs when you need request/response shapes across many vendors

Full catalog: Supported vendors.

Common setup pattern

  1. Add a clones: block in .molar.md or spawn via MCP molar_clone_spawn
  2. Point your app's vendor SDK base URL at the clone session URL, or enable route mode
  3. Apply a seed (seed on spawn or molar_clone_seed)
  4. Run scenarios — Trace shows clone.state events at each step

See Clones quick start for the full walkthrough.