WIP - pricing notes

Author: rainbowFi

src/pages/docs/ai-transport/index.mdx

@@ -134,17 +134,13 @@ Take a look at some example code running in-browser of the sorts of features you
 
 ## Pricing
 
-AI Transport uses Ably's [usage based billing model](/pricing) at your package rates. Your consumption costs will depend on the number of messages inbound (published to Ably) and outbound (delivered to subscribers), and how long channels or connections are active. [Contact Ably](/contact) to discuss options for Enterprise pricing and volume discounts.
+AI Transport uses Ably's [usage based billing model](/docs/platform/pricing) at your package rates. Your consumption costs will depend on the number of messages inbound (published to Ably) and outbound (delivered to subscribers), and how long channels or connections are active. [Contact Ably](https://ably.com/contact) to discuss options for Enterprise pricing and volume discounts.
 
 The cost of streaming token responses over Ably depends on:
 
-- the number of tokens in the LLM responses that you are streaming. For example, a simple support chatbot response is around 300 tokens, a code session chat can be 2000-3000 tokens and a deep reasoning response could be 50000+ tokens.
+- the number of tokens in the LLM responses that you are streaming. For example, a simple support chatbot response is around 300 tokens, a code session chat can be 2,000-3,000 tokens and a deep reasoning response could be over 50,000 tokens.
 - the rate at which your agent publishes tokens to Ably and the number of messages it uses to do so. Some LLMs output every token as a single event, while others batch multiple tokens together. Similarly, your agent may publish tokens as they are received from the LLM or perform its own processing and batching first.
-- the number of subscribers receiving the response
-- the [token streaming pattern](/docs/ai-transport/features/token-streaming#token-streaming-patterns) you choose
+- the number of subscribers receiving the response.
+- the [token streaming pattern](/docs/ai-transport/features/token-streaming#token-streaming-patterns) you choose.
 
-
-- message-per-response Ably will automatically
-
-- message-per-token you are in control, you can turn on server side batching to group messages together in a batching interval. Higher batching interval increases latency but reduces total number of messages, lower batching interval delivers messages quickly.
-[server-side batching](/docs/messages/batch#server-side)
+*** Link to worked example(s) ***

src/pages/docs/platform/pricing/examples/ai-chatbot.mdx

@@ -0,0 +1,23 @@
+---
+title: AI support chatbot
+meta_description: "Calculate AI Transport pricing for conversations with an AI chatbot. Example shows how using the message-per-response pattern and modifying the append rollup window can generate cost savings."
+meta_keywords: "chatbot, support chat, token streaming, token cost, AI Transport pricing, Ably AI Transport pricing, stream cost, Pub/Sub pricing, realtime data delivery, Ably Pub/Sub pricing"
+intro: "This example uses consumption-based pricing for an AI support chatbot use case, where a single agent is publishing tokens to user over AI Transport."
+---
+
+### Assumptions
+
+The scale and features used in this calculation.
+
+### Cost summary
+
+The high level cost breakdown for this scenario. Messages are billed for both inbound (published to Ably) and outbound (delivered to subscribers).
+
+### Effect
+
+
+- message-per-response Ably will automatically
+
+- message-per-token you are in control, you can turn on server side batching to group messages together in a batching interval. Higher batching interval increases latency but reduces total number of messages, lower batching interval delivers messages quickly.
+[server-side batching](/docs/messages/batch#server-side)
+