An agent can sign itself up
One unauthenticated call creates an organization, a first inbox and an API key. The agent names a human sponsor. Until that person verifies by email, the organization may only reply to people who wrote to it first, in the same thread, so a fresh signup cannot be used to send cold mail.
That is enough for the most common first job, receiving a verification code for a sign-up, with no human in the loop until the agent needs to write to someone new.
curl -X POST https://API_HOST/v1/agent/signup \
-H 'content-type: application/json' \
-d '{"name": "research agent", "sponsor_email": "owner@example.com"}' Tools generated from the API, not written beside it
The MCP server and the REST API are generated from one operation table. A tool call is dispatched through the same router as the HTTP request, so a tool cannot validate, authorize or fail differently from its endpoint, and a parity test fails the engine build if the two drift.
117 tools, served over streamable HTTP and named for the job rather than the endpoint: get_thread_context returns a whole thread ready for a model, set_thread_state records where the work stands, wait_for_email blocks until the code arrives, search_email and query_threads find work across inboxes, and find_availability and book_meeting schedule from the inbox's own calendar.
whoamilist_podscreate_podlist_inboxescreate_inboxget_inboxdelete_inboxlist_messageswait_for_emailget_messageupdate_messagesend_messagereply_to_messageforward_messageget_send_statusdecide_sendget_thread_contextget_message_metadataset_message_metadataget_thread_stateset_thread_stateget_inbox_metadataset_inbox_metadatalist_metadata_schemadeclare_metadata_keylist_eventscreate_webhooklist_domainscreate_domainget_domainverify_domainget_dns_setupcreate_hooktest_hooklist_held_sendslist_policy_entriesadd_policy_entryremove_policy_entrycheck_recipientsget_policy_settingsset_policy_settingsget_send_capsquery_audit_loglist_rulescreate_ruleupdate_ruledelete_ruletest_rulesimport_sieveexport_sievelist_quarantinerelease_messagedelete_quarantined_messageget_message_safetyscan_textdecidelist_decision_schemascreate_decision_schemadelete_decision_schemarelabel_decisionextract_messagelist_extraction_schemascreate_extraction_schemasearch_emailquery_threadsfind_inboxesget_hooks_witupload_hook_moduleget_hook_moduleupdate_hook_modulelist_calendarsget_calendar_settingsupdate_calendar_settingslist_calendar_eventscreate_calendar_eventget_calendar_eventupdate_calendar_eventdelete_calendar_eventrespond_to_invitefind_availabilityget_free_busybook_meetingcreate_draftlist_draftsget_draftupdate_draftdelete_draftsend_draftget_thread_driverset_thread_drivercreate_forwarding_addresslist_forwarding_addressesget_forwarding_addressupdate_forwarding_addressrotate_forwarding_addressrevoke_forwarding_addressstart_exportget_exportlist_retention_policiescreate_retention_policydry_run_retentionget_sending_statusget_domain_warmupget_ai_disclosurelist_agentscreate_agentget_agentrevoke_agentverify_agent_signatureget_mail_client_settingslist_federated_issuerscreate_federated_issuerdelete_federated_issuerlist_federation_bindingscreate_federation_bindingdelete_federation_bindingtest_federated_token
Wait for the code, not a polling loop
wait_for_email long-polls an inbox for up to a minute and returns as soon as a message matches the sender, subject or has_otp filter. Every message arrives with its one-time codes and classified links already extracted, so the agent reads a field instead of parsing HTML.
Inboxes can be given a time to live. A browser session, a test run or a single sign-up gets its own address, and the inbox removes itself, with an event, when it expires.
GET /v1/inboxes/{inbox_id}/wait?has_otp=true&timeout=60
{ "message": { "id": "e3KX9Q", "subject": "Your code", "otps": [{ "code": "482913", "source": "body" }], ... } } Connect with a key
Any MCP client that supports remote servers over streamable HTTP can connect with an API key sent as a bearer token. Scope the key to one inbox and the agent cannot see or send from any other.
The TypeScript and Python SDKs are generated from the same OpenAPI document: @nofeb/sdk for Node, Deno, Bun and edge runtimes, and nofeb for Python with sync and asyncio clients.
{
"mcpServers": {
"nofeb": {
"url": "https://API_HOST/mcp",
"headers": { "Authorization": "Bearer YOUR_KEY" }
}
}
} Or sign in with OAuth
Clients that cannot send a custom header, such as custom connectors in claude.ai and ChatGPT, connect by signing in. Give the client the MCP server URL and nothing else: a request without a credential is answered 401 with a pointer to the server's OAuth metadata, the client registers itself, and a person signs in to the nofeb console, picks the organization and optionally one inbox, and approves the scopes the client may use.
The flow is OAuth 2.1: dynamic client registration or a client ID metadata document, authorization code with PKCE, tokens bound to the MCP server they were issued for, and refresh tokens that rotate on every use, where a reused one revokes the whole grant. An OAuth token reaches exactly what an API key with the same scopes would. Connected apps are listed per organization and disconnected with one call, effective immediately. See the claude.ai and ChatGPT guides.
POST https://API_HOST/mcp (no credential)
401 WWW-Authenticate: Bearer resource_metadata="https://API_HOST/.well-known/oauth-protected-resource/mcp"
GET /.well-known/oauth-protected-resource/mcp
GET /.well-known/oauth-authorization-server
POST /oauth/register dynamic client registration
GET /oauth/authorize PKCE S256; a person approves in the console
POST /oauth/token access token and rotating refresh token
POST /oauth/revoke
GET /v1/oauth/grants connected apps
DELETE /v1/oauth/grants/{grant_id} disconnect one Tested against the clients people use
A conformance suite runs on every change to the engine: the official TypeScript and Python MCP SDK clients and the MCP inspector connect to a running server and go through initialization, listing tools, representative tool calls, error mapping, matching structured and text results, and the whole OAuth flow from registration and consent to refresh rotation, step-up and revocation.
Mail an agent can prove it sent
Register each agent with a name, a human sponsor and the API keys it acts through. Mail it sends carries an agent header and a signature over the sender, recipients, subject and body, which anyone can check against your organization's published keys, or by posting the raw message to nofeb's verification call with no key at all. Revoke an agent and its keys stop sending, and its earlier mail verifies as revoked.
Agents that sign in without an API key
An agent running in Azure, Google Cloud, Amazon EKS or GitHub Actions can skip the stored key: it exchanges the token its platform already gives it (Microsoft Entra ID or Entra Agent ID, a Google service account, an EKS service-account token, a GitHub Actions OIDC token, or any OIDC issuer) at nofeb's OAuth token endpoint for a short-lived access token, and uses it on the API, the MCP server, JMAP and the realtime stream. You decide which subject, and which repository or branch, acts as which registered agent, with which scopes and in which pod or inbox; a dry-run call explains why a pasted token would or would not be accepted. Its mail is signed as the agent and names the external identity that acted.
Status of everything on this page
Every capability named above, with its status as reconciled against the engine.
| Capability | What it does | Status |
|---|---|---|
| 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 |
| 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 |
| 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 |
| 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 |
| One-time code and link extraction | Verification codes and classified links are pulled out of every message and returned as fields. | Shipped |
| LLM-ready thread context | A whole thread, oldest first, with safe_body text and the thread's metadata, in one call. | 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 |
| 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 |
| OpenAPI document | A published OpenAPI document kept identical to the served routes by a parity test. | 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 |
| 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 |