Send a GET request to https://skedcast.com/developers/data/platform-capabilities.json. It is public and needs no API key.

How is this different from /facts.json?

/facts.json covers SkedCast's own product facts (plans, feature availability, platform count). This file covers per-PLATFORM publishing facts: caption limits, media counts, pacing, native-scheduling support. facts.json does not carry that detail.

How current is the data?

It is generated from the limits SkedCast applies when you publish. Responses are cached for up to a day, so a change can take that long to appear.

Platform capabilities (JSON)

Browse docs

3 min read

POST /v1/postsREST · OpenAPI · MCP

bash

curl -X POST https://api.skedcast.com/v1/posts \
  -H "Authorization: Bearer sked_live_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "clientId": "6d58a0f2-1c3e-4b7a-9f21-0a1b2c3d4e5f",
    "content": "New drop is live 🔥",
    "targets": { "mode": "group", "clientId": "6d58a0f2-1c3e-4b7a-9f21-0a1b2c3d4e5f" },
    "schedule": { "type": "at", "scheduledAt": "2030-01-15T15:00:00Z" }
  }'

json

{
  "data": {
    "postId": "f27e6cf1-8b2b-4c1a-9c0e-6a2b7e8f1d3a",
    "status": "scheduled",
    "targetCount": 24
  },
  "meta": { "correlationId": "c-74fb602e-…" }
}

What it is for#

/facts.json and llms.txt give an AI agent SkedCast's own product facts. This file adds the per-platform publishing limits, pacing defaults, and which platforms support native server-side scheduling, as structured data. You don't have to scrape a guide page to get them.

Shape (one entry, abridged)#

json

{
  "platform": "x",
  "displayName": "X (Twitter)",
  "nativeSchedule": false,
  "revokesAccessOnDisconnect": true,
  "caption": { "maxChars": 280, "weightedCharCount": true, "urlCharCost": 23, "maxHashtags": null },
  "media": { "maxMediaPerPost": 4, "platformMaxMediaPerPost": 4, "postTypes": ["text", "image", "video", "gif", "poll", "thread"] },
  "pacing": { "defaultDailyCap": 100, "defaultMinIntervalSec": 300 },
  "access": { "oauthScopes": ["tweet.read", "tweet.write", "users.read", "offline.access", "media.write", "users.email"], "accountTypeRequired": null }
}

One entry from the live file, shortened. Field names and values come from the file.

Fields#

Field	Meaning
`nativeSchedule`	Whether SkedCast can hand a scheduled post to the platform's own scheduler.
`revokesAccessOnDisconnect`	Whether disconnecting an account in SkedCast also revokes SkedCast's access on the platform. When `false`, access stays until the person removes it on the platform.
`caption.maxChars`	The caption character limit.
`caption.weightedCharCount`	`true` when the platform weighs characters unevenly (X).
`caption.urlCharCost`	How many characters a URL counts as, where that is fixed.
`caption.maxHashtags` / `caption.maxMentions`	The hashtag and mention limits, or `null` when the platform sets none.
`media.maxMediaPerPost`	The most media items SkedCast publishes in one post.
`media.platformMaxMediaPerPost`	The most media items the platform itself allows in one post.
`media.postTypes`	The post types SkedCast can publish to the platform.
`pacing.defaultDailyCap` / `pacing.defaultMinIntervalSec`	SkedCast's per-account pacing defaults: posts per day, and the minimum seconds between two posts.
`access.oauthScopes`	The OAuth scopes SkedCast requests when an account connects.
`access.accountTypeRequired`	The account type needed to publish (for example `business_or_creator`), or `null` when any account works.

jsonapiagentsplatform limits

FAQ

How do I fetch it?: Send a GET request to https://skedcast.com/developers/data/platform-capabilities.json. It is public and needs no API key.
How is this different from /facts.json?: /facts.json covers SkedCast's own product facts (plans, feature availability, platform count). This file covers per-PLATFORM publishing facts: caption limits, media counts, pacing, native-scheduling support. facts.json does not carry that detail.
How current is the data?: It is generated from the limits SkedCast applies when you publish. Responses are cached for up to a day, so a change can take that long to appear.

Platform capabilities (JSON)

What it is for#

Shape (one entry, abridged)#

Fields#

FAQ

Ready to broadcast everywhere?