Install Jentic One Beta

Connect the BlendDuck Public API to your agent

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

Publish a single logical post to multiple connected social channels at once

List and disconnect the social channels in a workspace

Compare attributed performance across your published posts

Upload and reuse inspected media for posts

GET STARTED

Start building with BlendDuck Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use BlendDuck Public API for, with concrete tasks.

★ Cross-channel publishing through Jentic

Let an agent post the same update everywhere at once. The agent composes one logical post and targets the connected channels, and BlendDuck fans it out to each provider. Through Jentic the post operation is discovered by intent and called with its input schema, so publishing across channels is a single step.

Create a multi-target post with POST /api/v1/posts targeting the connected channels

Performance comparison

Measure which posts and channels are working without opening each platform's dashboard. The agent reads attributed social performance across published posts, so a reporting workflow can rank posts or flag underperformers.

Compare post performance with GET /api/v1/analytics

Media upload and reuse

Attach images or video to a post from a managed media library. The agent uploads inspected media once and references it when composing a post, so the same asset can appear across channels without re-uploading.

Upload media with POST /api/v1/media, then reference it when creating a post with POST /api/v1/posts

Webhook delivery monitoring

Keep an eye on post and channel events delivered to your own endpoint. The agent lists a webhook endpoint's delivery history and replays a failed delivery, so an integration recovers from a missed event without manual intervention.

List deliveries with GET /api/v1/webhooks/{webhookEndpointId}/deliveries, then replay a failed one with POST /api/v1/webhooks/{webhookEndpointId}/deliveries/{webhookDeliveryId}/replay

Key Endpoints

25 endpoints — the blendduck public api publishes a single logical post across multiple connected social channels and tracks how each one performed.

METHOD

PATH

DESCRIPTION

POST

/api/v1/posts

Create a logical multi-target post

GET

/api/v1/posts

List logical posts

GET

/api/v1/analytics

Compare attributed social performance

GET

/api/v1/channels

List workspace channels

POST

/api/v1/media

Upload inspected workspace media

POST

/api/v1/webhooks

Create a workspace webhook endpoint

GET

/api/v1/webhooks/{webhookEndpointId}/deliveries

List webhook delivery logs

GET

/api/v1/providers

List provider capabilities

POST

/api/v1/posts

Create a logical multi-target post

GET

/api/v1/posts

List logical posts

GET

/api/v1/analytics

Compare attributed social performance

GET

/api/v1/channels

List workspace channels

POST

/api/v1/media

Upload inspected workspace media

POST

/api/v1/webhooks

Create a workspace webhook endpoint

GET

/api/v1/webhooks/{webhookEndpointId}/deliveries

List webhook delivery logs

GET

/api/v1/providers

List provider capabilities

Why Jentic?

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

Setup

Wiring BlendDuck by hand means learning its bearer auth, the one-organization-per-key model, and its multi-target post and webhook delivery shapes. Through Jentic you install once, import BlendDuck from the API Directory, store the token once, and your agent calls it.

Permission scoping

BlendDuck's key already scopes the agent to one organization, and ids like the webhook endpoint id travel in the URL path. You choose which operations your agent may call, so it can publish posts and read analytics while channel disconnection or webhook deletion stays out unless you add them.

Credential isolation

Your BlendDuck 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 'publish a social post' or 'compare post performance', and Jentic returns the matching BlendDuck operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using BlendDuck Public API through Jentic.

What authentication does the BlendDuck Public API use?

The BlendDuck Public API authenticates with a bearer token per its OpenAPI spec, and the token selects the organization it acts on, so posts and media stay within that workspace. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time.

Can I publish one post to multiple channels with the BlendDuck Public API?

Yes. Create a single logical post and BlendDuck fans it out to the connected channels you target, then list, update, or delete that logical post and read provider capabilities to see what each channel supports.

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

Yes. Write a rule that allows only post creation and analytics reads, so your agent can publish and measure posts but cannot disconnect channels or delete webhook endpoints unless you add those operations. BlendDuck carries a post's target channels in the request body, so rules bound which operations run, not which channel is reached.

What are the rate limits for the BlendDuck Public API?

The OpenAPI spec does not specify rate limits. Check the BlendDuck documentation at https://blendduck.com for current limits before publishing at high volume.

Is there a BlendDuck MCP server?

You don't need an MCP server to give your agent BlendDuck. Jentic connects it directly from the API Directory: import it, store your token once, and your agent runs the post, media, and analytics operations on demand. That also keeps extra tool definitions out of the agent's context.

How do I publish a post to multiple channels with the BlendDuck Public API through Jentic?

Search Jentic for 'publish a post to multiple social channels' and it returns the BlendDuck post operation with its input schema. Your agent composes one logical post, targets the connected channels, and BlendDuck delivers it. To run it on your own infrastructure, install Jentic One from its GitHub repo.

BlendDuck Public API

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readySocial MediaSocial Publishingbearer25 EndpointsREST

For Agents

Publish multi-target social posts and track their performance: create a logical post across connected channels, upload media, compare attributed analytics, and manage webhook endpoints across 25 endpoints.

Use for: Publish a post to all my connected social channels, Compare how my recent posts performed, Upload an image to use in a post, List the social channels connected to my workspace

Not supported: Does not design graphics, run paid ad campaigns, or manage direct messages. Use for publishing posts to connected social channels and tracking their performance only.

The BlendDuck Public API publishes a single logical post across multiple connected social channels and tracks how each one performed. It lists and disconnects workspace channels, uploads inspected media for posts, compares attributed social performance, and exposes each provider's posting capabilities. Workspace webhook endpoints report delivery events, with secret rotation, delivery history, test events, and safe replay of a failed delivery.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 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).

35%

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

Example Density

How richly the API is illustrated with examples.

100%

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

17%

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.

60%

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

64%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the BlendDuck Public API to your agent

Capabilities

Start building with BlendDuck Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

BlendDuck Public API

Jentic AI Readiness Score

BlendDuck Public 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