canonical: https://jentic.com/apis/outreachagent.dev/outreachagent # OutreachAgent API The OutreachAgent API sends, receives, and parses email for AI agents, tracking every delivery through webhook events. It manages inboxes, sending domains, contacts, segments, and templates, and runs multi-step workflows that enroll contacts into outreach sequences. Built-in extractions pull OTP codes and basic invoice fields from incoming messages, and approval policies gate what an agent is allowed to send. ## For AI agents Send and receive email, manage inboxes and sending domains, run outreach workflows with contact enrollments, and extract OTP codes or invoice fields from incoming messages. Approval policies gate what the agent can send. ## Scope Does not handle SMS, voice calls, or push notifications. Use for agent email sending, inboxes, and outreach automation only. ## Capabilities - Send emails and track every delivery through webhook events - Create and manage inboxes and sending domains - Run multi-step email workflows that enroll contacts into sequences - Search messages and threads across inboxes - Extract OTP codes and basic invoice fields from incoming messages - Segment contacts and preview templates before sending - Set approval policies that gate what the agent is allowed to send ## Use cases ### Agent Email Automation An AI agent connected to OutreachAgent through Jentic can send email from a managed inbox, watch delivery events through webhooks, and act on replies it reads back from threads. Approval policies let a human gate risky sends, so the agent runs within bounds you set. Example prompt: Send an email from a managed inbox, then poll webhook deliveries to confirm it was delivered ### Transactional Email Sending Send transactional messages from a verified sending domain and track their delivery. OutreachAgent records every delivery attempt as a webhook event, so an application can confirm receipt and retry failures. Example prompt: Create a sending domain, send a transactional message, and replay a failed webhook delivery ### OTP and Invoice Extraction Turn inbound email into structured data by extracting one-time passcodes and basic invoice fields. An agent can forward a received message to the extraction endpoints and get back the OTP or invoice fields without parsing raw email itself. Example prompt: Extract the OTP code from a received message and use it to complete a login flow ### Outreach Sequences Build nurture sequences by enrolling segmented contacts into a workflow and letting it run step by step. OutreachAgent tracks enrollment logs and workflow analytics, and an agent can pause or resume individual nodes as conditions change. Example prompt: Enroll a segment of contacts into a workflow and pause one node pending review ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/v1/messages/send` | Send an email message | | POST | `/v1/search/messages` | Search messages across inboxes | | POST | `/v1/inboxes` | Create an inbox | | POST | `/v1/workflows` | Create an outreach workflow | | POST | `/v1/enrollments` | Enroll contacts into a workflow | | POST | `/v1/extractions/otp` | Extract an OTP from a message | ## Key resources - **Messages** — Send, search, and read email messages and threads - **Inboxes and Domains** — Manage agent inboxes and verified sending domains - **Workflows and Enrollments** — Multi-step outreach sequences and contact enrollments - **Extractions** — OTP and basic invoice extraction from messages - **Webhooks** — Delivery and event webhooks with replay - **Policies and Approvals** — Approval policies that gate agent sends ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 58 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 60 / 100 - Developer Experience & Jentic Compatibility: 56 / 100 - AI-Readiness & Agent Experience: 52 / 100 - Agent Usability: 87 / 100 - Security: 68 / 100 - AI Discoverability: 39 / 100 - **View full report:** https://jentic.com/apis/outreachagent.dev/outreachagent/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring OutreachAgent by hand means handling its bearer auth, verifying sending domains, and wiring webhook replay yourself. Through Jentic you install once, import OutreachAgent from the API Directory, store the credential once, and your agent calls it. - **Permission scoping:** OutreachAgent carries the recipient and message content in the request body, so a rule bounds which operations your agent may call rather than which inbox. Pick the operations it needs, such as sending and searching messages, and leave inbox deletion or policy changes out unless you add them. - **Credential handling:** Your OutreachAgent credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'send an email' or 'extract an OTP', and Jentic returns the matching OutreachAgent operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Resend** — Developer-focused transactional email API, where OutreachAgent adds inboxes and outreach workflows. - **Brevo** — Email plus marketing automation platform, overlapping OutreachAgent's sequences and segments. - **Customer.io** — Behavioral messaging driven by product events, complementing OutreachAgent's email delivery. ## FAQ ### Is there an OutreachAgent MCP server? You don't need an MCP server to give your agent the OutreachAgent API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent can send mail, manage inboxes, and run workflows. Operations are discovered on demand, so your agent's context stays lean. ### Can I limit what my agent is allowed to do with the OutreachAgent API? Yes. Write a rule that allows only the message-send and search operations, so the agent can send and read mail but cannot delete inboxes or change policies unless you add those operations. OutreachAgent also has approval policies that gate sends, and every call Jentic makes is logged. ### What authentication does the OutreachAgent API use? The OutreachAgent API authenticates with a bearer token in the Authorization header per its OpenAPI spec, accepting either a Clerk JWT or an OutreachAgent API key. With Jentic, the token is stored encrypted by your own Jentic One instance and injected at call time. ### Can I extract an OTP code from an email with the OutreachAgent API? Yes. The OTP extraction endpoint takes a message or text input and returns the one-time passcode, and a separate endpoint extracts basic invoice fields. An agent can act on inbound mail without parsing raw email itself. ### What are the rate limits for the OutreachAgent API? The spec exposes send-limit endpoints you can configure, but it does not specify API rate limits. Check the OutreachAgent documentation at https://outreachagent.dev for current limits. ### How do I send an email with the OutreachAgent API through Jentic? Import the OutreachAgent API from the Jentic API Directory, store your credential once, and have your agent search by intent such as 'send an email'. Jentic returns the send operation with its input schema, and your agent passes the inbox and recipient. To run it on your own infrastructure, install Jentic One from its GitHub repo.