Install Jentic One Beta

Connect the SocialClaw API to your agent

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

Connect social accounts through a guided connection flow and list each account's publishing capabilities

Schedule and publish posts to connected accounts, then track every delivery attempt

Publish draft runs on demand and reconcile posts whose provider status has drifted

Upload, import, and register media assets for use in posts

Retrieve post, account, and run analytics and refresh post metrics on demand

GET STARTED

Start building with SocialClaw API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use SocialClaw API for, with concrete tasks.

★ Agent-Driven Social Publishing

An AI agent connects a social account, uploads the media, schedules a post, and publishes it without a human wiring each provider by hand. The agent starts a connection, registers an asset, applies a run, and then publishes that run, checking the delivery attempts afterward to confirm the post went live. Jentic exposes each SocialClaw operation with its input schema so the agent fills the right fields on the first call.

Connect an Instagram account, upload a video asset, create a run scheduled for Friday at 09:00, publish it, and confirm the delivery attempt succeeded

Scheduled Content Calendar

A content team queues a week of posts across several connected accounts and lets the schedule drive publishing. The SocialClaw API validates each schedule, previews the campaign, and publishes draft runs at the planned time, exposing run status and a run table so the calendar stays accurate. Posts that fail at the provider can be retried or reconciled rather than silently lost.

List posts scheduled for the next seven days, then preview the campaign for a run before it publishes

Post-Performance Reporting

A growth team pulls engagement numbers for published posts and rolls them up by account and by run. The SocialClaw API serves post analytics, account analytics, and run analytics, and can refresh post metrics on demand so a report reflects the latest provider figures. The result is a single reporting flow over every connected profile.

Refresh analytics for a published post, then retrieve the account analytics for the owning profile

Media Asset Pipeline

An app lets users drop in images and video that later attach to scheduled posts. The SocialClaw API registers an asset, uploads it directly or imports it from a URL, and serves it back through signed delivery URLs, with multipart upload steps available for larger files. Assets can be listed and deleted so the library stays tidy.

Key Endpoints

91 endpoints — the socialclaw api connects social accounts, schedules posts, and publishes them across those accounts while tracking every delivery attempt.

METHOD

PATH

DESCRIPTION

POST

/v1/connections/start

Start a connection to a social account

GET

/v1/accounts

List connected accounts

POST

/v1/posts/apply

Create a run from a post plan

POST

/v1/runs/{runId}/publish

Publish a draft run

GET

/v1/posts

List posts

POST

/v1/assets/upload

Upload a media asset

GET

/v1/analytics/posts/{postId}

Read analytics for one post

POST

/v1/connections/start

Start a connection to a social account

GET

/v1/accounts

List connected accounts

POST

/v1/posts/apply

Create a run from a post plan

POST

/v1/runs/{runId}/publish

Publish a draft run

GET

/v1/posts

List posts

POST

/v1/assets/upload

Upload a media asset

GET

/v1/analytics/posts/{postId}

Read analytics for one post

Why Jentic?

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

Setup

Wiring the SocialClaw API by hand means managing its bearer token, the per-provider connection flow for each social account, and the asset upload and post-reconcile steps yourself. Through Jentic you install once, import SocialClaw from the API Directory, store the token once, and your agent calls it.

Permission scoping

SocialClaw puts the account id in the URL path (/v1/accounts/{accountId}/...), so a rule can pin your agent to one connected account and the operations you pick, such as listing posts and publishing. You choose the operations it may call, so destructive ones like disconnecting an account or deleting an asset are not included unless you add them.

Credential isolation

Your SocialClaw 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 post' or 'check post analytics', and Jentic returns the matching SocialClaw operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using SocialClaw API through Jentic.

What authentication does the SocialClaw API use?

The SocialClaw API authenticates programmatic calls with a bearer token in the Authorization header per its OpenAPI spec. Dashboard-session calls instead use a socialclaw_dash_session cookie, and inbound webhooks are verified with an x-signature header. Public endpoints like health checks, media delivery, and OAuth callbacks need no credential. Through Jentic the bearer token is stored encrypted by your own Jentic One instance and injected at call time.

Can I schedule and publish posts with the SocialClaw API?

Yes. You apply a run from a post plan, publish that draft run when you are ready, and the API tracks each delivery attempt per connected account. If a provider rejects a post you can retry it or reconcile its status, and validate a schedule before anything goes out.

What are the rate limits for the SocialClaw API?

The SocialClaw OpenAPI spec does not publish fixed rate limits. The workspace usage endpoint reports your current usage, so your agent can read consumption before sending more requests rather than guessing a ceiling.

Is there a SocialClaw MCP server?

You do not need an MCP server to give your agent the SocialClaw API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls its operations. Operations are discovered on demand, so your agent's context stays lean instead of loading a full tool list up front.

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

Yes. Write a rule that allows only the read and publish operations under one connected account id, so the agent can list posts, schedule, and publish for that account and touch nothing else, and every call it makes is logged. Account-disconnect and asset-delete operations stay out of the allowed set unless you add them.

How do I publish a scheduled post with the SocialClaw API through Jentic?

Search Jentic for 'schedule and publish a social media post', and it returns the SocialClaw run and publish operations with their input schemas. Your agent applies a run, publishes it, and reads the delivery attempts to confirm the post is live. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Getsocialclaw SocialClaw API

AI ReadinessFoundational (C+)60/100

See full scorecard

Official vendor OpenAPI document · agent-readySocial MediaSocial Publishingbearer, apiKey91 EndpointsREST

For Agents

Connect social accounts, schedule and publish posts, upload media, and pull post, account, and run analytics across connected social profiles.

Use for: I want to connect a new social account, Schedule a post to publish next week, Publish a draft run now, Check the analytics for a published post

Not supported: Does not handle ad campaign buying, audience targeting, or direct messaging. Use for scheduling and publishing posts to connected social accounts only.

The SocialClaw API connects social accounts, schedules posts, and publishes them across those accounts while tracking every delivery attempt. It covers media asset upload and import, campaign previews, and draft runs you publish on demand, with reconcile and retry paths for posts whose provider status drifts. Per-post, per-account, and per-run analytics, signed media delivery URLs, and inbound webhooks round out the publishing pipeline for connected social profiles.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C+Signals: 4

94%

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

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.

49%

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

83%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

59%

OperationId Quality

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

51%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

87%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1

53%

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

66%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the SocialClaw API to your agent

Capabilities

Start building with SocialClaw API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Getsocialclaw SocialClaw API

Jentic AI Readiness Score

SocialClaw 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