Skip to content

API

Social media platform capabilities API

The SkedCast social media platform capabilities API — /developers/data/platform-capabilities.json — is a real, generated JSON file: caption limits, media caps, pacing defaults, native-scheduling support and OAuth scopes for every platform SkedCast supports, read directly from the same PLATFORM_CAPABILITIES and COMPOSER_PROFILES registries the product enforces at publish time.

Browse docs

3 min read

Why this social media platform capabilities API exists#

facts.json and llms.txt already give an AI agent SkedCast's own product facts. Neither one previously carried per-platform publishing limits, pacing caps, or which platforms support native server-side scheduling — an agent that needed those had to scrape a rendered guide page. This route closes that gap as structured data.

Nothing in this file is hand-typed: it is generated at request time from the exact registries the composer, the bulk validator, and the quota-aware router already read. A limit that changes in the product changes here at the same moment, not on the next content update.

Shape (one entry, abridged)#

json
{
  "platform": "x",
  "displayName": "X (Twitter)",
  "isActive": true,
  "nativeSchedule": false,
  "caption": { "maxChars": 280, "weightedCharCount": true, "urlCharCost": 23, "maxHashtags": null },
  "media": { "maxMediaAdapterHonest": 4, "maxMediaPlatformTheoretical": 4, "postTypes": ["text", "image", "video", "gif", "poll", "thread"] },
  "pacing": { "defaultDailyCap": 100, "defaultMinIntervalSec": 300, "platform24hHardCap": null },
  "access": { "oauthScopes": ["tweet.read", "tweet.write", "users.read", "offline.access", "media.write"], "approvalRequired": false },
  "costModel": { "perPostUsd": 0.015, "perUrlPostUsd": 0.2 }
}
One real entry from the live endpoint — field names and values are generated, not illustrative.
jsonapiagentsplatform limits

FAQ

Is /developers/data/platform-capabilities.json a real, working endpoint?
Yes — it returns real JSON generated from SkedCast's own capability registry on every request, not a static mock file.
How is this different from /facts.json?
/facts.json covers SkedCast's own product facts (plans, feature availability, platform count). This route covers per-PLATFORM publishing facts — caption limits, media caps, pacing, native-scheduling support — at a level of detail facts.json does not carry.
Can this data go stale relative to the actual product?
No — it is generated at request time from the same registries the composer and publish pipeline read, so it reflects the product's real enforced limits at the moment of the request.

Ready to broadcast everywhere?

Sign up free — no credit card. You land on the Free plan, and you can start a one-time 7-day Studio trial from your workspace whenever you are ready. Connect your first accounts, import a batch, and watch one post fan out across every platform.