# Schedule a batch of posts on a calendar

> Schedule a batch of posts on a calendar: 1 companies fully do it, 14 with a limit, 19 carry the tag. Every listing in Social media posting APIs with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/social-media.schedule-calendar/
- Markdown: https://www.anchorterminal.com/niches/social-media.schedule-calendar/index.md (~1,600 tokens)
- Slim: https://www.anchorterminal.com/niches/social-media.schedule-calendar/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/social-media.schedule-calendar/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 14 | 19 | 11 | 6 |

## What counts as done

Every post is stored as scheduled at the stated instant with an explicit timezone, listable afterwards with its state.

Measured, for our own tests: each publishes within 5 minutes of its time.

How agents ask for it: schedule these ten posts over the next two weeks; plan and queue a month of content; put this in the next free slot; post this every Tuesday at 9

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Typefully (Typefully Inc.)**: publish_at takes ISO 8601 with a timezone or next-free-slot, drafts list by status and update by id, and webhooks fire on schedule and publish; no publish-latency figure is given.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Ayrshare API + MCP (Neverminds Solution LLC)**: scheduleDate takes a UTC ISO time and returns status scheduled, history lists posts with state, but no publish-latency figure is given and errors at publish time arrive only by webhook or /history.
- **Blotato (Blotato Inc.)**: scheduledTime is UTC ISO 8601 and echoed back, scheduled posts are listed and editable by id, but there is no timezone field and no publish-latency figure.
- **Buffer API + MCP (Buffer, Inc.)**: customScheduled takes dueAt in ISO 8601 UTC, posts are listed by status and editable by id; no named timezone is taken and no publish-latency figure is given.
- **bundle.social (BUNDLE SP. Z O.O.)**: postDate in UTC ISO with SCHEDULED, RETRYING, ERROR and REVIEW states listable and retryable; no named timezone is taken, and per-account daily caps and the YouTube organisation cap can fail a post at publish time.
- **Zernio (formerly Late) API + MCP (ZERNIO SOFTWARE SL)**: scheduledFor with an offset or an IANA timezone, listable states, editable by PUT; but TikTok posts beyond the daily cap are held and published later, so the 5-minute bar is not guaranteed.
- **Metricool API + MCP (METRICOOL SOFTWARE, S.L.)**: publicationDate takes a dateTime and an IANA timezone, and posts are listed between dates, fetched and edited by id; publish latency and per-network outcome are not documented, and Free caps at 20 scheduled posts.
- **Mixpost API + MCP (INOVECTOR DIGITAL S.R.L.)**: date and time are read in a given timezone and stored as UTC, posts are listable; an open issue reports the API rejecting valid future UTC dates as past and add-to-queue ignoring custom dates.
- **OneUp API + MCP (OneUp, Inc.)**: Posts are listable by scheduled, published, failed and draft state and editable, but scheduled_date_time is YYYY-MM-DD HH:MM with no timezone field, so the account's timezone governs.
- **Post Bridge API + MCP (Post Bridge)**: scheduled_at or use_queue, posts listed and patched by id, and per-account results; the schema gives no timezone rule beyond a date-time, and publish latency is not stated.
- **Postiz API + MCP (Gitroom Limited)**: date is UTC ISO, posts are listed and can move between draft and queue; an open issue shows Cloud accepting a TikTok Direct Post and failing at publish time on the shared app's daily active-user cap.
- **Publer API + MCP (Kalemi Code)**: scheduled_at takes ISO 8601 with Z or an offset, posts list by state including scheduled_reauth and failed, and reschedule echoes the time; no publish-latency figure, and a one-minute gap per account is required.
- **Repostit (Repostit LLC)**: A Brief is scheduled at an exact future time with a timezone given in the request and all destinations share it; no tool schema shows the stored time being echoed or the publish latency.
- **SocialCannon (Tiny Red Pixel Ltd)**: scheduledAt is ISO 8601 within a 30-day window, posts list by status with a cursor and the workspace has a configured timezone; no publish-latency figure, and accounts under restriction hold posts as awaiting_account.
- **Upload-Post API + MCP (TONVI TECH SL)**: scheduled_date with an IANA timezone, scheduled posts listed and patched by job_id; but an open MCP issue shows youtubePublishAt dropped, leaving videos private instead of scheduled.

- not this job: Sprout Social API (Sprout Social, Inc.): Posts can be created only as drafts, even with delivery details, so nothing is scheduled to publish without a person in Sprout.
- not this job: TwitterAPI.io MCP (Prism Digital, LLC): No scheduling; the MCP is read-only.
- not this job: X MCP (X Corp.): No scheduling tools; Articles can be drafted and published but not scheduled.
- not this job: Xpoz MCP (XPOZ): No scheduling or posting tools.

1 listings in the category were added after this reading and aren't marked yet.

## What stops agents finishing

- a shared vendor app hits a network's daily cap at publish time, after the post was accepted
- the scheduling endpoint rejects valid future times
- a connection's token expires between scheduling and publishing

## Around it

Before: llm.draft-copy, spreadsheets.read-rows. After: social-media.confirm-delivery, social-media.performance-report.

## Where this comes from

Weight 11 of 100 in Social media posting APIs: 6 of 57 use-case tags; scheduling is in every vendor's pitch but accounts mostly report it through failures at publish time

As data: https://www.anchorterminal.com/api/v1/use-cases/social-media.schedule-calendar.json, or the MCP tool get_use_case with id social-media.schedule-calendar. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
