Send what happened
identify and track over one typed API, across every app you run. Backfill a year of history without emailing a year of users.
Cowliss
Send events from your app, and write the follow-up emails in TypeScript in your own repo. Cowliss keeps the profiles, the segments, and the waits that last for weeks.
Write the follow-up
defineJourney({ trigger, run }) in your own repo. One run per user, with waits that survive a restart and events delivered as they arrive.
Segments stay current
Rules over traits and event history, recomputed every time a profile changes. Entering or leaving one can start a journey.
Hand it to an agent
Anything the dashboard does, the cow CLI and the MCP server do too, off the same typed API. These docs ship llms.txt and per-page markdown.
Read these docs as an agent
Section titled “Read these docs as an agent”Every page is available as markdown: append index.md to its URL (for example /journeys/index.md). The full index is at /llms.txt and the whole site inline at /llms-full.txt. The API contract is also served as OpenAPI at /openapi.json.
QuickstartInstall the SDK, create an API key, and send your first identify and track.
Projectscow init to cow deploy: journeys and emails as code in your own repo.
API referenceGenerated from the same zod schemas the API validates with.
CLI referenceGenerated from the Cowliss CLI's own command definitions.
CLI and MCP for agentsEverything the dashboard does, without the dashboard.