Install Jentic One Beta

Connect the Postproxy Social Media API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Postproxy Social Media 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%2Fpostproxy.dev%2Fpostproxy" | 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%2Fpostproxy.dev%2Fpostproxy" | 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 Postproxy Social Media API.

Publish one post to several connected profiles at once, now, at a scheduled_at time, or as a draft

Add posts to a posting queue with high, medium, or low queue_priority and read the next available timeslot

Read, reply to, hide, pin, and like comments on a post, and send a private reply from a comment

List chats and send, edit, or react to direct messages on a connected profile

GET STARTED

Start building with Postproxy Social Media API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Postproxy Social Media API for, with concrete tasks.

★ Agent-run cross-posting through Jentic

A developer wants their agent to announce each release on every channel they use. Through Jentic the agent finds the Postproxy create-post operation by intent, sends the post body with a profiles array such as twitter and linkedin, and reads the per-platform outcome. The bearer key is attached by your own instance, and a rule can keep the agent to creating drafts so a human publishes them.

Call POST /api/posts with post.body set to the release note, post.draft true, and profiles twitter, linkedin, and bluesky, then publish it with POST /api/posts/{id}/publish after approval

Queued posting calendar

Instead of picking exact times, a content team fills a queue and lets Postproxy space posts out. A queue is created once, posts are added with queue_id and an optional queue_priority, and the next-slot operation shows when the next post will go out. Passing scheduled_at together with queue_id is not allowed, since the queue sets the time.

Call POST /api/posts with queue_id q_123 and queue_priority high, then call GET /api/post_queues/{id}/next_slot to report when it will publish

Comment and DM inbox triage

Community managers need one place to see and answer replies. Postproxy lists comments across posts or on a single post, creates replies, hides or pins comments, and sends a private reply that moves a public comment into DMs. Chats and messages can be listed per profile, filtered by direction and status, and answered from the same API.

Call GET /api/comments for the last 24 hours, then reply to each unanswered question with POST /api/posts/{post_id}/comments

Performance reporting

A weekly report needs engagement per post and audience growth per profile. GET /api/posts/stats returns stats for chosen post_ids or profiles over a from and to range, while the profile stats, daily stats, and follower history operations return time series for a connected profile and placement.

Call GET /api/profiles/{id}/follower_history and GET /api/profiles/{id}/daily_stats with from and to set to last week and summarise the change in followers

Google Business listing upkeep

Local businesses need their Google Business details kept current. Postproxy reads and updates a location, replaces opening hours, attributes, service lists, and food menus, manages place action links, and adds or removes profile media for a connected Google Business profile.

Call PATCH /api/profiles/{profile_id}/google_business/update_hours with the holiday hours for location_id loc_1 and confirm with GET /api/profiles/{profile_id}/google_business/location

Key Endpoints

140 endpoints — the postproxy social media api publishes one post payload to facebook, instagram, tiktok, linkedin, youtube, x (twitter), threads, pinterest, bluesky, telegram, and google business, mapping it to each platform's rules and returning a per-platform outcome.

METHOD

PATH

DESCRIPTION

POST

/api/posts

Create, schedule, or queue a post

POST

/api/posts/{id}/publish

Publish a draft post

GET

/api/posts

List posts by status and platform

GET

/api/posts/stats

Get post stats

GET

/api/comments

List comments across posts

POST

/api/chats/{chat_id}/messages

Send a direct message

GET

/api/post_queues/{id}/next_slot

Get next available timeslot

GET

/api/profiles/{id}/follower_history

Get follower history

POST

/api/posts

Create, schedule, or queue a post

POST

/api/posts/{id}/publish

Publish a draft post

GET

/api/posts

List posts by status and platform

GET

/api/posts/stats

Get post stats

GET

/api/comments

List comments across posts

POST

/api/chats/{chat_id}/messages

Send a direct message

GET

/api/post_queues/{id}/next_slot

Get next available timeslot

GET

/api/profiles/{id}/follower_history

Get follower history

Why Jentic?

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

Setup

Wiring Postproxy by hand means managing a bearer key that may be full-access or profile-group scoped, passing profile_group_id where needed, adding Idempotency-Key headers to writes, and learning which operations only work on certain platforms. Through Jentic you install once, import Postproxy from the API Directory, store the key once, and your agent calls it.

Permission scoping

Postproxy puts the profile id in the URL path for comments, chats, stats, Google Business, and WhatsApp operations (/api/profiles/{profile_id}/...), so a rule can pin your agent to one profile there. Post creation carries its target profiles in the request body, so for publishing a rule bounds the operation rather than the profile. You choose the operations it may call, so destructive ones like deleting a post on the platforms or revoking an API key are not included unless you add them.

Credential isolation

Your Postproxy 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 post to LinkedIn' or 'reply to a comment', and Jentic returns the matching Postproxy operation from its large surface with its input schema, so the agent does not have to read through the full reference.

FAQs

Specific to using Postproxy Social Media API through Jentic.

What authentication does the Postproxy Social Media API use?

Postproxy authenticates with an API key sent as a bearer token in the Authorization header, per its OpenAPI spec. Keys are either full-access to the whole account or scoped to a single profile group, and are created in the Postproxy dashboard under Settings, API Keys. Through Jentic the key is stored by your own instance and attached at call time.

Can I schedule a post to several platforms with one call?

Yes. POST /api/posts takes a profiles array of profile ids or platform names such as twitter or instagram, a post object with body, and either scheduled_at for a fixed time, draft true for review, or queue_id to let a queue pick the slot. All resolved profiles must belong to the same profile group, and the response reports the outcome per platform.

What are the rate limits for the Postproxy API?

The OpenAPI spec defines a RateLimited response for when a posting rate limit is reached but does not state the numbers. Check https://postproxy.dev/reference/overview/ for current limits, and send an Idempotency-Key header on writes so a retry after a rate-limit error does not publish twice.

Is there a Postproxy MCP server?

You don't need an MCP server to give your agent Postproxy. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent discovers the posting, comment, and stats operations it needs on demand instead of loading the whole surface into its context up front.

Can I limit what my agent is allowed to do with Postproxy?

Yes. For instance, write a rule that allows POST /api/posts, GET /api/posts/{id}, and GET /api/profiles/{profile_id}/comments, and the agent can create posts and read one profile's comments but cannot delete posts, remove them from platforms, or revoke API keys. Pairing that rule with a Postproxy key scoped to one profile group narrows it further, and every call is logged.

How do I publish a draft post through Jentic?

Search Jentic for 'publish a draft social media post', load POST /api/posts/{id}/publish, and execute it with the draft's id; then call GET /api/posts/{id} to read the per-platform result. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Postproxy Social Media API

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Official vendor OpenAPI document · agent-readySocial MediaSocial Publishingbearer140 EndpointsREST

For Agents

Publish, schedule, and queue posts across eleven social platforms from one payload, reply to comments and DMs, and read post and profile stats through Postproxy.

Use for: Post this announcement to LinkedIn, X, and Bluesky at once, Schedule an Instagram post for Friday at 9am, I need to add a post to my weekly posting queue, List new comments on yesterday's post

Not supported: Does not generate post images or video, run paid ad campaigns, or provide social listening across accounts you do not own. Use for publishing to and managing your connected social profiles only.

The Postproxy Social Media API publishes one post payload to Facebook, Instagram, TikTok, LinkedIn, YouTube, X (Twitter), Threads, Pinterest, Bluesky, Telegram, and Google Business, mapping it to each platform's rules and returning a per-platform outcome. Posts can be published now, scheduled with scheduled_at, saved as drafts, or added to a posting queue that picks the next free timeslot. Beyond publishing, it reads and replies to comments, reads and sends direct messages, manages WhatsApp templates and groups, edits Google Business locations and Facebook Pages, and reports post and profile stats. Sandbox mode is available on all plans for development without real accounts.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B-Signals: 4

92%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

50%

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.

50%

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

67%

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.

54%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A-Signals: 1

71%

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

74%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Postproxy Social Media API to your agent

Capabilities

Start building with Postproxy Social Media API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Postproxy Social Media API

Jentic AI Readiness Score

Postproxy Social Media 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