Canary pending

Publish to X from an API, checked before it ships.

Send prepared posts to the implemented X transport over REST, CLI, or MCP. Customer-ready publishing remains closed until the app, API balance, runtime credentials, and controlled canary are verified.

Start free See preflight

Publish modeControlled rollout

Text limit280 chars

MediaText, image, video

AuthServer-side OAuth

SchedulingRostrumPost queue

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; real delivery unlocks only after the funded app, credentials, and canary gates pass.

Audit every action

Each post, key, and run is recorded and exportable.

How X publishing works

X supports direct publishing through its official API, and RostrumPost has the transport implemented. The customer-ready lane remains closed until the intended app is revalidated, API usage is funded, credentials are loaded, and one controlled post canary returns a remote receipt.

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 cli

$ rostrum post --caption "Launch copy" --platforms x,linkedin
> preflight: 2 transport-ready, customer canary pending
> variants ready: x, linkedin

$ rostrum publish preview <variant_id>
> status: ready
> requires scopes: jobs:write + publish:write
> awaiting human confirmation

X publishing questions

Does RostrumPost use the official X API?

Yes. The official server-side OAuth transport is implemented, but it is not customer-ready until the app, billing, runtime credentials, and controlled canary are verified.

What is the character limit?

X posts are checked against a 280 character limit during preflight, so you see overage before publishing, not after.

Can an agent publish to X?

The agent workflow and scoped authorization exist. Real publishing stays fail-closed until the provider gates and controlled canary pass, and human approval can still be required per job.

Publish with fewer surprises.

Turn prepared content into native variants, preflight every channel, and publish only where the connection allows.

Start free Read the API