Publish to X from an API, checked before it ships.
Send prepared posts to X over a REST API or CLI. RostrumPost builds the native variant, runs preflight, and publishes directly once X is connected.
What you get for X
Preflight before publish
Length, media, and duplicate checks run before a post reaches the queue.
API, CLI, and MCP
Drive X publishing from your stack with one scoped authorization model.
Schedule or publish now
Queue posts for later or publish directly when the connection allows.
Audit every action
Each post, key, and run is recorded and exportable.
How X publishing works
X allows direct publishing through its API once an account is connected. RostrumPost keeps that explicit: a post is built as a native X variant, checked against the 280 character limit and media rules, and only then queued or published.
If a post would exceed a limit or is missing required media, preflight flags it as an action instead of letting it fail after the fact.
Drive it from the CLI
The same authorization model covers the API, CLI, MCP server, and agent Skill.
$ rostrum post --caption "Launch copy" --platforms x,linkedin
> preflight: 2 direct, 0 blocking
> variants ready: x, linkedin
$ rostrum publish preview <variant_id>
> status: ready
> requires scopes: jobs:write + publish:write
> awaiting human confirmationX publishing questions
Does RostrumPost use the official X API?
What is the character limit?
Can an agent publish to X?
Publish with fewer surprises.
Turn prepared content into native variants, preflight every channel, and publish only where the connection allows.