Inklate for agents

Inklate was built for a world where AI agents do the posting. Everything an agent can do — discover channels, author cross-platform posts, preflight against each platform’s real rules, schedule, publish, and pull metrics — goes through the same guarded API the dashboard calls, with the same membership checks, permissions, and validation. There is no weaker, separate agent path.

Why Inklate is agent-native

The dashboard and an agent both call one code path behind the scenes, so a human and an agent can never diverge. An agent is subject to exactly the rules a person is: the same organization membership, the same role-based permissions, the same per-platform content validation. What you can do in the UI, an agent can do over the API — and what an agent does shows up in the dashboard immediately, with no sync step.

This parity is structural, not a promise: a draft an agent creates appears in the drafts sidebar, a placement it schedules lands on the calendar in your local time, and metrics it pulls are the same snapshots the analytics charts read.

The core model

Authoring is cross-platform. One Story (a document or markdown) fans out into per-channel Renditions, and each Rendition publishes to a channel at a time as a Placement. Write the Story once; each placement’s rendition is adapted from it unless the agent supplies explicit variants. The preflight → fix → sync tools are the levers over that fan-out.

See Core concepts for the full vocabulary.

Two ways to connect

Both accept the same auth: an Organization API key created in the dashboard, or OAuth 2.1 for clients that support remote-MCP browser sign-in. Both operate on the same organizations, channels, and posts.

There is no separately published client SDK; the REST surface is described by an OpenAPI spec you can generate a typed client from, and the MCP server exposes the same capabilities as ready-to-call tools.

Where to start