Changelog

Every notable change to Inklate, newest first. Each entry links to the documentation for the feature it announces.

2026-07 — One call to post

• 2026-07-28 — The post API, redesigned: 18 operations become 7. One composed call now takes a post from nothing to drafted, scheduled, or published: POST /posts accepts content, channels (ids or provider names like "x"), schedule ("now", a future instant, or omitted for a draft), per_channel overrides, media, labels, and a campaign. Every response — create, update, get, and the dry-run validate — carries per-channel validation: ready, errors with real numbers and machine fixes, warnings, and the autofix repairs applied server-side. A draft with errors saves; only scheduling or publishing refuses, atomically. The standalone preflight, fix, sync, schedule, unschedule, and status operations are gone — the composed call replaced them across REST, MCP, the CLI, and the SDK. Approvals are now operable over MCP (approvals_rule, approvals_request, approvals_decide), and agents can no longer move money over MCP — billing tools are read-only, with checkout and top-ups staying in the dashboard. See the Quickstart and Never gets rejected.

2026-07 — Plans and the AI-credit wallet

• 2026-07-24 — Fair plan changes: upgrades now, downgrades at renewal. Plan changes follow one rule — Ink follows money. Upgrades apply immediately with a prorated charge and show exactly how much Ink is added to your balance today; downgrades are scheduled for your next billing date, so you keep the plan (and Ink) you paid for until then, with a one-click undo. Plan Ink now properly resets each cycle (top-up Ink never expires), and admins get a one-per-cycle heads-up when the balance runs low. See Billing.
• 2026-07-24 — Ink credits, two plans, and a new payment provider. Billing moved to “one balance, one plan”: two plans — Pro ($20/mo) and Team ($30/seat/mo), two months free on annual — with unlimited brands and channels on paid. Skill runs and AI actions spend Ink from one prepaid account balance (500 Ink/mo on Pro, 2,500 on Team), with $8 top-ups and a full usage ledger — Ink is prepaid, so there’s never a surprise bill. One subscription covers all your brands — a second brand attaches to it, never a new charge. Payments are processed by DodoPayments as merchant of record. See Billing.

2026-07 — Analytics and the agent surface

• 2026-07-12 — Operations dashboard and per-post metrics. An organization-wide dashboard tracks what’s queued, published, and failing, alongside per-post metrics synced from each platform. See Analytics and Metrics.
• 2026-07-11 — Seat-based billing. A single plan priced per seat, with a 14-day free trial and in-app upgrade. Superseded by the two-plan Ink pricing above (2026-07-24). See Billing.
• 2026-07-10 — MCP server and REST API. Claude and any MCP client can connect channels, draft, validate, schedule, and publish through the same guarded API the dashboard uses. See For agents and the MCP guide.
• 2026-07-10 — Approvals and collaboration. Approval lanes with a reviewer queue, org roles and permissions, and conflict-safe concurrent edits (optimistic concurrency — a stale write is refused, never clobbered). See Approvals.

2026-07 — Launch

The initial public release of Inklate.

• Cross-platform composer. Write one story and publish it natively to LinkedIn, X, Instagram, and Facebook. See Composer and Writing.
• Write once, native everywhere. Each channel gets its own tab and platform-native preview; edit any channel’s version independently without touching the others. See Write once, native everywhere.
• Media and video upload. Attach images and video, validated against each platform’s limits before publishing. See Media.
• The fit check. Inklate checks every channel against that platform’s real rules — length, media counts, aspect ratios — and flags anything that would fail with a suggested fix. See Never gets rejected.
• Scheduling and calendar. Per-channel scheduling in your local timezone, with a calendar of everything queued and published. See Scheduling and the Calendar.
• Passwordless sign-in and encrypted tokens. Google or email-code sign-in, social tokens encrypted at rest, and per-organization data isolation. See Security.