mailnix Docs
    mailnix / Docs

    mailnix documentation

    Forms and email for websites without a backend. Design a form and read its submissions, get a working bearer token in one HTTP call, send through any provider, and trace every message end to end. Built to be read by people and machines alike.

    Popularmailnix FormsQuickstartPOST /v1/messagesMCP tool referencellms.txt

    Start building

    Pick a path

    Every path starts the same way: one request returns a bearer token and a sandbox project. No signup required to read these docs or run the quickstart.

    Put a form on your site

    Design it, publish it as a hosted page or embed, and read submissions in an inbox. No backend needed.

    FORMS GUIDE

    Quickstart in your terminal

    One curl for a bearer, one for your first traced send. About sixty seconds, no account.

    GET STARTED

    Connect from an AI agent

    Point Claude, ChatGPT, or Cursor at the MCP server and let the model wire providers and read traces.

    MCP SETUP

    Send from your server

    A drop-in for the SendGrid, Postmark, and SES REST shape. Swap a base URL and a key, keep your code.

    REST API

    Send from the browser

    Publishable keys with origin lock, locked From, rate caps, and CAPTCHA. No backend needed for a form.

    BROWSER GUIDE

    Read by machines

    Docs an LLM can ingest in one fetch

    These docs follow the llms.txt convention. A single Markdown file at the site root gives any assistant a clean, link-rich map of the product, and a companion file inlines the full text so a model can load the whole reference in one request.

    Two files. Zero scraping.

    No HTML to strip, no nav to parse. Point a model at either file and it gets exactly what it needs, kept in sync with every page you see here.

    /llms.txt

    Curated index: structure, key links, one-line summaries.

    /llms-full.txt

    Every page concatenated as plain Markdown, ~310 KB.

    mailnix.ch/llms.txt
    # mailnix

> Forms and email for websites without a backend,
> built to be wired up by AI agents. Two core
> products: mailnix Forms (designer, hosted pages,
> submissions inbox, audited replies) and an email
> service with end-to-end tracing.

## What to grab next
- [Forms guide](/docs/forms): create, publish, embed
- [Styling contract](/docs/forms-styling): .mnx-* classes
- [Full text](/llms-full.txt): every tool + endpoint
- [OpenAPI 3.1](/openapi.yaml): the REST surface

## Concepts
- [Soft sandbox](/docs/concepts/soft-sandbox): capture vs relay
- [Virtual inboxes](/docs/virtual-inboxes): agent test loops
- [Publishable keys](/docs/publishable-keys): browser sends

    MCP tool reference

    A verb-noun tool catalog

    mailnix exposes a Model Context Protocol server with full conformance to spec 2025-11-25. Tool names read like the action they take, so a model picks the right one without guesswork.

    mcp.mailnix.chtransport Streamable HTTPspec 2025-11-25auth Bearer

    Forms

    form_createCreate a form from a schema: fields, validation, logic, theme.Free
    form_publishPublish a form; returns the hosted page URL.Free
    form_submission_waitBlock until a submission arrives, then return it.Free

    Email

    email_send_testSend a message to the sandbox and return a public trace ID.Free
    email_trace_lookupFetch the full event timeline for a trace ID.Free
    email_provider_connectAttach a real SMTP provider or webhoster mailbox to a project.Free

    Virtual inbox

    virtual_inbox_message_waitBlock until a message arrives at a sandbox address, then return it.Free

    Account

    account_claimBind an email to the anonymous token and keep the same project.Free
    account_statusRead session status, plan, and quota usage for the project.Free
    See every tool

    Browse the docs

    Everything, by area

    Forms

    Sending

    Traces & webhooks

    Providers

    MCP

    Suppression & inbound

    Security & data

    Get help

    When the docs run out

    Talk to a human or open the console

    Every send returns a trace ID. Bring it to support and we can see exactly what your code saw.