outsend documentation

Technical reference for outsend: modules, pipelines, monitoring, API. Built for developers and AI assistants.

This documentation describes the public contracts of every outsend module: what each one accepts as input, what it returns, how it behaves over time, and how modules chain into pipelines.

The goal is twofold:

Help integrators and power users understand what each module does and how to drive it from the UI or the API.
Be readable by AI assistants: every page is plain markdown, downloadable in bulk, exposed through the llms.txt standard.

How to read it

Concepts: start here if you're new. Covers what a job, a pipeline, and a veille are, plus the lifecycle and the events they emit.
Modules: one page per module. Each page is structured: Purpose → Inputs → Outputs → Lifecycle → Limits → Errors.
API reference: every REST endpoint, grouped by domain.
Integration: bring-your-own-key (BYOK), MCP server (planned), llms.txt.

Copy everything in one click

The Copy button in the top-right corner of every page lets you grab:

The current page (raw markdown)
The current section (e.g. all modules pages)
The entire documentation: a single concatenated markdown bundle, ready to paste into Claude, ChatGPT, Cursor, or any AI assistant.

There is also a stable LLM index at /docs/llms.txt and the full bundle at /docs/llms-full.txt: both follow the llms.txt standard, so most AI tools detect them automatically.

Scope

This documentation describes what outsend exposes, not how it is built internally. Implementation details (scraping stack, proxy infrastructure, DOM selectors, timing heuristics, exact success rates) are intentionally omitted. They are not stable contracts and would not help you integrate.

If something you need is missing, write to support@outsend.xyz.