{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/social-media.schedule-calendar/",
    "json": "https://www.anchorterminal.com/niches/social-media.schedule-calendar/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/social-media.schedule-calendar/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/social-media.schedule-calendar/index.min.md"
  },
  "markdown": "One company's docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 1 | 14 | 19 | 11 | 6 |\n\n## What counts as done\n\nEvery post is stored as scheduled at the stated instant with an explicit timezone, listable afterwards with its state.\n\nMeasured, for our own tests: each publishes within 5 minutes of its time.\n\nHow 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\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **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.\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n\n- 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.\n- not this job: TwitterAPI.io MCP (Prism Digital, LLC): No scheduling; the MCP is read-only.\n- not this job: X MCP (X Corp.): No scheduling tools; Articles can be drafted and published but not scheduled.\n- not this job: Xpoz MCP (XPOZ): No scheduling or posting tools.\n\n1 listings in the category were added after this reading and aren't marked yet.\n\n## What stops agents finishing\n\n- a shared vendor app hits a network's daily cap at publish time, after the post was accepted\n- the scheduling endpoint rejects valid future times\n- a connection's token expires between scheduling and publishing\n\n## Around it\n\nBefore: llm.draft-copy, spreadsheets.read-rows. After: social-media.confirm-delivery, social-media.performance-report.\n\n## Where this comes from\n\nWeight 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\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Schedule a batch of posts on a calendar",
        "url": ""
      }
    ],
    "description": "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.",
    "facts": null,
    "h1": "Schedule a batch of posts on a calendar",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/social-media.schedule-calendar/",
    "published": "",
    "section": "agents",
    "title": "Schedule a batch of posts on a calendar: who does it | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/social-media.schedule-calendar/"
  },
  "tokens": {
    "markdown": 1600,
    "slim": 330
  },
  "version": 1
}
