llms.txt
+23 −11
− - [Email API for a new era.](/index.md): One API to send and receive email. Replies land on the right thread as clean text, attachments as Markdown, and users can connect their own Gmail or Outlook.− - [Every reply on the right thread](/features/threading.md): Replies with a new sender, a new subject or no headers at all still land on the thread they answer. One API call gives your agent the whole conversation, in order.− - [Send from your customer's own inbox](/features/mailboxes.md): Let your customers connect the Gmail or Outlook account they already work out of. No DNS, no subdomain — it sends and receives through AI Inbx on the same API as a domain you own.− - [An email domain for every customer](/features/wildcard-domains.md): Connect *.yourapp.com once and give every customer their own email domain at signup — sending and receiving instantly, no DNS on their side.− - [A space for every customer](/features/spaces.md): Give every customer a space: their domains, their connected inboxes and every thread that went through them, kept apart — with one API key and one webhook endpoint on your side.− - [Email, from your terminal](/features/cli.md): Send and read email, run every API resource, forward webhooks to localhost without a tunnel, wait for an email in a test and check a domain's DNS — one binary, from a terminal, a script or an agent.− - [Give Claude an email address](/features/mcp.md): Give Claude, Cursor or any MCP client an inbox of its own. When it gets stuck, it emails whoever knows, gets on with the rest and picks the answer up when it lands.− - [Build the agent, not the inbox](/use-cases/ai-email-agent.md): Build your AI email agent on AI Inbx: reply categories, threading, clean reply text, attachments as Markdown, your users' own mailboxes and pacing, wired together in your code.− - [Build your outreach tool, not its email](/use-cases/cold-outreach.md): Build your cold outreach tool on AI Inbx: pacing, sending hours, scheduled follow-ups, reply categories and suppressions, wired together in your code.− - [Just the reply, not the thread under it](/solutions/email-reply-parser.md): Parse every email reply down to what the sender wrote: quoted text and repeated signatures removed, answers typed inside the quote kept where they were.− - [Agent setup](/agent.md): Instructions for an agent integrating AI Inbx.+ - [Email API for conversations.](/index.md): One API to send and receive email. Replies land on the right thread as clean text, attachments as Markdown, and users can connect their own Gmail or Outlook.+ - [Every reply on the right thread](/features/threading.md): Replies with a new sender, a new subject or no headers at all still land on the thread they answer. Every email event carries the thread_id your app files it under.+ - [Send from your customer's own inbox](/features/mailboxes.md): Let your customers connect the Gmail or Outlook account they already work out of. It needs no DNS and no subdomain, and sends and receives through AI Inbx on the same API as a domain you own.+ - [An email domain for every customer](/features/wildcard-domains.md): Connect *.yourapp.com once and give every customer their own email domain at signup. It sends and receives at once, with no DNS on their side.+ - [A space for every customer](/features/spaces.md): Give every customer a space: their domains, addresses and connected inboxes, with their mail handled apart from every other customer and one API key and one webhook endpoint on your side.+ - [Email, from your terminal](/features/cli.md): Everything the AI Inbx console and API do, as commands. Set up domains, webhooks and pacing, send and read email, forward webhooks to localhost and check a domain's DNS. One binary for a terminal, a script or a coding agent.+ - [Run AI Inbx from Claude or Cursor](/features/mcp.md): Connect Claude, ChatGPT, Cursor or any MCP client to your AI Inbx workspace. It does everything the console and the API do, from adding a domain to finding why an email was held, at the access you choose.+ - [Email infrastructure for AI agents](/use-cases/ai-email-agent.md): Email infrastructure for AI agents in your product: send, receive and reply through one API, with threading, clean reply text, attachments as Markdown and MCP.+ - [The email API for cold outreach tools](/use-cases/cold-outreach.md): Build your cold outreach tool on AI Inbx: pacing, sending hours, scheduled follow-ups, reply categories and suppressions, wired together in your code.+ - [The reply, without the thread under it](/solutions/email-reply-parser.md): Parse every email reply down to what the sender wrote: quoted text and repeated signatures removed, answers typed inside the quote kept where they were.+ ## Blog+ - [Building with email](/blog.md): Comparisons of email APIs, guides to building on them, and engineering notes on how AI Inbx threads, parses and paces email.+ - [Inboxes are the wrong primitive for platforms](/blog/why-inboxes-are-the-wrong-primitive.md): Inbox-centric email APIs suit one agent with one owner. Platforms serving customers need addresses that work without being created and a bill per email.+ - [Best email APIs for cold outreach tools (2026)](/blog/email-api-for-cold-outreach-tools.md): What a cold-outreach product needs from its email API, and how 12 providers compare on terms, send limits, sending hours, replies and per-customer separation.+ - [Best email APIs for AI agents (2026)](/blog/best-email-api-for-ai-agents.md): Why I think AI Inbx is the best email API for products that give agents email, the bugs it saves you from, and when AgentMail, Nylas or Postmark fit better.+ - [AI Inbx vs Nylas for email in your product (2026)](/blog/ai-inbx-vs-nylas.md): AI Inbx vs Nylas for Gmail and Outlook products: threads without reply headers, inline answers, out-of-office return dates, opt-outs, pacing and pricing.+ - [The best AgentMail alternatives (2026)](/blog/agentmail-alternatives.md): Seven AgentMail alternatives for platforms, compared on per-inbox pricing, catch-all domains, users' Gmail and Outlook, opt-out replies and outreach rules.+ - [AI Inbx vs AgentMail: inboxes vs addresses (2026)](/blog/ai-inbx-vs-agentmail.md): AgentMail bills per inbox; on AI Inbx every address works and the bill follows email. Threads, out-of-office dates, opt-outs, pacing and three worked bills.+ - [The best Nylas alternatives (2026)](/blog/nylas-alternatives.md): Aurinko, Unipile, EmailEngine and AI Inbx vs Nylas for Gmail and Outlook products: threading, reply text, out-of-office dates, opt-outs, cost per account.+ - [Setup skill](/SKILL.md): The whole setup for a coding agent, from sign-in to the first email sent and its reply answered.+ - [Agent skills](https://github.com/aiinbx/skills): `npx skills add aiinbx/skills` — setup, integration, concepts and the CLI as skills; listed at /.well-known/agent-skills/index.json.+ - [Credentials for agents](/auth.md): How an agent signs in and where an API key goes.+ - [Agent prompt](/agent.md): The one prompt to hand a coding agent.