Core concepts

Inklate has a small vocabulary that the rest of the docs assume. Work happens inside an organization; you connect channels to it; and every post moves through three shapes — a story, its per-platform renditions, and the placements that publish each rendition to a channel at a time. Learn these five words and the product reads plainly.

Organization

An organization is Inklate’s workspace — the container for your channels, posts, teammates, and billing. You run one per brand or client, and everything you do belongs to exactly one of them.

Switching organizations switches the whole surface: a different set of connected channels, a different post calendar, a different team, and a separate plan. Members, roles, and approvals are scoped here too, so a teammate you add to one organization has no visibility into another. Billing is per-organization as well — each has its own subscription.

Channel

A channel is a single connected social destination that posts can go to — one LinkedIn profile, one LinkedIn page, one X account, one Instagram professional account, or one Facebook page. LinkedIn (profiles and pages), X, Instagram, and Facebook are live today; Threads and Mastodon are coming soon and not yet connectable.

You connect a network once, through its own OAuth screen, and each destination it grants becomes its own channel. A single LinkedIn authorization, for example, can add both your personal profile and any pages you manage — two separate channels from one connection. Channels carry their own health and token-expiry status, because a network can revoke access at any time.

Story, rendition, placement

This is the core model, and it is what lets you compose once and publish natively everywhere.

• Story — the platform-agnostic post. You write it once: the text, the images, the video, the idea. A story knows nothing about any specific network.
• Rendition — the story adapted to one provider and format. Each network gets its own rendition, with platform-native formatting and any per-channel edits you make. You can tune one rendition without touching the others.
• Placement — a rendition scheduled or published to a specific channel at a specific time. Placements are what actually go live, and each one succeeds or fails on its own — one network failing never blocks the rest.

The practical payoff: your message stays consistent while each platform receives a version shaped to its rules. Inklate validates every rendition against that platform’s real limits — length, media counts, aspect ratios — before anything publishes.

Labels

Labels organize posts within an organization. They are lightweight tags you apply to posts so you can group and filter work — by campaign, client, theme, or whatever your team tracks. They do not change where or when a post publishes; they exist purely to keep a busy calendar navigable.

One guarded API for humans and agents

Everything above is reachable two ways: through the dashboard, and through Inklate’s MCP server and REST API. Both paths go through the same guarded API with the same permissions and the same validation — an agent connecting a channel, drafting renditions, or scheduling placements is subject to exactly the rules a person is. There is no separate, weaker agent path; agents are first-class operators of the same model.

Times are stored in UTC

Inklate stores every time in UTC and shows it to you in your local timezone. When you schedule a placement, you enter the time you mean in your own zone; Inklate records it as UTC and displays it back correctly wherever it is read. Teammates in different timezones each see the same moment in their own local time.