Skip to main content
You do not start by firing requests. You start by standing up the Connect account your product (or your agent) will use.
1

Create a Connect account

Sign up at connect.trypost.it/register. One account per customer — no workspaces, no extra tenants.The dashboard is for your team: accounts, keys, billing, logs, playground. It is not the UI you ship to your users.
2

Connect at least one social network

Nothing publishes until an identity exists. Open Accounts and connect the networks you need.When you ship a product, your users connect in their browser. Connect hosts OAuth and the pickers (including Bluesky, Mastodon, and Telegram). Your backend only starts the flow and receives them back. There is no MCP connect tool.How the browser flow works: Connect accounts.Two non-X identities are free. X always counts. A third non-X account, or any X account, needs a card.
3

Get credentials

REST — create a key under API keys. The plain token is shown once. Keep it on a server.Agents — add https://connect.trypost.it/mcp and sign in with OAuth (mcp:use). An API key on /mcp returns 403.Details: Authentication. Client setup: MCP.

What you can do

Same account, three callers: your backend (REST), an agent (MCP), and your team (dashboard).

Publish

One post, many networks. Shared caption and media, optional per-network overrides. Draft, schedule, or publish now.

Upload media

Presign a PUT, send the file, then attach that public_url. External URLs are rejected. There is no asset library.

Group identities

Optional sets — a brand, a client, a campaign. Not a second workspace.

Listen for outcomes

Signed POSTs when a post publishes or fails, or when a social account connects or disconnects.
Try the live API from the playground once you have a key. When you need the exact path, body, or response, open the API reference — this page does not repeat those requests.