• Disclose AI-generated content on YouTube uploads: You can now set containsSyntheticMedia on the youtube post configuration to comply with YouTube's altered/synthetic content disclosure requirement. Set it to true or false to make an explicit declaration, or omit it entirely if you don't need to disclose anything. This applies to new uploads; videos already published need to be updated directly in YouTube Studio.
• Fixed broken accounts examples across the docs and website: Every code sample that showed "accounts": ["facebook"] or similar network names has been replaced with working examples. Those samples would return a 400 error or a silent partial publish if copied as-is, since accounts must be referenced by account ID or username, never by network name. Fixes cover the getting-started guide, per-network configuration pages, comparison and idempotency examples, and the MCP tool reference.
• Corrected guidance on which networks need your own developer app: Documentation for Facebook, Instagram, LinkedIn, Pinterest, Threads, TikTok, and YouTube now leads with the fact that these are covered by our managed keys, so most integrations don't need to register a developer app at all. Bring-your-own-key is now clearly presented as an optional white-labelling path rather than a requirement. Missing disclosure callouts were also added for networks that do require your own keys (Google Business Profile, X).
• Fixed dead links in the network configuration docs: Several links to the configurations index and to individual network pages (including Bluesky and Pinterest, which were missing from the index entirely) were pointing to the wrong path and returning a 404. All configuration pages are now reachable from the index.