The API is not a separate developer tier. It is on every paid plan, with the same rate limits published in the docs and an API key you generate yourself.
Free plan, no card needed
curl https://api.eksis.io/v1/posts \
-H "Authorization: Bearer $EKSIS_KEY" \
-H "Content-Type: application/json" \
-d '{"mode":"schedule",
"scheduledAt":"2026-09-20T09:00:00+07:00",
"baseCaption":"Weekend restock",
"targets":[{"socialAccountId":"<channel-id>",
"contentType":"text"}]}'{ "data": {
"id": "<post-id>",
"status": "scheduled",
"scheduledAt": "2026-09-20T02:00:00.000Z" } }GET /v1/posts/<post-id>
{ "data": { "status": "published",
"targets": [{ "status": "published",
"permalink": "https://…" }] } }Posts with their schedules and approvals, media uploads, the connected accounts, incoming comments and direct messages, and analytics. Anything the interface can do to a post, a request can do to the same post. The screens and the API run against one service, not two.
Publishing runs in the background: the request returns once the post is queued, and reading the post back shows each channel's status, its link, and the reason a platform gave if it refused. Every response also says how many requests are left in today's quota.
Publish a product post the moment stock lands, mirror a CMS release to every channel, or route comments into the helpdesk you already run. Rate limits are stated up front so a batch job can be paced instead of discovered the hard way.
The same API is available as an MCP server. Connect Claude, ChatGPT, Cursor, or any other MCP client to a workspace and ask it to draft a week of posts, schedule them into the queue, or answer the comments and direct messages that came in overnight. It signs in with your account or an API key, acts with your role, and shares the API quota.
Connect an account, schedule your first week, and see whether it fits. No card, no trial countdown.
Create a free workspace Free plan, no card needed