For agents
How an assistant or a script should point itself at Postonus.
Last updated on
If you are an AI assistant or an agent reading this to figure out how to work with Postonus, here is the map.
Read the site as text first
https://postonus.com/llms.txt is a curated index of the site — pricing, features, platform pages, and this documentation tree — meant to be fetched once instead of crawled. Every page it links to also has a plain-markdown copy at <page-url>.md:
https://postonus.com/docs/mcp/tools → the rendered page
https://postonus.com/docs/mcp/tools.md → the same content, as markdownFetching the .md twin is cheaper than parsing rendered HTML and never differs from what a human reader sees, because it is generated from the same source.
Act on a workspace: use MCP
If you are a conversational assistant (Claude, Cursor, ChatGPT) connected to a user's session, use the MCP server:
https://app.postonus.com/api/mcpIt authenticates over OAuth — no key for the user to find and paste — and exposes five tools scoped to their workspace. See MCP and Tools. Every write it makes stages a scheduled post; nothing you do through it publishes immediately.
Running unattended, or need more than five tools: use the API
MCP's tool set covers conversational scheduling. If you need to do more than the five tools allow — read paginated history, manage tags, handle media uploads directly, or run with no user present to complete an OAuth flow — call the HTTP API with an API key instead. It is the same underlying operations, with a wider surface and no conversational framing.
| Situation | Use |
|---|---|
| Conversational assistant, acting for a signed-in user | MCP |
| Unattended script, CI, or a cron job | API with an API key, or the CLI |
| Need an operation outside the public surface | Neither — that operation needs a dashboard session; see Public surface |
Everything here is generated or derived
Nothing in this documentation section is translated, and none of it repeats marketing copy — prose here describes cross-cutting rules (auth, errors, limits) and links to the generated API reference for exact fields. If something you read here disagrees with a live response, the response is correct — file it as a documentation bug, not a product change.