Not supported

Some paths exist so that clients written for other agent-mailbox APIs get a clear answer instead of a 404. They return 501 not_implemented with a reason:

• not_planned: simail does not offer this.
• phase_2: not offered in this version of the API.

{
  "type": "https://docs.simail.ai/errors#not_implemented",
  "title": "NotImplementedError",
  "status": 501,
  "code": "not_implemented",
  "reason": "not_planned",
  "retryable": false,
  "request_id": "req_…"
}

Endpoints

Path	reason	Use instead
/v0/domains, /v0/pods/{pod_id}/domains and below	not_planned	simail mail domains
/v0/inboxes/{inbox_id}/calendar…, /v0/inboxes/{inbox_id}/files…	phase_2
/v0/apps…, /v0/accounts…, /v0/inboxes/{inbox_id}/accounts…	phase_2
/v0/organizations/labs	not_planned
POST /v0/inboxes/{inbox_id}/authorize	not_planned	API keys scoped to the inbox
POST /v0/inboxes/{inbox_id}/messages/{message_id}/agent-armor/feedback	not_planned
/v0/webhooks/polling and below	not_planned	GET /v0/events
POST /v0/agent/human, POST /v0/agent/verify	not_planned	the claim flow in Private beta

Unknown paths under /v0/ return 404 not_found; a known path with the wrong method returns 405 method_not_allowed with an Allow header.

Things simail does not do

• IMAP or SMTP access, custom (bring-your-own) domains and dedicated sending IPs.
• Open or click tracking. Outbound mail has no tracking pixels and no remote images.
• Cold outreach, bulk mail or newsletters. simail is for expected, transactional mail.
• Bulk or random address creation, and collecting one-time codes for other people.
• Running models for you. No language model reads your mail on the receive path.
• Regulated use: legal, healthcare and financial services are out of scope during the beta.

See the Acceptable Use Policy.