OpenPMM enters limited access
OpenPMM gives coding agents one publishing path for your own social accounts. You connect each account once. Your agent then prepares, schedules, and publishes Posts through the public API or CLI.
The initial release keeps the product focused. It does not try to replace a social media dashboard. It gives your agent a clear contract for the part that must happen after content is ready.
Publish from the workflow you already use
The public API and CLI support the same core workflow:
- Create an account and Workspace.
- Connect a social account as a Destination.
- Upload and validate media Assets.
- Create a draft Post.
- Publish the Post now or schedule it for later.
- Check the Post state and publication result.
- Retry or reschedule a Post when the workflow needs a change.
The API also supports account access, Workspace management, team invitations, product feedback, signed webhooks, and Slack notifications.
One publishing path across nine channels
The initial release supports:
- Bluesky
- Mastodon
- Threads
- TikTok
- X
- YouTube
OpenPMM checks media against the selected Destination rules before publishing. It keeps provider-specific connection state behind the Destination contract, so your agent does not need a separate publishing integration for every channel.
Keep public publishing explicit
OpenPMM treats publishing as an external side effect. A request that publishes or schedules a Post must include explicit confirmation. OAuth also stays in a browser flow that the account owner completes.
This boundary lets an agent prepare the work without hiding the action that reaches a public account. Your workflow can review the Destination, content, media, and timing before the Post leaves OpenPMM.
Use the CLI from a terminal or coding agent
The first-party CLI uses the public API. You can run it from a terminal, script, or coding-agent workflow. It supports stable output, explicit confirmations, request identifiers, retries, and the same Post states as the API.
The documentation includes read-only quickstart steps, authentication, draft and publishing workflows, media handling, scheduling, retry behavior, and signed webhook events.
Read the documentation
The public documentation now includes:
- Guides for accounts, Workspaces, Destinations, Posts, Assets, and media limits.
- CLI workflows for authentication, publishing, automation, feedback, and webhooks.
- API reference pages generated from the production OpenAPI document.
- Destination-specific media guidance for all supported channels.
Start with the API quickstart, then read Posts and publishing before you create public content.
A focused first release
OpenPMM starts with setup, connections, media, publishing, scheduling, and reliable state. It does not include a social inbox, listening tools, analytics suite, or customer-facing white-label API.
That narrow scope is intentional. The product gives your agent one dependable way to publish to your own accounts, while the content planning and brand workflows remain in the agent tools you already use.