Install Jentic One Beta

Connect the Mailtrap API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mailtrap 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.

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%2Fmailtrap.io%2Fmain" | sh

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%2Fmailtrap.io%2Fmain" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Mailtrap API.

Send a single transactional email with HTML, text, attachments, and template variables

Send a batch of personalised messages to many recipients in one call

Attach files inline by base64-encoding them in the request body

Reference a stored Mailtrap template by ID and pass per-recipient variables

Track each send by category and custom variable for downstream analytics

GET STARTED

Start building with Mailtrap API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Mailtrap API for, with concrete tasks.

★ Single Transactional Email

Most user-triggered emails - receipts, password resets, sign-up confirmations - are individual messages with personalised content. The Mailtrap /send endpoint accepts the from, to, subject, HTML, text, and attachment fields and returns a sending message ID for downstream log lookup. Integration is a single POST per message and pairs naturally with template references for consistent formatting.

POST /send with from, to, subject, html, and a base64 PDF attachment, then capture the returned message_id for log lookup.

Batched Personalised Send

Onboarding sequences and bulk notifications need per-recipient personalisation in a single call. The Mailtrap /batch endpoint accepts a list of recipients with their own template variables, sending each as an individual message while keeping the request count low. Each recipient gets a distinct message ID for downstream tracking.

POST /batch with a list of 100 recipients each carrying their own template variables, then store the per-recipient message IDs.

Template-Driven Receipts

Storing email content in Mailtrap templates lets non-engineers update copy without redeploying. The send endpoints accept a template ID and a variables object, applying server-side rendering before delivery. Receipts, shipping confirmations, and other structured messages move from inline HTML in code to managed templates in the Mailtrap dashboard.

POST /send with template_uuid set to the receipt template and template_variables carrying order_total and tracking_number.

AI Agent Outbound Email

Agents that close support tickets, confirm bookings, or notify users need a reliable send surface. Through Jentic the agent searches for the Mailtrap send operation, loads the schema, and executes the POST while the API-Token stays in the vault. The same flow underpins notification copilots and automated case-resolution agents.

Use Jentic to search 'send a transactional email', execute POST /send with the resolved customer details, and report the message_id back to the calling tool.

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for mailtrap api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/send

Send email

POST

/batch

Batch send emails

POST

/send

Send email

POST

/batch

Batch send emails

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Mailtrap API by hand means sending your token in the API-token header, choosing between the send.api and bulk.api Mailtrap hosts, and building the email payload yourself. Through Jentic you install once, import Mailtrap from the API Directory, store the token once, and your agent calls it.

Permission scoping

Mailtrap carries the recipients in the request body for both /send and /batch, so limit the agent to the operations it needs, such as single-message send, and add batch sending only when you want it. The operation set is your choice.

Credential isolation

Your Mailtrap API token 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.

Intent-based discovery

Agents search Jentic by intent such as 'send a transactional email' or 'send a batch of emails', and Jentic returns the matching Mailtrap operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Mailtrap API through Jentic.

Why is there no official OpenAPI spec for Mailtrap API?

Mailtrap does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Mailtrap API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Mailtrap API use?

Mailtrap requires an API-Token request header on each call. Through Jentic the token is stored encrypted in the vault and injected at execute time, so the raw value never enters the agent context.

Can I send to multiple recipients in one call?

Yes. POST /batch accepts a list of recipients each with their own template variables and returns a per-recipient message ID. Use POST /send when you only need to deliver a single message.

How do I attach a file to a Mailtrap send?

Include an attachments array on the POST /send body where each entry has the base64-encoded content, filename, and content_type. Inline images use the same shape with a content_id reference.

What are the rate limits for the Mailtrap API?

Rate limits are not declared in the spec and depend on the Mailtrap plan attached to the account. Check the Mailtrap dashboard before driving high-volume sends.

How do I send a single email through Jentic?

Run pip install jentic, search 'send a transactional email through mailtrap', load the schema for POST /send, and execute with the from, to, subject, and html fields. Jentic injects the API-Token from the vault.

Can I limit what my agent is allowed to do with the Mailtrap API?

Yes. Because Jentic One is self-hosted, you decide which Mailtrap operations your agent can call, and the Mailtrap surface is just two operations: POST /send for a single message and POST /batch for many recipients in one call. You can allow only single-message send and add batch sending when you actually want it, since the operation set is your choice. Your Mailtrap API token is held by your own instance and injected at execution time, so the agent uses the credential without it entering the prompt or logs.

Mailtrap API

Name: Mailtrap API
Brand: Mailtrap API
Availability: InStock

Browse all Mailtrap APIs

Agent-ready OpenAPI document · curated by JenticCommunicationsEmail DeliveryapiKey2 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Send a single transactional email or a batch of messages through Mailtrap. Used by agents that deliver receipts, sign-up confirmations, password resets, and other one-off or batched messages.

Use for: I need to send a transactional confirmation email through Mailtrap, Send a batch of password-reset emails to a list of users, Deliver a receipt email with a PDF attachment via Mailtrap, Personalise a Mailtrap template with per-recipient variables

Not supported: Does not manage sending domains, suppression lists, or delivery logs - use for sending single or batched transactional email only.

Jentic publishes the only available OpenAPI specification for Mailtrap API, keeping it validated and agent-ready. The Mailtrap send API is a focused two-endpoint surface for delivering transactional email: a single send endpoint for one message and a batch endpoint for sending many in one call. It is built around the API-Token header and is the operational pair to Mailtrap's domain, suppression, and log management API.

Jentic One on Github View OpenAPI Document

Connect the Mailtrap API to your agent

Capabilities

Start building with Mailtrap API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Mailtrap API