Skip to content
nofeb

Give an AI agent its own email address

Call POST /v1/agent/signup with a name and a human sponsor's email. The response holds an API key and a working inbox address. The agent can receive immediately and reply to anyone who writes first; once the sponsor verifies by email, it can start conversations too, within its inbox's autonomy tier.

Checked against the engine on .

What do you need?

  • A human who will sponsor the agent (an email address they read)
  • curl, or the TypeScript or Python SDK

Steps

  1. 1. Sign the agent up

    One unauthenticated call creates the organization, a first inbox and an API key. The key is shown once; store it where the agent keeps secrets.

    Agent self-signup
    curl -X POST https://api.nofeb.com/v1/agent/signup \
      -H 'content-type: application/json' \
      -d '{"name": "research agent", "sponsor_email": "owner@example.com"}'
    
    { "org_id": "org_…", "api_key": "nfb_…", "key_id": "key_…",
      "inbox": { "id": "inb_…", "address": "research-agent@agents.nofeb.com", … } }
  2. 2. Use the address

    Give the address to whatever needs to reach the agent: a sign-up form, a vendor, a colleague. Mail arrives within the same pipeline as every other nofeb inbox, parsed for a model.

  3. 3. Read what arrives

    Block until the next message, or subscribe a webhook. Every message carries reply_text, safe_body, one-time codes and links.

    Wait for the next message (TypeScript)
    import { Nofeb } from "@nofeb/sdk";
    const nf = new Nofeb({ apiKey: process.env.NOFEB_API_KEY });
    
    const { message } = await nf.inboxes.waitForEmail(inboxId, { timeout: 60 });
    console.log(message?.safe_body.text);
  4. 4. Reply in the thread

    Replies keep the thread: nofeb sets In-Reply-To and References. Until the sponsor verifies, the agent may only reply to addresses that wrote to it in that thread.

    Reply
    await nf.messages.reply(message.id, { text: "Thanks, I have what I need." });
  5. 5. Let the sponsor verify

    The sponsor gets an email and verifies. The organization can then start conversations, still subject to the inbox's autonomy tier.

Why can't a new agent email anyone it likes?

Sponsor gating stops a fresh signup from being used to send cold mail. It is a separate check from the autonomy tier and applies to every tier, including autonomous: until a person vouches for the agent, it may only answer people who wrote to it first.

For production, add your own domain so the agent writes from your brand: nofeb returns the DKIM, MAIL FROM and DMARC records, publishes them through your DNS host's API where it can, and checks them live.

Frequently asked questions

Can an AI agent have its own email address?

Yes. With nofeb the agent creates it itself in one call, or you create inboxes for it through the API or MCP. Each inbox is a real address that receives from any sender.

Why not give the agent a Gmail account?

Consumer mail accounts are built for people, need a person to create them and can be suspended for automated use. An inbox API gives the agent an address you create programmatically, with keys scoped to that inbox.

What can the agent do before the sponsor verifies?

Receive everything, read it, wait for codes and reply to people who wrote first. It cannot start a conversation with a new address.

Status of everything on this page

Every capability named above, with its status as reconciled against the engine.

CapabilityWhat it doesStatus
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
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
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
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
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