post-bridgelisted

# Post Bridge API Manage social media posts across connected accounts using the Post Bridge API. Authentication uses the `POST_BRIDGE_API_KEY` environment variable. --- ## Authentication All requests require a Bearer token header. Verify the key is set before making calls: ```bash echo "Key set: ${POST_BRIDGE_API_KEY:+yes}" ``` Use this header on every request: ``` Authorization: Bearer $POST_BRIDGE_API_KEY ``` --- ## Safety Gate for External Side Effects Creating, scheduling, or immediately publishing a post is an external side effect. Default to a dry-run preview or draft unless the user explicitly asks for a live/scheduled post **and** confirms the final payload. Before any non-draft `POST /v1/posts` (including scheduled posts), show a final review that includes: - destination account IDs and platforms - caption text and platform/account overrides - media IDs or `media_urls` - draft vs. scheduled vs. immediate publish state, including `scheduled_at`/`use_queue` - the endpoint and redacted JSON payload to be submitted Then ask for the exact confirmation phrase `POST BRIDGE LIVE CONFIRMED`. Do not send the non-draft create request until the user replies with that phrase. If confirmation is absent or ambiguous, either stop after the preview or create a draft with `"is_draft": true` when the user wants a saved draft. Read-only requests (accounts, analytics, post-results) and media preparation (signed upload URL + file upload) do not require the final confirmation