For developers
Publishing is the part of a workflow where a mistake is public and permanent. Post Array gives you one backend, typed errors, idempotency on every write and an approval model that an agent cannot talk its way around.
Two commands, machine readable
relay accounts list --jsonrelay media upload ./launch.png --idempotency-key launch-image-1 --json
Five surfaces, one backend
- REST API
- Scoped API keys, an idempotency key required on every write, cursor pagination, and a typed error envelope carrying a stable code, a message key and sanitized details. No provider payload is ever reflected back to you raw.
- Remote MCP server
- Streamable HTTP with OAuth. Tools are granular and each one declares its side effects. Reading, drafting, requesting approval, scheduling and publishing are separate scopes, so a model that can draft cannot publish.
- CLI
- Every command supports machine readable output with a stable shape, so a script can parse it and a continuous integration job can fail on it.
- Signed webhooks
- Publish results, approval decisions, connection health and validation outcomes, signed, replay resistant and redeliverable from the dashboard.
The agent safety model
A scoped API key is not a copy of a browser session. The server reauthorizes every call, records the actor and never trusts an agent host to approve its own action. Dedicated service accounts are not built yet.
Web pages, feeds, comments and platform responses are treated as untrusted data. Model output is revalidated deterministically, because a model saying a post is fine is not a security decision.
Revoke an API key to stop future calls. Pause a social connection to stop new work for that account. A workspace-wide kill switch is not built yet.
What you can rely on
- Every write takes an idempotency key. Replaying a request with the same key returns the original result rather than creating a second post.
- Every error carries a stable code, a message key and sanitized details. Codes do not change meaning between versions.
- Breaking changes get a new version and an announced deprecation window. Additive changes do not.
- Reading, drafting, requesting approval, scheduling and publishing are separate scopes. A credential gets the smallest set that does its job.
Open pieces
The connector contract, the CLI, schema examples, MCP tool definitions and the provider simulator are the parts you need to build against Post Array without a sandbox account. Where a repository is not published yet, this page says so rather than linking to nothing.
Run it on your own accounts
Starting is free, takes no card, and includes your first published posts. Connector availability is shown account by account as each platform completes its review.
Post Array costs $25 a month, or $250 a year, which is two months free. Starting is free and takes no card: connect your accounts, schedule as much as you like, and your first published posts are on us. Connector availability is shown account by account as each platform completes its review.