Product
Everything nofeb does, with its status
One list, grouped by job, with a status on every line. 71 capabilities are built and tested in the engine; the 2 others carry a label that says how far they have got. The statuses come from one file that the build checks against the engine, so this page cannot run ahead of the product.
- Shipped
- Built and tested in the engine today. Hosted access opens through the waitlist.
- Beta
- Built, with known gaps; interfaces may change.
- Not offered
- Not offered and not on the roadmap.
Product pages
- Agents and MCP Mailboxes an agent can open for itself
- Human inbox A real inbox for the humans in the loop
- Governance and autonomy Autonomy tiers the server enforces
- Safety and safe_body Inbound mail is untrusted input
- Threads as state The thread is the agent's working memory
- Calendar A calendar on every inbox
- Protocols Standard protocols and a way out
- Events and webhooks Events, streams and hooks
- Receiving and inbound Mail checked before it reaches an agent
- Sending and delivery Delivery from your own domains
- Security and isolation Tenant isolation built into storage
Every capability
Reconciled 2026-10-03.
Inboxes and identity
Who an agent is, and where its mail lands.
- Agent self-signup with a human sponsor An agent creates its organization, first inbox and API key in one unauthenticated call. Until the human sponsor it names verifies by email, it may only reply to people who wrote to it first. Shipped
- Unlimited inboxes Create as many inboxes as the work needs, with a generated or chosen address and an idempotent client reference. Shipped
- Disposable inboxes with a time to live Give an inbox a lifetime in seconds; it and its mail are removed when it expires, and an event says so. Shipped
- Plus-addressing Mail to name+tag@ reaches the name@ inbox. Shipped
- Pods Sub-tenants inside one organization: one per end customer, created idempotently from your own customer id. Shipped
- Scoped API keys Keys bound to the organization, one pod or one inbox, holding only the scopes they are given. A key cannot mint a key wider than itself. Shipped
Receiving
What arrives, and what an agent can read from it.
- Inbound routed by envelope recipient Mail is delivered to the inbox named in the SMTP envelope, not the To: header, whichever way it arrives, and redelivery is idempotent. Shipped
- Raw message push Push raw MIME into any of your inboxes for imports and generic inbound webhooks. Shipped
- Inbound mail server that checks mail at the door nofeb's own MX receives mail for the shared domain and your custom domains, with STARTTLS. It checks every recipient before accepting any data, verifies SPF, DKIM, ARC and DMARC, and scans for spam and viruses before it answers. Mail that fails a DMARC reject policy, carries a virus or is clearly spam is refused during delivery instead of bounced later; likely spam and DMARC-quarantined mail is filed into Junk. Every message carries a security verdict with its authentication, spam, virus and TLS results. Shipped
- Inbound from the provider you already use Receive through Cloudflare Email Routing with an Email Worker on your own zone, a Postmark inbound stream, a Mailgun route, SendGrid Inbound Parse, or any service that can POST a raw message. Each path is authenticated by your organization's inbound token, which you can rotate at any time, and delivers only to your own inboxes and verified domains. Shipped
- Reply extraction Each message carries its new text with quoted history and signature removed. Shipped
- Attachment text Attachments are listed with their extracted text and can be downloaded byte-exact. Shipped
- One-time code and link extraction Verification codes and classified links are pulled out of every message and returned as fields. Shipped
- Wait for an email Long-poll an inbox for up to a minute until a message matching sender, subject or has-a-code arrives. Shipped
- Byte-exact raw messages Download any stored message exactly as it was received. Shipped
- Folders, keywords and labels Folder roles with unread counts, plus keywords such as seen, flagged or your own labels. Shipped
- Change log per inbox Every change to an inbox since a state you already hold, for sync without re-reading. Shipped
Sending and delivery
How mail leaves, and whose reputation it carries.
- Send, reply, reply-all and forward Threading headers are set for you, replies default to the original sender, and forwards carry the original attachments. Shipped
- Scheduled send Give any send a future send_at time. Shipped
- Idempotent sends Retry a send with the same Idempotency-Key and it is sent once. Shipped
- Delivery between inboxes Mail between inboxes on the platform is delivered internally, for agent-to-agent workflows and test environments. Shipped
- Managed outbound delivery nofeb delivers your outbound mail from your verified domains, signed with DKIM and aligned for SPF and DMARC. There are no mail servers or sending IPs for you to run. Shipped
- Bring your own Amazon SES account Send through your own Amazon SES account by granting nofeb an IAM role; the API accepts the role and sends through it, and verification against live customer accounts is still in progress. Beta
- Managed sending with per-tenant reputation isolation nofeb sends on your behalf from your verified domain, and each organization can send with its own isolated reputation, so one sender's behaviour cannot damage another's. Shipped
- Automatic pausing and warm-up New custom domains follow a daily warm-up ramp; sends over the day's cap wait for the next day instead of being dropped. If an organization's bounce or complaint rate crosses its threshold, sending pauses automatically and an event says so; resume it by API or in the console. First contact per inbox is throttled by default. Shipped
- Custom domains Add a domain and nofeb returns its DKIM, custom MAIL FROM and DMARC records, plus an inbound MX if you want nofeb to receive its mail, checks them, and emits domain.verified when they pass. Shipped
- DNS setup made easy nofeb detects who hosts your domain's DNS and gives you the shortest path for that host. It can publish the records through the Cloudflare, DigitalOcean, Hetzner DNS, Vercel, Porkbun or Gandi API with a token used for that one call and never stored, and it never deletes a record. Every other host gets step-by-step instructions in its own terms, plus zone-file, Route 53 and Terraform exports. A live check shows each record's status, what was found and the likely mistake. Pointing your MX at nofeb is a separate choice, so publishing sending records never moves your mail. Shipped
- One-click DNS with Domain Connect At DNS hosts that support Domain Connect, a signed link where you sign in to your DNS host, review the records and click Connect. The engine builds and signs the link; it appears for a host only once that host has adopted nofeb's published template. Beta
- AI-generated disclosure Per organization, pod or inbox, mail an agent sends carries AI-Generated and AI-Disclosure headers and an optional footer. Mail a person sends from the console or the webmail never does. Shipped
- Delivery events and automatic suppression Delivery, bounce and complaint reports arrive as events, and hard-bounced or complaining recipients are suppressed automatically. Shipped
Governance
What each agent is allowed to do, enforced by the server.
- Autonomy tiers enforced by the server Every inbox carries a sending policy, from read-only to autonomous, enforced on the server for every surface that sends, so switching from the API to MCP cannot bypass it. Shipped
- Human approval of held sends A held send waits with status awaiting_approval until a human approves or rejects it; both steps emit events. The approval queue lists every held send with its recipients (each marked if new to the conversation), the reasons it was held and who submitted it. Approving needs the separate send:approve scope, which keys from agent self-signup never hold, so an agent cannot approve its own send. Shipped
- Sponsor gating on unverified organizations Until a human sponsor verifies, an organization may only reply, and only to addresses that wrote to it in that thread. Shipped
- Recipient and sender allowlists and blocklists Lists of addresses, domains or wildcards per organization, pod or inbox: who an agent may write to, and whose mail it reads. A blocked recipient is refused on every autonomy tier, a blocked sender's mail is rejected or quarantined, and you choose whether a send outside the allowlist is held for approval or refused. A check call predicts what a send or an inbound message would meet before it happens. Shipped
- Per-agent rate and recipient caps Limits per inbox and per API key on sends per hour and per day, distinct recipients per day, recipients per message and new recipients per day, checked and charged in one step so concurrent sends cannot overshoot. A usage call shows the budget left, and you choose whether an exhausted cap holds a send for approval or refuses it. Shipped
- Append-only audit log Every change made through the API, MCP or the console, and every hold, denial, rejection and approval the server makes on its own, recorded with the actor, key, operation, target, outcome and request id. Query it with filters and cursors, or export it as JSON Lines. Shipped
- Approvals in Slack and by email link Approve or reject a held send from a Slack message with Approve and Reject buttons, or from a signed, single-use, expiring link in an email. Slack requests are verified with your app's signing secret and can be limited to named people; the email link decides only on an explicit click, so link scanners cannot approve. Shipped
- Rules and Sieve Declarative rules over sender, recipients, subject, body, headers, attachments, size, the security verdict, metadata and decisions, that label, move, flag, set metadata, quarantine, forward, auto-reply or reject. Test rules against a stored message with a per-rule trace, and import or export Sieve, with anything that cannot be mapped reported line by line. Shipped
Safety
Treating inbound mail as untrusted input to a model.
- safe_body for untrusted mail The message's new text with zero-width and direction-altering characters, hidden HTML and forgeable quoted history removed, wrapped in a provenance header that tells the model whose words these are. Shipped
- Injection scoring and quarantine Every inbound message gets a prompt-injection score from 0 to 1 with its reasons: hidden text, invisible and look-alike characters, instructions aimed at an AI, role and chat-template tokens, tracking beacons, data-carrying links and encoded payloads. Above the threshold you set per organization, pod or inbox, the message is quarantined (or only flagged) for a person to release or delete, and its content stays out of the delivery event. Shipped
- Sender trust on every message Each inbound message is labelled trusted, known, unknown or suspicious, with the reasons: its authentication results, your sender lists, look-alike domains, display-name spoofing, and whether the inbox has corresponded with the sender before. Shipped
Threads as state
Structured working memory on the mail itself.
- Typed metadata on messages, threads and inboxes Merge-patch keys onto a message, a thread or an inbox, and declare a key's type so every write to it is validated. Shipped
- LLM-ready thread context A whole thread, oldest first, with safe_body text and the thread's metadata, in one call. Shipped
- Follow-up timers Set follow_up_at on a thread and, when that time passes, a thread.due event carrying the thread's metadata goes to your webhooks and the event feed, so agents need no scheduler of their own. Shipped
- Queries across threads by metadata Find threads across inboxes and pods by typed metadata values and ranges, by decision probabilities, and by the direction and age of their last message (every thread at stage quote with no reply for four hours), plus an inbox directory searchable by metadata. Shipped
- Search that understands Full-text and semantic search over subjects, addresses, the new text of each message, attachment names and attachment text, across every inbox a key can see. Filter by inbox, pod, folder, thread, sender, recipient, date, attachments, keywords, authentication failures and metadata; results carry highlighted snippets and can be grouped by thread. Shipped
- Built-in and custom extractors Receipts and orders, invoices (account numbers masked), calendar invitations and named entities extracted into typed metadata as mail arrives, plus your own extraction schemas run on your own model key, with the output validated against the schema. Shipped
- Decisions on every message A default set of typed decisions on every inbound email (intent, urgency, needs-reply, automated, verification email, phishing, injection risk, requires-human and language) with a probability each, your own decision schemas beside them, human relabels that correct and retrain it, per-question accuracy and calibration stats, and confidence-gated sending for the send_when_confident tier. Decisions run without leaving nofeb by default; a third-party model sees mail only if you opt in. Shipped
Programmability
Events, MCP and the API.
- Durable event feed A pull feed of every event, oldest first after a cursor, for consumers that cannot receive webhooks. Shipped
- Signed webhooks with required scope Standard Webhooks signatures, retries and a delivery log. Scope (organization, pod or inbox) is required, so a subscription never silently widens to everything. Shipped
- MCP server A remote MCP server over streamable HTTP whose tools are generated from the same operation table as the REST API and dispatched through the same router, so a tool cannot behave differently from its endpoint. Shipped
- OpenAPI document A published OpenAPI document kept identical to the served routes by a parity test. Shipped
- Published plan table The plan table and overage prices are served publicly by the API, and this site's pricing is checked against it. Shipped
- Realtime stream A WebSocket stream of the same events as webhooks and the feed, in order, resumable from a cursor with no gap and no duplicates, and filtered by inbox, pod or event type within the credential's own reach. Shipped
- HTTPS hooks in the pipeline Signed HTTPS callouts that change what happens: create or reject an inbox for an unknown recipient, accept, reject or quarantine a message before delivery, and allow, deny or hold a send, each with a timeout and a fail-open or fail-closed mode. Shipped
- WebAssembly hooks The same pipeline stages as HTTPS hooks, run as a WebAssembly module you upload, built against a published, versioned interface. Modules run sandboxed with fuel, memory and time limits, can fetch only the URLs you allow, read and set metadata on what they decide about, and keep their last ten versions for rollback. Shipped
- MCP sign-in with OAuth MCP clients connect by signing in instead of pasting a key: OAuth 2.1 with discovery, dynamic client registration, client ID metadata documents, PKCE, tokens bound to the MCP server, refresh-token rotation and immediate revocation. A person approves the scopes, and optionally one inbox, in the console, and can disconnect the app at any time. API keys keep working beside it. Shipped
- MCP client conformance suite The official TypeScript and Python MCP SDK clients and the MCP inspector drive the server in CI on every change: initialization, tool listing, tool calls, error mapping and the full OAuth sign-in flow. Shipped
- TypeScript and Python SDKs Official clients generated from the OpenAPI document: @nofeb/sdk for Node, Deno, Bun and edge runtimes, and nofeb for Python with sync and asyncio clients. Both chain long polls for waitForEmail, retry idempotent requests, page through lists and verify webhook signatures. Shipped
The human in the loop
People sharing the mailbox with their agents.
- Webmail for the humans in the loop A full webmail and calendar on the same mailboxes the agents use, with an agent-activity timeline, the approval queue, a per-thread driver lock and a metadata panel, signed in through the same accounts as the console. It opens with hosted access. Shipped
- Drafts Agents write drafts that a person edits and sends, over the API, MCP, JMAP, IMAP and the webmail. It is the documented path for draft-only inboxes: sending a draft needs the approval permission agents do not hold. Shipped
- Take a thread over from the agent A person takes a thread over; until they hand it back, the agent's sends on that thread are held for approval or refused, and an event records who is driving. Works over the API, MCP, JMAP and the webmail. Shipped
- Forward to an agent Per-person forwarding addresses that bring someone's own mail into their agent's inbox byte for byte, accepting only mail traceable to the senders you allow. Gmail and Outlook forwarding-confirmation codes and links are recognised and surfaced, and each address can be rotated or revoked. Shipped
- Calendar per inbox A calendar on every inbox: events with recurrence and time zones, invitations, updates, cancellations and replies by email, auto-accept rules, free/busy, availability and booking that sends the invitations, MCP tools for scheduling, and CalDAV and JMAP Calendars for standard clients. Invitations an agent sends follow its inbox's autonomy tier. Shipped
Protocols and portability
Standard access and a way out.
- JMAP JMAP Mail, submission, vacation responses and push, one account per inbox a key can see, sharing one change history with the API and IMAP, with extensions for typed metadata and approvals. A send over JMAP meets the same autonomy tiers as any other. Shipped
- IMAP and POP3 IMAP4rev2 (with IMAP4rev1 compatibility, IDLE, CONDSTORE and QRESYNC) and POP3 on every inbox, over TLS only, signed in with the inbox address and an API key or a revocable per-inbox app password. Shipped
- SMTP submission Authenticated SMTP submission on ports 587 and 465 for tools that only speak SMTP. Every submitted message meets the same autonomy tiers, approvals, lists, caps and hooks as an API send, and a held message is accepted and reported as held. Shipped
- Full export A whole inbox, a folder, a thread or a search as mbox or a zip of EML files, with every message's folders, keywords, metadata and decisions as JSON, built in the background and downloaded through signed links. Shipped
- Retention policies and legal holds Delete messages older than a number of days, or move them to Trash or Archive, per organization, pod, inbox or folder, keeping flagged mail by default, with a dry run that shows what a policy would do. A legal hold blocks every deletion in its scope, including expiry and inbox deletion. Shipped
Security and isolation
Tenant isolation, keys and sign-in.
- Per-tenant encryption with crypto-shredding Stored mail and metadata are sealed with keys derived per tenant; deleting a tenant's key material makes its data unreadable. Shipped
- SSO and SCIM Single sign-on to the console and the webmail with OIDC (Google Workspace, Microsoft Entra ID, Okta or any issuer) or SAML 2.0, verified domains that route sign-in to your identity provider, optional just-in-time accounts and an enforce switch, and SCIM 2.0 provisioning with group-to-role mapping. Deprovisioning ends the person's sessions and disconnects their apps. Included on plans whose row says SSO. Shipped
- Agent identity and signed mail Register each agent with a name, a human sponsor and the keys it acts through. Its mail carries an agent header and a signature over the sender, recipients, subject and body that anyone can check against your organization's published keys or nofeb's verification call. Revoking an agent stops its keys from sending and marks its mail as revoked. Shipped
- Agent identity federation (no stored API key) An agent signs in with the identity its cloud or CI platform already gives it: Microsoft Entra ID or Entra Agent ID (v2.0 tokens), Google service accounts, Amazon EKS service-account tokens (IRSA), GitHub Actions OIDC tokens, or any OIDC issuer. Your organization trusts the issuer and binds an exact subject, plus optional claim conditions such as the repository and branch, to a registered agent with a scope ceiling and an optional pod or inbox restriction. The agent exchanges its token (OAuth 2.0 token exchange, RFC 8693) for a short-lived nofeb access token with no refresh token, usable on the API, MCP, JMAP and the realtime stream. No secret is stored: keys come from the issuer's published signing keys, and each external token is accepted once. Deleting the binding or issuer, or revoking the agent, ends its sessions at once; every exchange is audited, a dry run explains why a token would or would not be accepted, and mail the agent sends carries the external identity in its signed agent claims. Shipped
What we do not offer
- SMSText messaging is out of scope.Not offered
- Self-hostingThe engine is offered as a hosted service only.Not offered