• X Direct Messages are now documented: X DMs and comment-to-DM shipped previously but were missing from our docs. The Conversations guide, getting started page, and capability references now cover X alongside Instagram and Facebook, including the dm.read scope and X's webhook setup.
• Meta Direct Messages confirmed to work with your own API keys (BYOK): Several docs pages incorrectly told BYOK customers that Direct Messages required our Managed Keys and that they should contact support instead of building against the feature. This has been corrected across Instagram, Facebook, comment-to-DM, and getting-started docs: Meta DMs work the same way on both Managed Keys and BYOK.
• Messaging windows and limits correctly scoped per network: Reply-window rules (like the 24-hour messaging window) were documented as if they applied to all networks. They're now correctly scoped: Instagram and Facebook have reply windows, while X has none.
• Pricing docs reflect billing for all three messaging networks: /pricing.md previously said Direct Message billing was "currently Instagram" only, even though Facebook and X messaging bill the same way. The page now correctly states that conversation billing applies uniformly across Instagram, Facebook, and X.
• X capability chip on outstand.so no longer shows Direct Messages as unavailable: Our homepage and X landing page were incorrectly showing Direct Messages as struck through / unsupported for X. That's fixed, and the comment-to-DM marketing pages now accurately describe all three supported networks instead of two.
• Corrected media upload endpoint in agent-facing docs: /docs/llms.txt and context7.json referenced a non-existent GET /v1/media/upload-url endpoint. Both now correctly point to POST /v1/media/upload, so AI coding assistants reading these files get a working endpoint.