Introduction

Aigeon is an AI-powered email platform that turns every send into revenue: you design, segment, and ship newsletters; built-in ads and a publisher marketplace layer on monetization automatically.

This documentation covers three audiences:

• Operators — marketers, publishers, and creators running Aigeon from the web console. Start with Features to learn how to build your audience, design emails, and analyze results.
• Developers — teams integrating Aigeon into their own product. Start with the API reference for keys, scopes, and code samples.
• Automation builders — anyone composing AI agents against Aigeon via the MCP server or the REST API.

How Aigeon is organized

Every object you create in Aigeon belongs to an organization. Most day-to-day entities map onto a few core types:

| Concept | What it is | | --- | --- | | Contact | A single recipient, identified by hashed email. Owns properties and custom fields. | | List | A named group of contacts you can send to directly. | | Segment | A saved query over contacts/events. Re-evaluates whenever you send. | | Template | An email design. Has component-based layout and a version history. | | Flow | An automation graph that reacts to triggers and sends emails on your schedule. | | Campaign | A one-time send to a list or segment. | | Sending domain | A domain you authenticate (SPF / DKIM / DMARC) to send from. |

What's next

• Quickstart — send your first email end-to-end.
• Core concepts — how flows, campaigns, and contacts fit together.
• API keys — mint a key to start automating.
• MCP servers — talk to Aigeon from Claude Desktop, Claude Code, or Cursor.