Definition

The social media API
built for AI agents.

A social media API for AI agents is not a scheduler with a REST wrapper. It is a contract an agent can reason over: one publish call, one response shape, retries that cannot double-post, and analytics in the same names on every network. PostLake is that contract. REST for LangGraph and CrewAI. A hosted MCP server for Claude, Cursor and ChatGPT. Agent skills for coding agents. Same accounts underneath.

Free tier. No card · one API for every network · full MCP access

Before you start

Same setup the docs quickstart uses. Do this once:

1. Sign up at app.postlake.dev and verify your email (unlocks free credits).
2. On Channels, create a profile (e.g. my-brand) and connect at least one account. Bluesky is the fastest first channel: no app review. Instagram/TikTok/Facebook need each platform's review before API posting.
3. Account menu → API Keys → create a key (sk_live_…). It shows once; treat it like a password.

Give any MCP client the posting API

This is the whole agent setup. Paste it into Claude, Cursor, ChatGPT or any MCP host. The agent gets publish, schedule, media and analytics as tools, not nine platform SDKs.

{
  "mcpServers": {
    "postlake": {
      "url": "https://api.postlake.dev/mcp"
    }
  }
}

Make it work

Tool-specific glue on top of the shared setup above:

1. Decide how the agent talks to PostLake: MCP (OAuth, no key in chat), agent skills (npx skills add postlake/postlake-mcp --all), or REST with a Bearer key in your runtime.
2. Connect the social accounts the agent may use under one profile. Bluesky is the fastest smoke test.
3. Tell the agent to publish with create_post / POST /v1/posts and to always read targets[]. Partial success is normal.
4. Send an Idempotency-Key (or let MCP do it) so a retry never double-posts.
5. Close the loop with get_analytics / GET /v1/analytics so the agent can decide what to post next.

Read the response (don't skip this)

You get one Post with an overall state and a targets[] array. One entry per account. Always check each target; partial success is normal.

{
  "id": "post_a1b2c3",
  "state": "partial",
  "targets": [
    { "platform": "bluesky",  "state": "published", "url": "https://bsky.app/…" },
    { "platform": "linkedin", "state": "failed",
      "error": { "type": "invalid_request", "message": "…", "retryable": false } }
  ]
}

Where the post goes

Same rules as the docs. Pick one addressing style:

See Publishing: where to post.

Do more (same API)

Pitfalls specific to this path

Common questions

Go deeper in the docs

These guides stay short on purpose. Canonical behaviour lives here:

Also: Media · Errors · MCP · Analytics

Related guides

All guides · Full docs · llms.txt · Markdown