Publishing & calendar
How this is scored
Scheduling across networks: per-network formatting, the calendar as a working surface, bulk operations, and what happens when a post fails.
0 — No publishing or scheduling; the product is a listening, analytics or inbox tool only.
3 — Posts scheduled to several networks from one composer, with a list or calendar of what is planned.
5 — A content calendar with scheduling across the main networks, per-network text and media variants, drafts, and post previews.
8 — Bulk upload or CSV import, queue or evergreen scheduling, best-time suggestions, link shortening with UTM tags, stories, reels or shorts where the API allows, and failure notifications with a retry.
10 — Publishing is dependable at volume: hundreds of scheduled items across many accounts without collision, best-time recommendations from the account's own history, and every failure surfaced with the platform error and a one-click recovery.
The Skeptic
The developer pages document a real publishing pipeline: a message-composer endpoint with per-network service selection, content types from status to carousel, Instagram Reels, drafts, a calendar module, and an endpoint returning what is posted or scheduled, with a lifecycle running draft to pending to published and an error state. That is a working calendar with per-network variants; we found no public information on bulk upload, queue or evergreen scheduling, best-time suggestions, or failure notifications with a retry, so dependability at volume rests entirely on undocumented ground. 2 3 4