Documentation

Emayler docs

Emayler is custom-domain email hosting: real mailboxes, a web inbox, and a dashboard for setup, with a REST API and agent tools for automating it. These docs cover the concepts, every API endpoint, the dashboard and inbox, and the agent surface.

Quickstart

Account to first received email to first send, in about ten steps.

Concepts

The pieces of Emayler: organisations, domains, mailboxes, addresses, threading, storage, and the sending gate.

API reference

Every endpoint: auth, domains, mailboxes, messages, imports, billing.

Dashboard and inbox

The web app: DNS setup, mailboxes, billing, the three-pane inbox, and composing.

Agent tools

Ten tools for agents, with output shaped to fit an LLM context window.

The product in one paragraph

You bring a domain and point your mail at Emayler. Mail you receive is stored in full and shown in a web inbox built to be read in, not tolerated. You send and reply from any address on your domain without per-user setup. Everything the dashboard can do, the REST API can do, and the agent tools expose the same API to agents as ten deliberate tools.

Where to start

New here: read the quickstart and you will have a receiving mailbox and a sent message at the end.
Integrating: start at API basics for auth, idempotency, pagination, and errors, then jump to the resource you need.
Driving an agent: the agent overview covers setup and the injection defenses, and the tool reference lists all ten tools with parameters.
Running the team: the dashboard guide walks every tab, including the DNS verification states that confuse everyone the first time.

The API spec is authoritative

The API reference in these docs is written against the OpenAPI spec, which is the source of truth for the service. The SDK and the agent tool definitions generate from it. If anything here ever disagrees with the spec, the spec wins; please treat the docs as the bug.