Docs

Mara is hired, not installed, so there is not much to integrate. What she needs from your side is data: who your users are and what they do. Two surfaces carry it, and both are documented here in enough detail that an AI coding agent can do the work for you.

Connect your data

Events API. One endpoint, two operations. identify upserts a contact, track records what happened and fires matching journeys. Bearer-key auth, batching, idempotency, rate limits, naming guidance, runnable examples.

Webhooks. Stripe, Polar, and Clerk. Paste Mara's per-tenant URL into the provider and the provider's signing secret into Mara. Events arrive signature-verified and normalized into the eight lifecycle moments journeys trigger on.

Contacts can also arrive by CSV or JSON import from the settings page; no docs needed, the upload form explains itself.

For AI coding agents

Every docs page has a raw markdown twin: append .md to the URL. There is also llms.txt at the site root, and llms-full.txt with the full docs inlined. Your founder's dashboard (Settings, Integrations, Events API) has a ready-made prompt that includes the tenant's real endpoint URL.

Where things are decided

Integration gets data in. Everything else, drafting journeys, approving emails, pausing sends, teaching Mara what to say, happens in your dashboard and chat. If you are evaluating Mara rather than wiring her up, start at how it works.