diff --git a/changelog.mdx b/changelog.mdx
index c1db3554d..21aceb6a3 100644
--- a/changelog.mdx
+++ b/changelog.mdx
@@ -7,6 +7,32 @@ keywords: ["changelog", "API updates", "release notes", "what's new", "API chang
 
 To subscribe to updates, please [**“Turn on notifications”**](https://help.x.com/en/managing-your-account/notifications-on-mobile-devices#:~:text=In%20the%20top%20menu,%20you,you%20would%20like%20to%20receive) for [**@API**](https://x.com/api). You can also follow this changelog in your feed reader via the [**RSS feed**](https://docs.x.com/changelog/rss.xml).
 
+<Update label="Aug 25, 2026" description="X API v2">
+  ### This week: credit balance endpoint, broadcast events, and more
+
+  #### New features
+
+  **Check your Pay-per-use credit balance**
+
+  We added [`GET /2/usage/credits`](/x-api/usage/get-usage-credits), a new endpoint in the [Usage section](/x-api/usage/introduction) that returns your Pay-per-use (PPU) credit balance in USD. You can now monitor your remaining credits programmatically and top up before you run out. It supports both app-only and user-context (OAuth 2.0) authentication.
+
+  **Broadcast start and end events for X Activity API**
+
+  We added `broadcast.start` and `broadcast.end` events to the [X Activity API](/x-api/activity/introduction). Subscribe by User ID to receive real-time notifications when a user starts or ends a live broadcast. Both are public events, so you can subscribe with either app-only or user-context authentication. See the [event payloads reference](/x-api/activity/event-payloads) for sample payloads.
+
+  #### Updates
+
+  **Pay-per-use monthly Post cap raised to 3 million**
+
+  We raised the monthly [Post cap](/x-api/fundamentals/post-cap) on Pay-per-use plans from 2 million to 3 million Post reads per billing cycle. If you need higher volume, consider an [Enterprise plan](/forms/enterprise-api-interest).
+
+  #### Bug fixes
+
+  **Trends by WOEID reference corrected**
+
+  `GET /2/trends/by/woeid/{woeid}` returns `trend_name` only; it does not return `tweet_count`, even when requested via `trend.fields`. We removed `tweet_count` from the [endpoint reference](/x-api/trends/trends-by-woeid/introduction) to match actual behavior. `GET /2/users/personalized_trends` is unaffected and still returns `tweet_count`.
+</Update>
+
 <Update label="Aug 13, 2026" description="X Ads API">
   ### Updated `video_total_views` definition