quiver-cli 1.3.1 → 2.0.0

package/template/.agents/skills/integrations/posthog/references/llm-analytics-manual-capture.md

@@ -1,397 +0,0 @@
-# Manual capture LLM analytics installation - Docs
-
-1.  1
-
-    ## Capture LLM events manually
-
-    If you're using a different server-side SDK or prefer to use the API, you can manually capture the data by calling the `capture` method or using the [capture API](/docs/api/capture.md).
-
-    ## API
-
-    ### Capture via API
-
-    ```bash
-    curl -X POST "https://us.i.posthog.com/i/v0/e/" \
-            -H "Content-Type: application/json" \
-            -d '{
-                "api_key": "<ph_project_token>",
-                "event": "$ai_generation",
-                "properties": {
-                    "distinct_id": "user_123",
-                    "$ai_trace_id": "trace_id_here",
-                    "$ai_model": "gpt-5-mini",
-                    "$ai_provider": "openai",
-                    "$ai_input": [{"role": "user", "content": "Tell me a fun fact about hedgehogs"}],
-                    "$ai_input_tokens": 10,
-                    "$ai_output_choices": [{"role": "assistant", "content": "Hedgehogs have around 5,000 to 7,000 spines on their backs!"}],
-                    "$ai_output_tokens": 20,
-                    "$ai_latency": 1.5,
-                    "$ai_stream": true,
-                    "$ai_time_to_first_token": 0.25
-                }
-            }'
-    ```
-
-    ## Node.js
-
-    ### 1\. Install
-
-    ```bash
-    npm install posthog-node
-    ```
-
-    ### 2\. Initialize PostHog
-
-    ```javascript
-    import { PostHog } from 'posthog-node'
-    const client = new PostHog('<ph_project_token>', {
-        host: 'https://us.i.posthog.com'
-    })
-    ```
-
-    ### 3\. Capture Event
-
-    ```javascript
-    // After your LLM call
-    client.capture({
-        distinctId: 'user_123',
-        event: '$ai_generation',
-        properties: {
-            $ai_trace_id: 'trace_id_here',
-            $ai_model: 'gpt-5-mini',
-            $ai_provider: 'openai',
-            $ai_input: [{ role: 'user', content: 'Tell me a fun fact about hedgehogs' }],
-            $ai_input_tokens: 10,
-            $ai_output_choices: [{ role: 'assistant', content: 'Hedgehogs have around 5,000 to 7,000 spines on their backs!' }],
-            $ai_output_tokens: 20,
-            $ai_latency: 1.5,
-            // For streaming responses, also include:
-            // $ai_stream: true,
-            // $ai_time_to_first_token: 0.25
-        }
-    })
-    client.shutdown()
-    ```
-
-    ## Python
-
-    ### 1\. Install
-
-    ```bash
-    pip install posthog
-    ```
-
-    ### 2\. Initialize PostHog
-
-    ```python
-    from posthog import Posthog
-    posthog = Posthog("<ph_project_token>", host="https://us.i.posthog.com")
-    ```
-
-    ### 3\. Capture Event
-
-    ```python
-    # After your LLM call
-    posthog.capture(
-        distinct_id='user_123',
-        event='$ai_generation',
-        properties={
-            '$ai_trace_id': 'trace_id_here',
-            '$ai_model': 'gpt-5-mini',
-            '$ai_provider': 'openai',
-            '$ai_input': [{'role': 'user', 'content': 'Tell me a fun fact about hedgehogs'}],
-            '$ai_input_tokens': 10,
-            '$ai_output_choices': [{'role': 'assistant', 'content': 'Hedgehogs have around 5,000 to 7,000 spines on their backs!'}],
-            '$ai_output_tokens': 20,
-            '$ai_latency': 1.5,
-            # For streaming responses, also include:
-            # '$ai_stream': True,
-            # '$ai_time_to_first_token': 0.25
-        }
-    )
-    ```
-
-    ## Go
-
-    ### 1\. Install
-
-    ```bash
-    go get github.com/posthog/posthog-go
-    ```
-
-    ### 2\. Initialize PostHog
-
-    ```go
-    import "github.com/posthog/posthog-go"
-    client, _ := posthog.NewWithConfig("<ph_project_token>", posthog.Config{
-        Endpoint: "https://us.i.posthog.com",
-    })
-    defer client.Close()
-    ```
-
-    ### 3\. Capture Event
-
-    ```go
-    // After your LLM call
-    client.Enqueue(posthog.Capture{
-        DistinctId: "user_123",
-        Event:      "$ai_generation",
-        Properties: map[string]interface{}{
-            "$ai_trace_id":        "trace_id_here",
-            "$ai_model":           "gpt-5-mini",
-            "$ai_provider":        "openai",
-            "$ai_input_tokens":    10,
-            "$ai_output_tokens":   20,
-            "$ai_latency":         1.5,
-            // For streaming responses, also include:
-            // "$ai_stream":              true,
-            // "$ai_time_to_first_token": 0.25,
-        },
-    })
-    ```
-
-    ## Ruby
-
-    ### 1\. Install
-
-    ```bash
-    gem install posthog-ruby
-    ```
-
-    ### 2\. Initialize PostHog
-
-    ```ruby
-    require 'posthog-ruby'
-    posthog = PostHog::Client.new({
-        api_key: '<ph_project_token>',
-        host: 'https://us.i.posthog.com'
-    })
-    ```
-
-    ### 3\. Capture Event
-
-    ```ruby
-    # After your LLM call
-    posthog.capture({
-        distinct_id: 'user_123',
-        event: '$ai_generation',
-        properties: {
-        '$ai_trace_id' => 'trace_id_here',
-        '$ai_model' => 'gpt-5-mini',
-        '$ai_provider' => 'openai',
-        '$ai_input_tokens' => 10,
-        '$ai_output_tokens' => 20,
-        '$ai_latency' => 1.5
-        # For streaming responses, also include:
-        # '$ai_stream' => true,
-        # '$ai_time_to_first_token' => 0.25
-        }
-    })
-    ```
-
-    ## PHP
-
-    ### 1\. Install
-
-    ```bash
-    composer require posthog/posthog-php
-    ```
-
-    ### 2\. Initialize PostHog
-
-    ```php
-    <?php
-    require_once __DIR__ . '/vendor/autoload.php';
-    use PostHog\PostHog;
-    PostHog::init('<ph_project_token>', [
-        'host' => 'https://us.i.posthog.com'
-    ]);
-    ```
-
-    ### 3\. Capture Event
-
-    ```php
-    // After your LLM call
-    PostHog::capture([
-        'distinctId' => 'user_123',
-        'event' => '$ai_generation',
-        'properties' => [
-            '$ai_trace_id' => 'trace_id_here',
-            '$ai_model' => 'gpt-5-mini',
-            '$ai_provider' => 'openai',
-            '$ai_input_tokens' => 10,
-            '$ai_output_tokens' => 20,
-            '$ai_latency' => 1.5
-            // For streaming responses, also include:
-            // '$ai_stream' => true,
-            // '$ai_time_to_first_token' => 0.25
-        ]
-    ]);
-    ```
-
-    ### Event Properties
-
-    Each event type has specific properties. See the tabs below for detailed property documentation for each event type.
-
-    ## Generation
-
-    A generation is a single call to an LLM.
-
-    **Event name**: `$ai_generation`
-
-    ### Core properties
-
-    | Property | Description |
-    | --- | --- |
-    | $ai_trace_id | The trace ID (a UUID to group AI events) like conversation_idMust contain only letters, numbers, and special characters: -, _, ~, ., @, (, ), !, ', :, \|Example: d9222e05-8708-41b8-98ea-d4a21849e761 |
-    | $ai_session_id | (Optional) Groups related traces together. Use this to organize traces by whatever grouping makes sense for your application (user sessions, workflows, conversations, or other logical boundaries).Example: session-abc-123, conv-user-456 |
-    | $ai_span_id | (Optional) Unique identifier for this generation |
-    | $ai_span_name | (Optional) Name given to this generationExample: summarize_text |
-    | $ai_parent_id | (Optional) Parent span ID for tree view grouping |
-    | $ai_model | The model usedExample: gpt-5-mini |
-    | $ai_provider | The LLM providerExample: openai, anthropic, gemini |
-    | $ai_input_tokens | The number of tokens in the input (often found in response.usage) |
-    | $ai_output_tokens | The number of tokens in the output (often found in response.usage) |
-    | $ai_latency | (Optional) The latency of the LLM call in seconds |
-    | $ai_time_to_first_token | (Optional) Time to first token in seconds. Only applicable for streaming responses. |
-    | $ai_http_status | (Optional) The HTTP status code of the response |
-    | $ai_base_url | (Optional) The base URL of the LLM providerExample: https://api.openai.com/v1 |
-    | $ai_request_url | (Optional) The full URL of the request made to the LLM APIExample: https://api.openai.com/v1/chat/completions |
-    | $ai_is_error | (Optional) Boolean to indicate if the request was an error |
-    | $ai_error | (Optional) The error message or object |
-
-    ### Cost properties
-
-    Cost properties are optional as we can automatically calculate them from model and token counts. If you want, you can provide your own cost properties or custom pricing instead.
-
-    #### Pre-calculated costs
-
-    | Property | Description |
-    | --- | --- |
-    | $ai_input_cost_usd | (Optional) The cost in USD of the input tokens |
-    | $ai_output_cost_usd | (Optional) The cost in USD of the output tokens |
-    | $ai_request_cost_usd | (Optional) The cost in USD for the requests |
-    | $ai_web_search_cost_usd | (Optional) The cost in USD for the web searches |
-    | $ai_total_cost_usd | (Optional) The total cost in USD (sum of all cost components) |
-
-    #### Custom pricing
-
-    | Property | Description |
-    | --- | --- |
-    | $ai_input_token_price | (Optional) Price per input token (used to calculate $ai_input_cost_usd) |
-    | $ai_output_token_price | (Optional) Price per output token (used to calculate $ai_output_cost_usd) |
-    | $ai_cache_read_token_price | (Optional) Price per cached token read |
-    | $ai_cache_write_token_price | (Optional) Price per cached token write |
-    | $ai_request_price | (Optional) Price per request |
-    | $ai_request_count | (Optional) Number of requests (defaults to 1 if $ai_request_price is set) |
-    | $ai_web_search_price | (Optional) Price per web search |
-    | $ai_web_search_count | (Optional) Number of web searches performed |
-
-    ### Cache properties
-
-    | Property | Description |
-    | --- | --- |
-    | $ai_cache_read_input_tokens | (Optional) Number of tokens read from cache |
-    | $ai_cache_creation_input_tokens | (Optional) Number of tokens written to cache (Anthropic-specific) |
-    | $ai_cache_reporting_exclusive | (Optional) Whether cache tokens are excluded from $ai_input_tokens. When true, cache tokens are separate from input tokens. When false, input tokens already include cache tokens. Defaults to true for Anthropic provider or Claude models, false otherwise. |
-
-    ### Model parameters
-
-    | Property | Description |
-    | --- | --- |
-    | $ai_temperature | (Optional) Temperature parameter used in the LLM request |
-    | $ai_stream | (Optional) Whether the response was streamed |
-    | $ai_max_tokens | (Optional) Maximum tokens setting for the LLM response |
-
-    ## Trace
-
-    A trace is a group that contains multiple spans, generations, and embeddings. Traces can be manually sent as events or appear as pseudo-events automatically created from child events.
-
-    **Event name**: `$ai_trace`
-
-    ### Core properties
-
-    | Property | Description |
-    | --- | --- |
-    | $ai_trace_id | The trace ID (a UUID to group related AI events together)Must contain only letters, numbers, and special characters: -, _, ~, ., @, (, ), !, ', :, \|Example: d9222e05-8708-41b8-98ea-d4a21849e761 |
-    | $ai_session_id | (Optional) Groups related traces together. Use this to organize traces by whatever grouping makes sense for your application (user sessions, workflows, conversations, or other logical boundaries).Example: session-abc-123, conv-user-456 |
-    | $ai_latency | (Optional) The latency of the trace in seconds |
-    | $ai_span_name | (Optional) The name of the traceExample: chat_completion, rag_pipeline |
-    | $ai_is_error | (Optional) Boolean to indicate if the trace encountered an error |
-    | $ai_error | (Optional) The error message or object if the trace failed |
-
-    ### Pseudo-trace Events
-
-    When you send generation (`$ai_generation`), span (`$ai_span`), or embedding (`$ai_embedding`) events with a `$ai_trace_id`, PostHog automatically creates a pseudo-trace event that appears in the dashboard as a parent grouping. These pseudo-traces:
-
-    -   Are not actual events in your data
-    -   Automatically aggregate metrics from child events (latency, tokens, costs)
-    -   Provide a hierarchical view of your AI operations
-    -   Do not require sending an explicit `$ai_trace` event
-
-    This means you can either:
-
-    1.  Send explicit `$ai_trace` events to control the trace metadata
-    2.  Let PostHog automatically create pseudo-traces from your generation/span events
-
-    ## Span
-
-    A span is a single action within your application, such as a function call or vector database search.
-
-    **Event name**: `$ai_span`
-
-    ### Core properties
-
-    | Property | Description |
-    | --- | --- |
-    | $ai_trace_id | The trace ID (a UUID to group related AI events together)Must contain only letters, numbers, and the following characters: -, _, ~, ., @, (, ), !, ', :, \|Example: d9222e05-8708-41b8-98ea-d4a21849e761 |
-    | $ai_session_id | (Optional) Groups related traces together. Use this to organize traces by whatever grouping makes sense for your application (user sessions, workflows, conversations, or other logical boundaries).Example: session-abc-123, conv-user-456 |
-    | $ai_span_id | (Optional) Unique identifier for this spanExample: bdf42359-9364-4db7-8958-c001f28c9255 |
-    | $ai_span_name | (Optional) The name of the spanExample: vector_search, data_retrieval, tool_call |
-    | $ai_parent_id | (Optional) Parent ID for tree view grouping (trace_id or another span_id)Example: 537b7988-0186-494f-a313-77a5a8f7db26 |
-    | $ai_latency | (Optional) The latency of the span in secondsExample: 0.361 |
-    | $ai_is_error | (Optional) Boolean to indicate if the span encountered an error |
-
-    ## Embedding
-
-    An embedding is a single call to an embedding model to convert text into a vector representation.
-
-    **Event name**: `$ai_embedding`
-
-    ### Core properties
-
-    | Property | Description |
-    | --- | --- |
-    | $ai_trace_id | The trace ID (a UUID to group related AI events together). Must contain only letters, numbers, and special characters: -, _, ~, ., @, (, ), !, ', :, \|Example: d9222e05-8708-41b8-98ea-d4a21849e761 |
-    | $ai_session_id | (Optional) Groups related traces together. Use this to organize traces by whatever grouping makes sense for your application (user sessions, workflows, conversations, or other logical boundaries).Example: session-abc-123, conv-user-456 |
-    | $ai_span_id | (Optional) Unique identifier for this embedding operation |
-    | $ai_span_name | (Optional) Name given to this embedding operationExample: embed_user_query, index_document |
-    | $ai_parent_id | (Optional) Parent span ID for tree-view grouping |
-    | $ai_model | The embedding model usedExample: text-embedding-3-small, text-embedding-ada-002 |
-    | $ai_provider | The LLM providerExample: openai, cohere, voyage |
-    | $ai_input | The text to embedExample: "Tell me a fun fact about hedgehogs" or array of strings for batch embeddings |
-    | $ai_input_tokens | The number of tokens in the input |
-    | $ai_latency | (Optional) The latency of the embedding call in seconds |
-    | $ai_http_status | (Optional) The HTTP status code of the response |
-    | $ai_base_url | (Optional) The base URL of the LLM providerExample: https://api.openai.com/v1 |
-    | $ai_request_url | (Optional) The full URL of the request made to the embedding APIExample: https://api.openai.com/v1/embeddings |
-    | $ai_is_error | (Optional) Boolean to indicate if the request was an error |
-    | $ai_error | (Optional) The error message or object if the embedding failed |
-
-    ### Cost properties
-
-    Cost properties are optional as we can automatically calculate them from model and token counts. If you want, you can provide your own cost property instead.
-
-    | Property | Description |
-    | --- | --- |
-    | $ai_input_cost_usd | (Optional) Cost in USD for input tokens |
-    | $ai_output_cost_usd | (Optional) Cost in USD for output tokens (usually 0 for embeddings) |
-    | $ai_total_cost_usd | (Optional) Total cost in USD |
-
-### Community questions
-
-Ask a question
-
-### Was this page useful?
-
-HelpfulCould be better

package/template/.agents/skills/integrations/posthog/references/llm-analytics-traces.md

@@ -1,98 +0,0 @@
-# Traces - Docs
-
-Traces are a collection of [generations](/docs/llm-analytics/generations.md) and [spans](/docs/llm-analytics/spans.md) that capture a full interaction between a user and an LLM. The [traces tab](https://app.posthog.com/llm-analytics/traces) lists them along with the properties autocaptured by PostHog like the person, total cost, total latency, and more.
-
-## Sessions vs Traces
-
--   **Trace** (`$ai_trace_id`): Groups related generations and spans together. Required for all LLM analytics events.
--   **Session** (`$ai_session_id`): Optional property that groups multiple traces together based on your chosen grouping strategy.
-
-See the [Sessions](/docs/llm-analytics/sessions.md) documentation for more details on how to use `$ai_session_id`.
-
-## Trace timeline
-
-Clicking on a trace opens a timeline of the interaction with all the generation and span events. The trace timeline enables you to see the entire conversation, profiling details, and the individual generations and spans.
-
-![LLM traces](https://res.cloudinary.com/dmukukwp6/image/upload/llma_traces_25e203aa50.png)![LLM traces](https://res.cloudinary.com/dmukukwp6/image/upload/llma_traces_dark_dd6ad555dc.png)
-
-A trace presents LLM event data in a timeline, tree-structured view
-
-## Conversation display options
-
-When viewing a trace, you can control how conversation messages are displayed using the display options dropdown. The available options are:
-
--   **Expand all** - Shows the full content of all messages in the conversation
--   **Expand user only** - Expands only user messages, keeping system and assistant messages collapsed for easier scanning of user inputs
--   **Collapse except output and last input** - The default view that shows the model's output and the most recent user input, keeping earlier messages collapsed
-
-## Tool calls
-
-Traces display any [tools](/docs/llm-analytics/tools.md) called by the generations within them, shown as tags in the traces list. This makes it easy to see which conversations involved tool use at a glance.
-
-## Sentiment classification
-
-PostHog can classify the sentiment of user messages in a trace as negative, neutral, or positive. Sentiment is computed on-demand using a local model when you view a trace — no data is sent to third-party services. Each trace gets an overall sentiment label and score, with a per-generation and per-message breakdown. See [Sentiment classification](/docs/llm-analytics/sentiment.md) for more details.
-
-## Search traces with PostHog AI
-
-[PostHog AI](/docs/posthog-ai.md) can search and analyze your LLM traces using natural language. When you're on an [LLM Analytics page](https://app.posthog.com/llm-analytics), PostHog AI automatically switches to its LLM analytics mode, giving it access to tools for searching traces by date range, model, cost, error status, and other properties.
-
-Example prompts you can try:
-
--   "Show me recent LLM traces from the past week"
--   "What are the most expensive LLM calls from today?"
--   "Find traces with errors in the last 30 days"
--   "What's happening in my most expensive trace?"
-
-PostHog AI returns trace details including name, latency, cost, token counts, and error count. It can also read individual traces to provide a detailed summary of what happened.
-
-## AI event hierarchy
-
-flowchart TD S\["<strong>$ai\_session\_id</strong><br/>(optional)"\] A\[<strong>$ai\_trace</strong>\] A2\[<strong>$ai\_trace</strong>\] B\[<strong>$ai\_generation</strong>\] C@{ shape: processes, label: "<strong>$ai\_spans</strong>" } D\[<strong>$ai\_generation</strong>\] E@{ shape: processes, label: "<strong>$ai\_spans</strong>" } F\[<strong>$ai\_generation</strong>\] S -.-> A S -.-> A2 A --> B A --> C C --> D C --> E E --> F
-
-Traces consist of the following event hierarchy:
-
-1.  (Optional) A session (`$ai_session_id`) can group multiple traces together.
-2.  A trace (`$ai_trace_id`) is the top-level required grouping for LLM events.
-3.  A trace can contain multiple spans and generations.
-4.  A span can be the parent of other spans.
-5.  A generation can be the child of a span or trace.
-
-## Event properties
-
-A trace is a group that contains multiple spans, generations, and embeddings. Traces can be manually sent as events or appear as pseudo-events automatically created from child events.
-
-**Event name**: `$ai_trace`
-
-### Core properties
-
-| Property | Description |
-| --- | --- |
-| $ai_trace_id | The trace ID (a UUID to group related AI events together)Must contain only letters, numbers, and special characters: -, _, ~, ., @, (, ), !, ', :, \|Example: d9222e05-8708-41b8-98ea-d4a21849e761 |
-| $ai_session_id | (Optional) Groups related traces together. Use this to organize traces by whatever grouping makes sense for your application (user sessions, workflows, conversations, or other logical boundaries).Example: session-abc-123, conv-user-456 |
-| $ai_latency | (Optional) The latency of the trace in seconds |
-| $ai_span_name | (Optional) The name of the traceExample: chat_completion, rag_pipeline |
-| $ai_is_error | (Optional) Boolean to indicate if the trace encountered an error |
-| $ai_error | (Optional) The error message or object if the trace failed |
-
-### Pseudo-trace Events
-
-When you send generation (`$ai_generation`), span (`$ai_span`), or embedding (`$ai_embedding`) events with a `$ai_trace_id`, PostHog automatically creates a pseudo-trace event that appears in the dashboard as a parent grouping. These pseudo-traces:
-
--   Are not actual events in your data
--   Automatically aggregate metrics from child events (latency, tokens, costs)
--   Provide a hierarchical view of your AI operations
--   Do not require sending an explicit `$ai_trace` event
-
-This means you can either:
-
-1.  Send explicit `$ai_trace` events to control the trace metadata
-2.  Let PostHog automatically create pseudo-traces from your generation/span events
-
-### Community questions
-
-Ask a question
-
-### Was this page useful?
-
-HelpfulCould be better

package/template/.agents/skills/integrations/posthog/references/llm-analytics-vercel-ai.md

@@ -1,120 +0,0 @@
-# Vercel AI SDK LLM analytics installation - Docs
-
-1.  1
-
-    ## Install dependencies
-
-    Required
-
-    Install the PostHog AI package, the Vercel AI SDK, and the OpenTelemetry SDK.
-
-    ```bash
-    npm install @posthog/ai @ai-sdk/openai ai @opentelemetry/sdk-node @opentelemetry/resources
-    ```
-
-    **No proxy**
-
-    These SDKs **do not** proxy your calls. They only send analytics data to PostHog in the background.
-
-2.  2
-
-    ## Set up the OpenTelemetry exporter
-
-    Required
-
-    Initialize the OpenTelemetry SDK with PostHog's `PostHogTraceExporter`. This sends `gen_ai.*` spans directly to PostHog's OTLP ingestion endpoint. PostHog converts these into `$ai_generation` events automatically.
-
-    ```typescript
-    import { NodeSDK } from '@opentelemetry/sdk-node'
-    import { resourceFromAttributes } from '@opentelemetry/resources'
-    import { PostHogTraceExporter } from '@posthog/ai/otel'
-    const sdk = new NodeSDK({
-      resource: resourceFromAttributes({
-        'service.name': 'my-ai-app',
-      }),
-      traceExporter: new PostHogTraceExporter({
-        apiKey: '<ph_project_token>',
-        host: 'https://us.i.posthog.com',
-      }),
-    })
-    sdk.start()
-    ```
-
-3.  3
-
-    ## Call Vercel AI with telemetry enabled
-
-    Required
-
-    Pass `experimental_telemetry` to your Vercel AI SDK calls. The `posthog_distinct_id` metadata field links events to a specific user in PostHog.
-
-    ```typescript
-    import { generateText } from 'ai'
-    import { openai } from '@ai-sdk/openai'
-    const result = await generateText({
-      model: openai('gpt-5-mini'),
-      prompt: 'Tell me a fun fact about hedgehogs.',
-      experimental_telemetry: {
-        isEnabled: true,
-        functionId: 'my-ai-function',
-        metadata: {
-          posthog_distinct_id: 'user_123', // optional
-        },
-      },
-    })
-    console.log(result.text)
-    await sdk.shutdown()
-    ```
-
-    > **Note:** If you want to capture LLM events anonymously, omit the `posthog_distinct_id` metadata field. See our docs on [anonymous vs identified events](/docs/data/anonymous-vs-identified-events.md) to learn more.
-
-    You can expect captured `$ai_generation` events to have the following properties:
-
-    | Property | Description |
-    | --- | --- |
-    | $ai_model | The specific model, like gpt-5-mini or claude-4-sonnet |
-    | $ai_latency | The latency of the LLM call in seconds |
-    | $ai_time_to_first_token | Time to first token in seconds (streaming only) |
-    | $ai_tools | Tools and functions available to the LLM |
-    | $ai_input | List of messages sent to the LLM |
-    | $ai_input_tokens | The number of tokens in the input (often found in response.usage) |
-    | $ai_output_choices | List of response choices from the LLM |
-    | $ai_output_tokens | The number of tokens in the output (often found in response.usage) |
-    | $ai_total_cost_usd | The total cost in USD (input + output) |
-    | [[...]](/docs/llm-analytics/generations.md#event-properties) | See [full list](/docs/llm-analytics/generations.md#event-properties) of properties |
-
-4.  ## Verify traces and generations
-
-    Recommended
-
-    *Confirm LLM events are being sent to PostHog*
-
-    Let's make sure LLM events are being captured and sent to PostHog. Under **LLM analytics**, you should see rows of data appear in the **Traces** and **Generations** tabs.
-
-    ![LLM generations in PostHog](https://res.cloudinary.com/dmukukwp6/image/upload/SCR_20250807_syne_ecd0801880.png)![LLM generations in PostHog](https://res.cloudinary.com/dmukukwp6/image/upload/SCR_20250807_syjm_5baab36590.png)
-
-    [Check for LLM events in PostHog](https://app.posthog.com/llm-analytics/generations)
-
-5.  4
-
-    ## Next steps
-
-    Recommended
-
-    Now that you're capturing AI conversations, continue with the resources below to learn what else LLM Analytics enables within the PostHog platform.
-
-    | Resource | Description |
-    | --- | --- |
-    | [Basics](/docs/llm-analytics/basics.md) | Learn the basics of how LLM calls become events in PostHog. |
-    | [Generations](/docs/llm-analytics/generations.md) | Read about the $ai_generation event and its properties. |
-    | [Traces](/docs/llm-analytics/traces.md) | Explore the trace hierarchy and how to use it to debug LLM calls. |
-    | [Spans](/docs/llm-analytics/spans.md) | Review spans and their role in representing individual operations. |
-    | [Anaylze LLM performance](/docs/llm-analytics/dashboard.md) | Learn how to create dashboards to analyze LLM performance. |
-
-### Community questions
-
-Ask a question
-
-### Was this page useful?
-
-HelpfulCould be better