Install Jentic One Beta

Connect the Breaker API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Breaker 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%2Fbreaker.email%2Fbreaker" | 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%2Fbreaker.email%2Fbreaker" | 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 Breaker API.

Create, schedule, and export the rendered HTML of email campaigns

Read campaign reporting: opens, unsubscribes, and clicks per link

Build dynamic and static segments and recalculate them on demand

Tag contacts and attach custom fields to your newsletter audience

Create and update multi-step automations and their email content

GET STARTED

Start building with Breaker API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Breaker API for, with concrete tasks.

★ Agent-authored newsletter campaign

An AI agent that drafts newsletter content can create a draft campaign in Breaker, replace its body with the generated HTML, and schedule it, all against the single newsletter the key belongs to. The rendered email can be exported for a final human review before send.

Create a draft campaign titled 'October update', set its body content, and schedule it for the newsletter

Engagement-based segmentation

A growth agent can build a dynamic segment whose rules target engaged readers, recalculate it, then list the contacts it contains, so a follow-up campaign reaches only people who opened or clicked recently. Breaker tracks per-contact engagement and clicks per link.

Create a dynamic segment of contacts who clicked any link in the last campaign and recalculate it

Campaign reporting pull

A reporting agent can read a campaign's summary stats, its clicks per link, and the contacts who clicked a specific link, then read unsubscribes over a date range to produce a weekly performance digest for the newsletter owner.

Read the report for the latest campaign and list the contacts who clicked the top link

Key Endpoints

45 endpoints — the breaker api creates and schedules newsletter email campaigns, reads their reporting, builds subscriber segments, and works with contacts from your own code.

METHOD

PATH

DESCRIPTION

POST

/campaigns

Create a draft campaign

PUT

/campaigns/{campaignId}/content

Replace a campaign body

GET

/reports/campaigns/{campaignId}

Stats for one campaign

GET

/campaigns/{campaignId}/links

Clicks per link for a campaign

POST

/segments

Create a segment

POST

/contacts

Create a contact

POST

/campaigns

Create a draft campaign

PUT

/campaigns/{campaignId}/content

Replace a campaign body

GET

/reports/campaigns/{campaignId}

Stats for one campaign

GET

/campaigns/{campaignId}/links

Clicks per link for a campaign

POST

/segments

Create a segment

POST

/contacts

Create a contact

Why Jentic?

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

Setup

Wiring Breaker by hand means handling its bearer-token auth and remembering that each key is scoped to one newsletter, so no call takes a newsletter id. Through Jentic you install once, import Breaker from the API Directory, store the token once, and your agent calls it.

Permission scoping

You choose which Breaker operations the agent may call, such as reading reports and building segments, so a destructive operation like deleting a draft campaign is not included unless you add it.

Credential isolation

Your Breaker key 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 newsletter email campaign', and Jentic returns the matching Breaker operation with its input schema so the agent calls the right endpoint without browsing the docs.

FAQs

Specific to using Breaker API through Jentic.

What authentication does the Breaker API use?

The Breaker API authenticates with an API key sent as a bearer token in the Authorization header, per its OpenAPI spec. A key belongs to one newsletter, so you create a separate key for each newsletter you work with.

Is there a Breaker MCP server?

You do not need an MCP server to give your agent Breaker. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the campaign, segment, and reporting operations. No extra server tool definitions are loaded into the agent's context.

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

Yes. Write a rule that allows only the report-read and segment operations, so the agent can analyse engagement and build audiences but cannot delete or send a campaign, and every call it makes is logged.

Can I read per-link click reporting with the Breaker API?

Yes. The campaign links endpoint returns clicks per link, and a further endpoint lists the contacts who clicked a specific link, so an agent can see exactly which readers engaged with which content.

What are the rate limits for the Breaker API?

The OpenAPI spec does not publish a numeric rate limit. Check the Breaker documentation for the current limits before scheduling a large batch of campaigns or segment recalculations.

How do I send a newsletter campaign with the Breaker API through Jentic?

Search Jentic for 'send a newsletter email campaign', and it returns the Breaker create-campaign operation with its input schema. Create the draft, set its content, and schedule it, all against the newsletter your key belongs to. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Breaker Email Breaker API

AI ReadinessAI-Aware (A-)73/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingEmail Marketingbearer45 EndpointsREST

For Agents

Create and send email campaigns, build segments, manage contacts and tags, and read opens, clicks, and unsubscribes for one newsletter.

Use for: Create a draft email campaign for my newsletter, Schedule a campaign and export its rendered HTML, Build a dynamic segment of contacts who opened the last campaign, Get the open and click report for a specific campaign

Not supported: Does not handle SMS, transactional email, or payment collection. Use for newsletter email campaigns, segments, and reporting only.

The Breaker API creates and schedules newsletter email campaigns, reads their reporting, builds subscriber segments, and works with contacts from your own code. It covers automations, per-campaign and per-contact engagement, link-level click tracking, and custom fields and tags. A key belongs to one newsletter, so no endpoint takes a newsletter id.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

97%

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).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

32%

Example Density

How richly the API is illustrated with examples.

99%

Example Validity

Percentage of examples that conform to their schemas.

75%

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.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C+Signals: 4

61%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

71%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

78%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Breaker API to your agent

Capabilities

Start building with Breaker API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Breaker Email Breaker API

Jentic AI Readiness Score

Breaker API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness