docs(pricing): fix moderation billing and clarify inbound/outbound message counts

Moderation rule invocations are billed as outbound webhook events, not
inbound messages, so correct the moderation rows in the chat and
consolidated message-counting tables.

Also relabel operations that were described with a bare "message" to use
the inbound/outbound terminology that matches the billing stats users see
(messages.inbound.* / messages.outbound.*). History retrieval, rewind,
presence queries, push delivery, meta events, and LiveObjects sync/fetch
are outbound; LiveObjects batch operations are inbound. Persistence
storage is left unchanged pending confirmation of its stat category.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: umair-ably

src/pages/docs/chat/pricing.mdx

@@ -21,7 +21,7 @@ The following table shows how Chat operations contribute to your message count:
 | Delete message | 1 inbound message |
 | Message deletion delivery | 1 outbound message per subscriber |
 | [History](/docs/chat/rooms/history) ||
-| History retrieval | 1 message per retrieved message |
+| History retrieval | 1 outbound message per retrieved message |
 | [Typing indicators](/docs/chat/rooms/typing) ||
 | Typing keystroke | 1 inbound message; repeats every heartbeat interval (default 10s) |
 | Typing keystroke delivery | 1 outbound message per subscriber per heartbeat |
@@ -42,7 +42,7 @@ The following table shows how Chat operations contribute to your message count:
 | [Occupancy](/docs/chat/rooms/occupancy) ||
 | Occupancy event | 1 outbound message per subscriber (generated on membership changes, debounced up to 15s) |
 | [Moderation](/docs/chat/moderation) ||
-| Moderation action | 1 inbound message; triggers a message update or delete which follows standard delivery |
+| Moderation rule invocation (before or after publish) | 1 outbound webhook event per moderated message |
 
 ## Rooms and channels <a id="channels"/>
 

src/pages/docs/liveobjects/pricing.mdx

@@ -22,9 +22,9 @@ The following table shows how LiveObjects operations contribute to your message
 | LiveCounter increment or decrement | 1 inbound message |
 | LiveCounter create | 2 inbound messages (create + assign) |
 | ObjectMessage delivery | 1 outbound message per connected client |
-| [Synchronization](#synchronization) | 1 message per object synchronized |
-| [REST API](#rest-api) fetch | 1 message per object in response |
-| [Batch](/docs/liveobjects/batch) operation | 1 message per operation in the batch |
+| [Synchronization](#synchronization) | 1 outbound message per object synchronized |
+| [REST API](#rest-api) fetch | 1 outbound message per object in response |
+| [Batch](/docs/liveobjects/batch) operation | 1 inbound message per operation in the batch |
 
 Nested object creation generates additional messages for each nested object.
 

src/pages/docs/platform/pricing/message-counting.mdx

@@ -46,24 +46,24 @@ The following table shows how [Pub/Sub](/docs/pub-sub) operations contribute to
 | Presence leave | 1 inbound message |
 | Presence update | 1 inbound message |
 | Presence event delivery | 1 outbound message per presence subscriber |
-| Presence REST query | 1 message per member returned |
-| Batch presence request | 1 message per member across all queried channels |
+| Presence REST query | 1 outbound message per member returned |
+| Batch presence request | 1 outbound message per member across all queried channels |
 | [Storage and history](/docs/storage-history/storage) ||
 | Persistence storage | 1 additional message per stored message |
-| History retrieval | 1 message per retrieved message |
-| [Rewind](/docs/channels/options/rewind) on attach | 1 message per rewound message (up to 100) |
+| History retrieval | 1 outbound message per retrieved message |
+| [Rewind](/docs/channels/options/rewind) on attach | 1 outbound message per rewound message (up to 100) |
 | [Integrations](/docs/platform/integrations) ||
 | Integration delivery | 1 outbound message per integration target |
 | [Inbound integration publish](/docs/platform/integrations#inbound) | 1 inbound message |
 | [Push notifications](/docs/push) ||
-| Push notification delivery | 1 message per delivered notification |
+| Push notification delivery | 1 outbound message per delivered notification |
 | [Annotations](/docs/messages/annotations) ||
 | Annotation publish | 1 inbound message |
 | Annotation delete | 1 inbound message |
 | [Annotation summary delivery](/docs/messages/annotations#annotation-summaries) | 1 outbound message per subscriber; multiple annotations may be rolled up into a single summary |
 | [Metadata and stats](/docs/metadata-stats/metadata) ||
-| Lifecycle event (`[meta]connection.lifecycle`, `[meta]channel.lifecycle`) | 1 message per event |
-| `[meta]stats:minute` event | 1 message per event |
+| Lifecycle event (`[meta]connection.lifecycle`, `[meta]channel.lifecycle`) | 1 outbound message per event |
+| `[meta]stats:minute` event | 1 outbound message per event |
 | `[meta]log` subscription | Not counted |
 
 For Pub/Sub-specific cost optimization strategies, see [Pub/Sub pricing](/docs/pub-sub/pricing).
@@ -82,7 +82,7 @@ The [Chat SDK](/docs/chat) is built on top of [Pub/Sub](/docs/pub-sub). All Chat
 | Delete message | 1 inbound message |
 | Message deletion delivery | 1 outbound message per subscriber |
 | [History](/docs/chat/rooms/history) ||
-| History retrieval | 1 message per retrieved message |
+| History retrieval | 1 outbound message per retrieved message |
 | [Typing indicators](/docs/chat/rooms/typing) ||
 | Typing keystroke | 1 inbound message; repeats every heartbeat interval (default 10s) |
 | Typing keystroke delivery | 1 outbound message per subscriber per heartbeat |
@@ -103,7 +103,7 @@ The [Chat SDK](/docs/chat) is built on top of [Pub/Sub](/docs/pub-sub). All Chat
 | [Occupancy](/docs/chat/rooms/occupancy) ||
 | Occupancy event | 1 outbound message per subscriber (generated on membership changes, debounced up to 15s) |
 | [Moderation](/docs/chat/moderation) ||
-| Moderation action | 1 inbound message; triggers a message update or delete which follows standard delivery |
+| Moderation rule invocation (before or after publish) | 1 outbound webhook event per moderated message |
 
 For Chat-specific cost optimization strategies, see [Chat pricing](/docs/chat/pricing).
 
@@ -120,9 +120,9 @@ For Chat-specific cost optimization strategies, see [Chat pricing](/docs/chat/pr
 | LiveCounter increment or decrement | 1 inbound message |
 | LiveCounter create | 2 inbound messages (create + assign) |
 | ObjectMessage delivery | 1 outbound message per connected client |
-| [Synchronization](/docs/liveobjects/pricing#synchronization) | 1 message per object synchronized |
-| [REST API](/docs/liveobjects/pricing#rest-api) fetch | 1 message per object in response |
-| [Batch](/docs/liveobjects/batch) operation | 1 message per operation in the batch |
+| [Synchronization](/docs/liveobjects/pricing#synchronization) | 1 outbound message per object synchronized |
+| [REST API](/docs/liveobjects/pricing#rest-api) fetch | 1 outbound message per object in response |
+| [Batch](/docs/liveobjects/batch) operation | 1 inbound message per operation in the batch |
 
 Nested object creation generates additional messages for each nested object.
 

src/pages/docs/pub-sub/pricing.mdx

@@ -21,24 +21,24 @@ The following table shows how Pub/Sub operations contribute to your message coun
 | Presence leave | 1 inbound message |
 | Presence update | 1 inbound message |
 | Presence event delivery | 1 outbound message per presence subscriber |
-| Presence REST query | 1 message per member returned |
-| Batch presence request | 1 message per member across all queried channels |
+| Presence REST query | 1 outbound message per member returned |
+| Batch presence request | 1 outbound message per member across all queried channels |
 | [Storage and history](/docs/storage-history/storage) ||
 | Persistence storage | 1 additional message per stored message |
-| History retrieval | 1 message per retrieved message |
-| [Rewind](/docs/channels/options/rewind) on attach | 1 message per rewound message (up to 100) |
+| History retrieval | 1 outbound message per retrieved message |
+| [Rewind](/docs/channels/options/rewind) on attach | 1 outbound message per rewound message (up to 100) |
 | [Integrations](/docs/platform/integrations) ||
 | Integration delivery | 1 outbound message per integration target |
 | [Inbound integration publish](/docs/platform/integrations#inbound) | 1 inbound message |
 | [Push notifications](/docs/push) ||
-| Push notification delivery | 1 message per delivered notification |
+| Push notification delivery | 1 outbound message per delivered notification |
 | [Annotations](/docs/messages/annotations) ||
 | Annotation publish | 1 inbound message |
 | Annotation delete | 1 inbound message |
 | [Annotation summary delivery](/docs/messages/annotations#annotation-summaries) | 1 outbound message per subscriber; multiple annotations may be rolled up into a single summary |
 | [Metadata and stats](/docs/metadata-stats/metadata) ||
-| Lifecycle event (`[meta]connection.lifecycle`, `[meta]channel.lifecycle`) | 1 message per event |
-| `[meta]stats:minute` event | 1 message per event |
+| Lifecycle event (`[meta]connection.lifecycle`, `[meta]channel.lifecycle`) | 1 outbound message per event |
+| `[meta]stats:minute` event | 1 outbound message per event |
 | `[meta]log` subscription | Not counted |
 
 ## Channels <a id="channels"/>