Official vendor OpenAPI document · agent-readyCommunicationsEmailapikey443 EndpointsREST
For Agents
Create email inboxes and phone numbers, send email and SMS, and wait for, read, and process received messages.
Use for: Create a new email inbox, Send an email from an inbox, Wait for the latest email to arrive, Read the content of a received email
Not supported: Creates inboxes and phone numbers and sends and reads messages through MailSlurp; it does not manage your DNS, sending domains, or deliverability settings, which are configured in the MailSlurp dashboard.
The MailSlurp API creates email inboxes and phone numbers on demand and sends and receives email and SMS. It creates inboxes, sends emails, waits for and reads incoming messages and their attachments, and manages templates, contacts, webhooks, forwarders, and rulesets. Phone numbers can be allocated to receive SMS. Responses are JSON, so an agent can spin up a test inbox, send a message, and read the reply without running its own mail server.
Install Jentic One Beta
Connect the MailSlurp API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MailSlurp API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmailslurp.com%2Fmailslurp" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmailslurp.com%2Fmailslurp" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with MailSlurp API.
Create and list email inboxes
Send emails from an inbox
Wait for and read received emails
Read email attachments and content
Manage templates, contacts, and forwarders
Allocate phone numbers and receive SMS
Use Cases
Patterns agents use MailSlurp API for, with concrete tasks.
★ Create a disposable inbox
Testing signup and email flows needs a fresh mailbox. The MailSlurp API creates an inbox on demand and lists existing inboxes, so an application can generate a real address to receive mail. Each inbox can send and receive without manual mailbox setup.
Create a new inbox and return its email address.
Send and receive email
Automated flows send messages and check for replies. The MailSlurp API sends an email from an inbox and waits for the latest incoming email, so an application can verify that a message arrived and read its content. This supports confirmation-code and notification testing end to end.
Send an email, then wait for and read the reply.
Process inbound mail
Applications often act on email as it arrives. The MailSlurp API reads incoming emails and their attachments and manages webhooks, forwarders, and rulesets, so an application can route or react to inbound mail. Webhooks push new-email events to a configured endpoint.
Read a received email and its attachments for processing.
Agent-driven email flows
An AI agent can create an inbox and check for a message without a developer wiring each call. Through Jentic the agent matches an intent such as 'wait for the verification email' to the MailSlurp wait operation, runs it, and reads the result. The API key stays in the user's Jentic One instance and never reaches the agent's prompt.
Create an inbox, wait for the incoming email, and return its content.
Key Endpoints
443 endpoints — the mailslurp api creates email inboxes and phone numbers on demand and sends and receives email and sms.
METHOD
PATH
DESCRIPTION
POST
/inboxes
Create a new email inbox.
GET
/inboxes
List email inboxes.
POST
/sendEmail
Send an email from an inbox.
GET
/waitForLatestEmail
Wait for and return the latest email.
GET
/emails
List emails.
GET
/emails/{emailId}
Get an email's content including headers and body.
POST
/inboxes
Create a new email inbox.
GET
/inboxes
List email inboxes.
POST
/sendEmail
Send an email from an inbox.
GET
/waitForLatestEmail
Wait for and return the latest email.
GET
/emails
List emails.
GET
/emails/{emailId}
Get an email's content including headers and body.
Jentic AI Readiness Score
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.
M
MailSlurp API
- Foundational (C-)53/100
75
Foundational Compliance56
Developer Experience & Jentic Compatibility48
AI-Readiness & Agent Experience43
Agent Usability50
Security66
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
75
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
91%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
7%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
48
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
42%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
51%
Summary Coverage
Coverage of summaries across operations/tags/info.
43
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: D-Signals: 1
43%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
66
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
66%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring MailSlurp yourself means managing an API key, creating inboxes, and polling or waiting for incoming mail. With Jentic you install once, import MailSlurp from the API Directory, and store the key a single time.
Permission scoping
Jentic lets you grant your agent only the operations it needs, such as creating inboxes and reading email without inbox deletion, and enforces that on every call.
Credential isolation
Your MailSlurp API key is stored once, encrypted, by your own Jentic One instance. It is injected when a call runs and never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents find MailSlurp through Jentic's intent search, matching a request like 'wait for the verification email' to the right operation without hardcoded endpoints.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using MailSlurp API through Jentic.
What can an AI agent do with the MailSlurp API through Jentic?
An agent can create inboxes and phone numbers, send email and SMS, and wait for, read, and process incoming messages. Through Jentic the agent matches an intent to the right operation and runs it with your API key injected at execution time.
How do I authenticate with the MailSlurp API?
MailSlurp authenticates requests with an API key sent in the x-api-key header. You store the key once in your Jentic One instance, and it is added to each call at run time rather than exposed to the agent.
Can MailSlurp receive email as well as send it?
Yes. An inbox can send messages and receive them, and the API can wait for the latest email, read its content and attachments, and push new-email events to a webhook. This supports end-to-end email testing and inbound processing.
Does the MailSlurp API document rate limits?
The OpenAPI specification does not state rate limits; request allowances depend on your MailSlurp plan. Check the current limits for your account in MailSlurp's documentation.
Can I control which MailSlurp operations my agent can call?
Yes. Jentic lets you allow only the operations your agent needs, for example creating inboxes and reading email while withholding inbox deletion. Your Jentic One instance enforces that boundary on every call and keeps the API key outside the agent's context.
GET STARTED