Install Jentic One Beta

Connect the Breakreach API to your agent

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

Schedule, publish now, or save as draft a post to several connected accounts in one createPost call

Pick the next free posting slot for a workspace and queue a post into it with useNextSlot

Re-host a media URL or upload a local file to Breakreach storage before attaching it to a post

Read comments on a published post and reply to a comment by commentId on its platform

GET STARTED

Start building with Breakreach API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Breakreach API for, with concrete tasks.

★ AI agent cross-posting through Jentic

A developer wants their AI agent to turn a release note into posts for several networks without wiring the Breakreach client by hand. Through Jentic the agent searches for 'schedule a social media post', loads the createPost operation with its input schema, and sends the content with the target accountIds and a scheduledAt time, while the bearer key is injected at call time. The agent then lists posts by status to confirm the schedule landed.

Call GET /v1/accounts to find the LinkedIn and Bluesky accountIds, then POST /v1/posts with the release note as content, those accountIds, and scheduledAt set to 2026-11-06T09:00:00Z

Queue-based content calendar

A small team keeps a steady posting cadence by dropping new posts into the next open slot instead of picking times by hand. Breakreach returns the next free slot for a workspace through getNextSlot, and createPost accepts useNextSlot so a post is queued straight into it. Media is re-hosted with uploadMedia first so every platform gets a stable URL.

Re-host an image with POST /v1/media using its url, then POST /v1/posts with the content, accountIds, the returned media, and useNextSlot set to true

Comment and inbox triage

Community managers need to answer comments and DMs from several networks in one place. Breakreach lists recent comments by platform and account, reads the comments on a given post, and replies with replyToComment using the accountId, platform, commentId, and message. Inbox conversations can be read and answered with sendDirectMessage for the same connected account.

Call GET /v1/comments for platform instagram, then POST /v1/comments/reply with accountId, platform, commentId, and a thank-you message for each new comment

Post performance reporting

Marketers want a weekly view of which posts worked. Breakreach returns per-post metrics through getPostMetrics, daily account trends through getAccountTrends with a days window, and a ranked content performance list through getContentPerformance with sortBy and limit. Those three reads build a report without logging in to each network.

Call GET /v1/performance with days set to 7 and limit set to 10, then GET /v1/posts/{id}/metrics for the top post and summarise the results

Key Endpoints

37 endpoints — the breakreach api publishes and schedules social media posts across instagram, tiktok, x, reddit, linkedin, youtube, facebook, threads, bluesky, pinterest, mastodon, wordpress, ghost, dev.

METHOD

PATH

DESCRIPTION

POST

/v1/posts

Create, schedule, or publish a post

GET

/v1/posts

List posts by status

GET

/v1/accounts

List connected social accounts

GET

/v1/next-slot

Get the next free posting slot

POST

/v1/media

Re-host a media URL

POST

/v1/comments/reply

Reply to a comment

POST

/v1/inbox/{conversationId}/messages

Send a direct message

GET

/v1/posts/{id}/metrics

Get per-post metrics

POST

/v1/posts

Create, schedule, or publish a post

GET

/v1/posts

List posts by status

GET

/v1/accounts

List connected social accounts

GET

/v1/next-slot

Get the next free posting slot

POST

/v1/media

Re-host a media URL

POST

/v1/comments/reply

Reply to a comment

POST

/v1/inbox/{conversationId}/messages

Send a direct message

GET

/v1/posts/{id}/metrics

Get per-post metrics

Why Jentic?

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

Setup

Wiring Breakreach by hand means creating a bearer API key, tracking workspace and accountIds for each network, and sending an Idempotency-Key on POSTs so retries do not double-post. Through Jentic you install once, import Breakreach from the API Directory, store the key once, and your agent calls it.

Permission scoping

Breakreach carries the target accountIds and the workspace in the request body or query string, so rules bound which operations your agent may call, not which social account it posts to. Limit the agent to the operations it needs, such as creating posts, so destructive ones like deletePost or deleteDmAutomation are not included unless you add them.

Credential isolation

Your Breakreach API 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 'schedule a social media post' or 'reply to a comment', and Jentic returns the matching Breakreach operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Breakreach API through Jentic.

What authentication does the Breakreach API use?

The Breakreach API authenticates with a bearer token in the Authorization header, per its OpenAPI spec. The token is an API key created in the Breakreach dashboard (prefixed br_) or an OAuth access token (prefixed bro_). Through Jentic the key is stored encrypted by your own Jentic One instance and attached at call time, so the agent never handles it.

Can I schedule one post to several networks with the Breakreach API?

Yes. POST /v1/posts takes the content and a list of accountIds, plus scheduledAt for a fixed time, publishNow to post at once, useNextSlot to queue it in the next free slot, or draft to save it. Platform extras such as pinterestBoardId or redditSubreddit ride in the same body.

What are the rate limits for the Breakreach API?

The OpenAPI spec does not specify rate limits. Check the Breakreach documentation at https://breakreach.com for current limits. The spec does document an Idempotency-Key header on every POST, so a retried request with the same key and body returns the first response instead of creating a duplicate post.

Is there a Breakreach MCP server?

You don't need an MCP server to give your agent Breakreach. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the posting, inbox, and analytics operations it needs, discovered on demand without loading a set of tool definitions into its context.

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

Yes. For example, write a rule that allows only GET /v1/accounts, GET /v1/next-slot, and POST /v1/posts, so the agent can look up accounts and queue posts but cannot delete posts, send DMs, or change automations. Every call it makes is logged for review.

How do I publish a post with Breakreach through Jentic?

Search Jentic for 'schedule a social media post', load the createPost operation, and execute it with content, accountIds, and either scheduledAt or publishNow. Call GET /v1/accounts first if the agent needs the accountIds. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Breakreach API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readySocial MediaSocial Publishingbearer37 EndpointsREST

For Agents

Schedule or publish one post to many connected social accounts, reply to comments and DMs, and read post metrics and account trends across Breakreach workspaces.

Use for: Schedule a LinkedIn and Bluesky post for tomorrow morning, I want to publish this announcement to all my connected accounts now, Find the next free posting slot in my workspace, List all scheduled posts that have not gone out yet

Not supported: Does not run paid ad campaigns, buy promoted placements, or manage social ad accounts. Use for organic social publishing, inbox replies, and post analytics only.

The Breakreach API publishes and schedules social media posts across Instagram, TikTok, X, Reddit, LinkedIn, YouTube, Facebook, Threads, Bluesky, Pinterest, Mastodon, WordPress, Ghost, Dev.to, Hashnode, Tumblr and more with one request shape. A single post call takes the content, the target accountIds, and either a scheduledAt time, publishNow, useNextSlot, or draft. The same API reads comments and direct messages, replies to them, runs Comment to DM rules and DM automations, and reports post metrics, account trends, and content performance per workspace. Every POST accepts an Idempotency-Key header so a retried request does not create a second post.

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

100%

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: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

55%

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: D+Signals: 4

40%

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.

56%

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

77%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Breakreach API to your agent

Capabilities

Start building with Breakreach API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Breakreach API

Jentic AI Readiness Score

Breakreach 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