Welcome to NoInfra Mail

Quickstart

Use the console when you want a guided flow, or call the API directly from your product.

1. Open the console and paste a root or scoped API key.
2. Set a customer and deployment context, or create a test workspace.
3. Go to Inboxes, click Create agent inbox, and choose a handle such as support.
4. Send mail to the generated address, or compose outbound mail from the inbox page.
5. Use Webhooks to stream message events back into your product.

Core concepts

Console guide

The console is the fastest way to operate the service as a human.

API examples

All authenticated calls accept Authorization: Bearer <api-key>.

Create an agent with a custom inbox name

curl -X POST https://mail-api.noinfra.ai/v1/agents \
  -H "Authorization: Bearer $NOINFRA_MAIL_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "customerId": "cus_...",
    "deploymentId": "dep_...",
    "name": "Support Agent",
    "externalId": "support-agent",
    "defaultInboxUsername": "support"
  }'

Send email from an inbox

curl -X POST https://mail-api.noinfra.ai/v1/inboxes/inb_.../messages \
  -H "Authorization: Bearer $NOINFRA_MAIL_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": ["[email protected]"],
    "subject": "Hello from an agent",
    "text": "A useful, human-readable message.",
    "labels": ["outreach"]
  }'

Create and send a reviewed draft

draft=$(curl -s -X POST https://mail-api.noinfra.ai/v1/inboxes/inb_.../drafts \
  -H "Authorization: Bearer $NOINFRA_MAIL_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": ["[email protected]"],
    "subject": "Proposed reply",
    "text": "Draft text for review.",
    "labels": ["needs-review"]
  }')

curl -X POST https://mail-api.noinfra.ai/v1/inboxes/inb_.../drafts/$(echo "$draft" | jq -r .id)/send \
  -H "Authorization: Bearer $NOINFRA_MAIL_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

Reply, forward, and label messages

curl -X POST https://mail-api.noinfra.ai/v1/inboxes/inb_.../messages/msg_.../reply \
  -H "Authorization: Bearer $NOINFRA_MAIL_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text":"Thanks, I am on it."}'

curl -X POST https://mail-api.noinfra.ai/v1/inboxes/inb_.../messages/msg_.../forward \
  -H "Authorization: Bearer $NOINFRA_MAIL_KEY" \
  -H "Content-Type: application/json" \
  -d '{"to":["[email protected]"]}'

curl -X PATCH https://mail-api.noinfra.ai/v1/inboxes/inb_.../messages/msg_... \
  -H "Authorization: Bearer $NOINFRA_MAIL_KEY" \
  -H "Content-Type: application/json" \
  -d '{"addLabels":["needs-reply"],"removeLabels":["triaged"]}'

Control send, receive, and reply lists

curl -X POST https://mail-api.noinfra.ai/v1/lists \
  -H "Authorization: Bearer $NOINFRA_MAIL_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "customerId": "cus_...",
    "inboxId": "inb_...",
    "direction": "send",
    "action": "allow",
    "matcher": "domain",
    "value": "example.com"
  }'

curl "https://mail-api.noinfra.ai/v1/lists?customerId=cus_...&direction=send" \
  -H "Authorization: Bearer $NOINFRA_MAIL_KEY"

Stream live events with WebSocket

const ws = new WebSocket(
  "wss://mail-api.noinfra.ai/v1/events/ws?customerId=cus_...&api_key=" + NOINFRA_MAIL_KEY
);

ws.onmessage = (event) => {
  const payload = JSON.parse(event.data);
  if (payload.type === "event") {
    console.log(payload.event.type, payload.event.data);
  }
};

Stream live events with SSE

curl -N https://mail-api.noinfra.ai/v1/events/stream?customerId=cus_... \
  -H "Authorization: Bearer $NOINFRA_MAIL_KEY"

Webhooks

Create webhook endpoints to receive signed callbacks for mail events such as inbound messages, outbound sends, and workflow updates. Delivery attempts are durable and retryable from the console or API.

MCP

NoInfra Mail exposes a hosted MCP endpoint for AI clients that can call JSON-RPC tools over HTTP. Use the same API key you use for the REST API.

{
  "mcpServers": {
    "NoInfra Mail": {
      "url": "https://mail-api.noinfra.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${NOINFRA_MAIL_KEY}"
      }
    }
  }
}

The endpoint supports initialize, tools/list, and tools/call. Tools cover inboxes, messages, replies, threads, drafts, and attachments.

IMAP client access

Email clients and libraries can read agent inboxes through the live NoInfra IMAP listener. The username is the agent inbox email address, and the password is an API key with messages:read access to that inbox.

The IMAP worker supports CAPABILITY, LOGIN, LIST, SELECT, EXAMINE, SEARCH, FETCH, UID SEARCH, UID FETCH, and IDLE. Fetched messages are rendered as RFC822 from the API-backed message store.

SMTP client access

Apps and agent runtimes that already speak SMTP can submit outbound mail through the live NoInfra SMTP submission listener. The username is the agent inbox email address, and the password is an API key with messages:send access to that inbox.

The submission worker supports AUTH PLAIN, AUTH LOGIN, MIME text, HTML, and attachments. It authenticates through the REST API, then submits through the same outbound send pipeline used by the console and API.

Domains & DNS

The shared production domain is agents.noinfra.ai. Custom customer domains require MX, SPF, DKIM, DMARC, A/AAAA, and reverse-DNS alignment before inbox creation is allowed.

Deliverability

NoInfra Mail operates raw email infrastructure: SMTP edge for inbound MX traffic and a direct-MX outbound worker for delivery. SPF, DKIM, DMARC, PTR, queue health, and external auth checks are monitored. Inbox placement still requires warmup and sender reputation over time.

Feature readiness compared with AgentMail-style surfaces