Install Jentic One Beta

Connect the DunSocial API to your agent

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

Schedule posts and X threads or queue them for immediate publishing across connected accounts

Validate a post with a dry run before scheduling or publishing it

Reschedule, cancel, or delete scheduled posts

Manage drafts and a media gallery with presigned uploads

List connected social accounts and read per-platform options like Reddit flair and Pinterest boards

GET STARTED

Start building with DunSocial API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use DunSocial API for, with concrete tasks.

★ Agent-driven post scheduling

An AI agent connected through Jentic drafts a post, runs the validate dry run to catch per-platform problems, then schedules it across the connected accounts, all without a human opening the DunSocial app. The validate step returns the checks for each target so the agent can fix a post before it is queued rather than after it fails.

Validate a post for the connected accounts, and if it passes, schedule it for a given time

Thread publishing

Teams publish multi-tweet X threads by scheduling or immediately queuing a thread of two to twenty-five tweets through DunSocial. The API exposes dedicated schedule-thread and publish-thread endpoints plus the X monthly posting-cap usage, so an agent can check headroom before posting.

Check the X monthly posting-cap usage, then schedule a thread of five tweets if there is headroom

Draft and media management

Content workflows keep a library of drafts and media in DunSocial, creating and updating drafts and uploading images through presigned URLs that are confirmed into the gallery. An agent can assemble a post from stored drafts and media rather than regenerating assets each time.

Create a draft, request a presigned upload URL for an image, and confirm the upload into the gallery

Per-platform posting options

Before posting to platforms with their own rules, teams read the live requirements, such as Reddit flair templates and post rules for a subreddit, or the boards on a connected Pinterest account. DunSocial exposes these option endpoints so an agent builds a valid post for each platform rather than guessing its constraints.

List the Reddit flair templates and post requirements for a subreddit before scheduling a Reddit post

Key Endpoints

41 endpoints — the dunsocial api schedules and publishes social posts across connected accounts and manages the drafts, media, and workspace personalization behind them.

METHOD

PATH

DESCRIPTION

POST

/api/posts/schedule

Schedule a post

POST

/api/posts/publish-now

Queue a post for immediate publish

POST

/api/posts/validate

Dry-run schedule and publish checks

GET

/api/posts

List posts

POST

/api/drafts

Create a draft

GET

/api/social-accounts

List connected social accounts

POST

/api/media/upload-url

Get a presigned media upload URL

POST

/api/posts/schedule

Schedule a post

POST

/api/posts/publish-now

Queue a post for immediate publish

POST

/api/posts/validate

Dry-run schedule and publish checks

GET

/api/posts

List posts

POST

/api/drafts

Create a draft

GET

/api/social-accounts

List connected social accounts

POST

/api/media/upload-url

Get a presigned media upload URL

Why Jentic?

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

Setup

Wiring DunSocial by hand means handling its Bearer auth, adding the X-Workspace-Id header on workspace routes, and running the validate dry run and presigned media upload flow yourself. Through Jentic you install once, import DunSocial from the API Directory, store the token once, and your agent calls it.

Permission scoping

DunSocial carries post, draft, and media ids in the URL path, so a rule can pin your agent to the operations you pick, such as validating and scheduling posts. You choose the operations it may call, so destructive ones like deleting a post or publishing immediately are not included unless you add them.

Credential isolation

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

FAQs

Specific to using DunSocial API through Jentic.

What authentication does the DunSocial API use?

The DunSocial API authenticates with a Bearer token, a session or personal access token, in the Authorization header per its OpenAPI spec. Workspace-scoped routes additionally require an X-Workspace-Id header. Through Jentic the token is stored once and injected at call time so it never enters the agent's prompt.

Can I schedule a post across multiple accounts with the DunSocial API?

Yes. You can schedule a single post or an X thread, publish immediately, and run a validate dry run first to catch per-platform problems. Scheduled posts can then be rescheduled, cancelled, or deleted through their own endpoints.

What are the rate limits for the DunSocial API?

The OpenAPI spec does not publish fixed rate limits, though it does expose X monthly posting-cap usage so you can track that platform's limit. Check the DunSocial documentation for the per-account limits that apply to your plan.

Is there a DunSocial API MCP server?

You don't need an MCP server to give your agent the DunSocial API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent schedules and publishes posts on demand without loading another server's tool definitions into its context.

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

Yes. Write a rule that allows only the validate and schedule operations, so the agent can queue posts but cannot publish immediately or delete queued content, and every call it makes is logged for review.

How do I schedule social posts with the DunSocial API through Jentic?

Search Jentic for 'schedule a social post', add the DunSocial API from the directory, and store your token once; your agent can then validate and schedule posts across the connected accounts on demand. To run it on your own infrastructure, install Jentic One from its GitHub repo.

DunSocial API

AI ReadinessFoundational (C+)60/100

See full scorecard

Official vendor OpenAPI document · agent-readySocial MediaSocial Publishingbearer41 EndpointsREST

For Agents

Schedule, validate, and publish social posts and threads across connected accounts, manage drafts and media, and read per-platform posting options.

Use for: Schedule a post to go out tomorrow morning across my accounts, Publish a post immediately to the connected accounts, Validate a draft post before I schedule it, List the posts queued for this week

Not supported: Does not run paid ad campaigns, read social analytics dashboards, or manage direct messages. Use for scheduling and publishing social posts and their drafts and media only.

The DunSocial API schedules and publishes social posts across connected accounts and manages the drafts, media, and workspace personalization behind them. It schedules single posts and X threads, publishes immediately, validates a post with a dry run before it goes out, and reschedules, cancels, or deletes queued posts. Alongside publishing it manages a media gallery with presigned uploads, draft content, memory collections for personalization, and per-account options such as Reddit flair, Pinterest boards, and Slack or Discord channels.

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

42%

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.

47%

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

23%

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.

35%

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

57%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the DunSocial API to your agent

Capabilities

Start building with DunSocial API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

DunSocial API

Jentic AI Readiness Score

DunSocial 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