Publish and schedule reviewed media
Use signed-in Console and supported MCP tools to move generated assets into connected publishing accounts and schedules.
On this page
Generation and publishing are separate operations. A successful media generation produces assets; publishing selects reviewed assets, connected accounts, timing, and post state through the supported Console surface.
Use Console authority
Publishing management is a signed-in Console capability. A trusted agent can use the publishing tools exposed by Console MCP when its delegated user and organization currently have permission.
Public REST API keys are not publishing credentials. Do not send efapi_live_... keys to Console publishing routes or MCP clients.
Start with Accounts and posts to select a publishable account and create or edit a draft. Use Schedules only after the media, account, caption, time, and timezone are explicit.
Review before distribution
Inspect output assets and account selection before scheduling or publishing. Treat rescheduling, cancellation, retries, and failed delivery as explicit lifecycle actions rather than assuming a generation's status controls a post.