Install Jentic One Beta

Connect the Brevo Email API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Brevo Email 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%2Fdevelopers.brevo.com%2Fbrevo" | 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%2Fdevelopers.brevo.com%2Fbrevo" | 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 Brevo Email API.

Send a transactional email to one or more recipients

Look up the delivery status of a sent message

Read aggregated and event-level sending statistics

Create, update, and list reusable email templates

Review and manage the list of blocked contacts

GET STARTED

Start building with Brevo Email API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Brevo Email API for, with concrete tasks.

★ AI Agent Transactional Email Sender

An AI agent can send confirmations, alerts, and receipts on behalf of an application by calling the send operation with a template or inline content. Through Jentic the agent finds the send operation by intent and supplies recipients and variables, so a support or workflow agent can email users without a developer wiring the endpoint by hand.

Send a transactional email to a customer using a named template and return the resulting message id

Delivery Monitoring Assistant

A monitoring agent can confirm that important emails reached recipients and surface problems early. The API returns per-message delivery status plus aggregated and event-level statistics, so an agent can report opens, clicks, and bounces or flag a message that failed to deliver, all without a person checking a dashboard.

Fetch delivery events for the last day and report how many messages bounced or were opened

Template and Sender Hygiene

An operations agent can keep transactional sending healthy by maintaining templates and cleaning the contact list. The API lets an agent create or update templates, review blocked contacts, and clear hard bounces, so a team can standardize messaging and protect sender reputation as part of a routine workflow.

List the available templates, then remove hard bounces to clean the sending list

Key Endpoints

16 endpoints — the brevo email api sends transactional emails and reports on how they performed.

METHOD

PATH

DESCRIPTION

POST

/smtp/email

Send a transactional email

GET

/smtp/emails

List sent transactional emails

GET

/smtp/emailStatus/{identifier}

Get the status of a sent email

GET

/smtp/statistics/events

Read event-level sending statistics

GET

/smtp/statistics/aggregatedReport

Read an aggregated sending report

GET

/smtp/templates

List transactional email templates

POST

/smtp/templates

Create a transactional email template

GET

/smtp/blockedContacts

List blocked contacts

POST

/smtp/email

Send a transactional email

GET

/smtp/emails

List sent transactional emails

GET

/smtp/emailStatus/{identifier}

Get the status of a sent email

GET

/smtp/statistics/events

Read event-level sending statistics

GET

/smtp/statistics/aggregatedReport

Read an aggregated sending report

GET

/smtp/templates

List transactional email templates

POST

/smtp/templates

Create a transactional email template

GET

/smtp/blockedContacts

List blocked contacts

Why Jentic?

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

Setup

Wiring Brevo by hand means creating an API key, adding it to the api-key header on every call, and mapping the send and statistics operations. Through Jentic you install once, import Brevo from the API Directory, store the key once, and your agent calls it.

Permission scoping

You decide which Brevo operations the agent may use. Allow it to read statistics without sending, or allow sending while blocking template deletion, and because message and template ids sit in the URL path, a rule can restrict it to specific resources.

Credential isolation

Your Brevo API key is stored encrypted by your own Jentic One instance and injected into the api-key header at execution time. It never enters the agent's prompt, logs, or context window.

Intent-based discovery

Agents search Jentic by intent such as 'send a transactional email' or 'get email statistics', and Jentic returns the matching Brevo operation with its input schema so the agent calls the right endpoint.

FAQs

Specific to using Brevo Email API through Jentic.

Is there a Brevo MCP server?

You don't need an MCP server to give your agent the Brevo Email API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent can send transactional emails and read statistics. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.

Can I restrict what my agent is allowed to do with the Brevo Email API?

Yes. You choose which operations the agent may call, so you can allow it to read delivery statistics but not send mail, or allow sending but block template deletion. Because template and message ids appear in the URL path, a rule can also pin the agent to specific templates, and every call is logged.

What authentication does the Brevo Email API use?

The Brevo Email API authenticates with an API key, passed in the api-key request header per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and added to each request at call time, so it never appears in the agent's prompt or logs.

Can my agent check whether an email was delivered with the Brevo Email API?

Yes. After sending, the agent can look up a message by its identifier to read delivery status, and it can pull aggregated reports or per-event data to see opens, clicks, and bounces. This lets a monitoring agent confirm delivery and flag failures automatically.

What are the rate limits for the Brevo Email API?

The OpenAPI spec does not specify rate limits. Check the Brevo developer documentation at https://developers.brevo.com for the current per-plan sending and request limits before running high-volume workloads.

How do I send transactional email through Jentic?

Search Jentic for 'send a transactional email', import the Brevo operation, and store your API key once. Your agent then sends messages and reads their statistics on demand. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Brevo Email API

Name: Brevo Email API
Brand: Brevo
Availability: InStock

Official vendor OpenAPI document · agent-readyCommunicationsEmail DeliveryapiKey16 EndpointsREST

For Agents

Send transactional emails through Brevo, check their delivery status, read aggregated and event-level statistics, and manage email templates and blocked contacts.

Use for: Send a transactional confirmation email, Check whether a specific email was delivered, Pull last week's email open and click statistics, Create a new transactional email template

Not supported: Covers transactional email only. Does not handle marketing campaigns, SMS, or CRM contact management, which live in other parts of the Brevo platform.

The Brevo Email API sends transactional emails and reports on how they performed. You can send a message, look up its delivery status, pull aggregated and event-level statistics, and manage the reusable templates and blocked-contact list behind your sending. It covers the transactional email side of Brevo rather than marketing campaigns or CRM.

Jentic One on Github View OpenAPI Document

Connect the Brevo Email API to your agent

Capabilities

Start building with Brevo Email API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Brevo Email API