mixpeek 0.81.1

package/dist/api/taxonomy-analytics-api.d.ts

@@ -0,0 +1,514 @@
+/**
+ * Mixpeek API
+ * This is the Mixpeek API, providing access to various endpoints for data processing and retrieval.
+ *
+ * The version of the OpenAPI document: 0.81.1
+ * Contact: info@mixpeek.com
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import type { Configuration } from '../configuration';
+import type { AxiosPromise, AxiosInstance, RawAxiosRequestConfig } from 'axios';
+import { type RequestArgs, BaseAPI } from '../base';
+import type { AvailableStepsResponse } from '../models';
+import type { PathAnalysisRequest } from '../models';
+import type { PathAnalysisResponse } from '../models';
+import type { StepTransitionRequest } from '../models';
+import type { StepTransitionResponse } from '../models';
+/**
+ * TaxonomyAnalyticsApi - axios parameter creator
+ * @export
+ */
+export declare const TaxonomyAnalyticsApiAxiosParamCreator: (configuration?: Configuration) => {
+    /**
+     * Discover the most common multi-step paths documents take between two taxonomy steps.  Unlike the `/transitions` endpoint which only analyzes direct A→B transitions, this endpoint reveals the intermediate steps documents actually take.  ## Use Cases  **Email Thread Analysis:** - Question: What paths do emails take from \"inquiry\" to \"closed_won\"? - Discover: Some go inquiry → followup → proposal → closed_won - Discover: Others skip steps: inquiry → proposal → closed_won - Discover: Fast track: inquiry → closed_won  **Content Editorial Paths:** - Question: Common paths from \"draft\" to \"published\"? - Discover: draft → review → edit → review → published - Discover: draft → review → published (expedited) - Discover: Paths that loop back (draft → review → draft → review)  **Compliance Resolution Paths:** - Question: How do violations get resolved? - Discover: violation → investigated → remediated → resolved - Discover: violation → false_positive → closed - Discover: Escalation paths: violation → escalated → legal_review → resolved  ## Requirements  - Taxonomy must have `step_analytics` configured - Collection must contain documents with timestamp and sequence_id fields  ## Returns  **Completion Metrics:** - `total_sequences`: Sequences starting at from_step - `completed_sequences`: Number reaching to_step - `completion_rate`: Percentage that completed  **Paths (sorted by frequency):** - `path`: Ordered sequence of steps - `count`: Number of sequences following this path - `percentage`: Percentage of completing sequences - `avg_duration_sec`: Average time for this path  ## Example Request  ```json {     \"collection_id\": \"col_emails\",     \"taxonomy_id\": \"tax_sales_stages\",     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"max_path_length\": 10,     \"min_support\": 5 } ```  ## Example Response  ```json {     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"total_sequences\": 1000,     \"completed_sequences\": 350,     \"completion_rate\": 0.35,     \"paths\": [         {             \"path\": [\"inquiry\", \"followup\", \"proposal\", \"closed_won\"],             \"count\": 120,             \"percentage\": 34.3,             \"avg_duration_sec\": 604800.0         },         {             \"path\": [\"inquiry\", \"proposal\", \"closed_won\"],             \"count\": 90,             \"percentage\": 25.7,             \"avg_duration_sec\": 432000.0         },         {             \"path\": [\"inquiry\", \"closed_won\"],             \"count\": 70,             \"percentage\": 20.0,             \"avg_duration_sec\": 172800.0         }     ] } ```  ## Path Interpretation  **Length Analysis:** - Shorter paths indicate efficient progression - Longer paths may indicate complexity or bottlenecks - Loops (repeated steps) indicate rework or revisions  **Duration Analysis:** - Compare avg_duration_sec across paths - Shorter paths may not always be faster - Identify optimization opportunities  **Frequency Analysis:** - High-percentage paths are \"happy paths\" - Low-percentage paths may be edge cases or exceptions - Missing expected paths indicate drop-off points
+     * @summary Analyze multi-step transition paths
+     * @param {string} taxonomyId
+     * @param {PathAnalysisRequest} pathAnalysisRequest
+     * @param {string} [authorization] REQUIRED: Bearer token authentication using your API key. Format: \'Bearer sk_xxxxxxxxxxxxx\'. You can create API keys in the Mixpeek dashboard under Organization Settings.
+     * @param {string} [authorization2]
+     * @param {string} [xNamespace] REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like \'my-namespace\'
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    analyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics: (taxonomyId: string, pathAnalysisRequest: PathAnalysisRequest, authorization?: string, authorization2?: string, xNamespace?: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Discover the most common multi-step paths documents take between two taxonomy steps.  Unlike the `/transitions` endpoint which only analyzes direct A→B transitions, this endpoint reveals the intermediate steps documents actually take.  ## Use Cases  **Email Thread Analysis:** - Question: What paths do emails take from \"inquiry\" to \"closed_won\"? - Discover: Some go inquiry → followup → proposal → closed_won - Discover: Others skip steps: inquiry → proposal → closed_won - Discover: Fast track: inquiry → closed_won  **Content Editorial Paths:** - Question: Common paths from \"draft\" to \"published\"? - Discover: draft → review → edit → review → published - Discover: draft → review → published (expedited) - Discover: Paths that loop back (draft → review → draft → review)  **Compliance Resolution Paths:** - Question: How do violations get resolved? - Discover: violation → investigated → remediated → resolved - Discover: violation → false_positive → closed - Discover: Escalation paths: violation → escalated → legal_review → resolved  ## Requirements  - Taxonomy must have `step_analytics` configured - Collection must contain documents with timestamp and sequence_id fields  ## Returns  **Completion Metrics:** - `total_sequences`: Sequences starting at from_step - `completed_sequences`: Number reaching to_step - `completion_rate`: Percentage that completed  **Paths (sorted by frequency):** - `path`: Ordered sequence of steps - `count`: Number of sequences following this path - `percentage`: Percentage of completing sequences - `avg_duration_sec`: Average time for this path  ## Example Request  ```json {     \"collection_id\": \"col_emails\",     \"taxonomy_id\": \"tax_sales_stages\",     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"max_path_length\": 10,     \"min_support\": 5 } ```  ## Example Response  ```json {     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"total_sequences\": 1000,     \"completed_sequences\": 350,     \"completion_rate\": 0.35,     \"paths\": [         {             \"path\": [\"inquiry\", \"followup\", \"proposal\", \"closed_won\"],             \"count\": 120,             \"percentage\": 34.3,             \"avg_duration_sec\": 604800.0         },         {             \"path\": [\"inquiry\", \"proposal\", \"closed_won\"],             \"count\": 90,             \"percentage\": 25.7,             \"avg_duration_sec\": 432000.0         },         {             \"path\": [\"inquiry\", \"closed_won\"],             \"count\": 70,             \"percentage\": 20.0,             \"avg_duration_sec\": 172800.0         }     ] } ```  ## Path Interpretation  **Length Analysis:** - Shorter paths indicate efficient progression - Longer paths may indicate complexity or bottlenecks - Loops (repeated steps) indicate rework or revisions  **Duration Analysis:** - Compare avg_duration_sec across paths - Shorter paths may not always be faster - Identify optimization opportunities  **Frequency Analysis:** - High-percentage paths are \"happy paths\" - Low-percentage paths may be edge cases or exceptions - Missing expected paths indicate drop-off points
+     * @summary Analyze multi-step transition paths
+     * @param {string} taxonomyId
+     * @param {PathAnalysisRequest} pathAnalysisRequest
+     * @param {string} [authorization] REQUIRED: Bearer token authentication using your API key. Format: \&#39;Bearer sk_xxxxxxxxxxxxx\&#39;. You can create API keys in the Mixpeek dashboard under Organization Settings.
+     * @param {string} [authorization2]
+     * @param {string} [xNamespace] REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like \&#39;my-namespace\&#39;
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    analyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics_1: (taxonomyId: string, pathAnalysisRequest: PathAnalysisRequest, authorization?: string, authorization2?: string, xNamespace?: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Analyze how documents progress from one taxonomy step to another.  This endpoint computes conversion rates, duration statistics, and predictor lifts for documents transitioning between taxonomy labels.  ## Use Cases  **Email Thread Analysis:** - Question: How long from \"inquiry\" to \"closed_won\"? - Question: What % of inquiries result in sales? - Question: Which sender domains have highest conversion?  **Content Workflow Tracking:** - Question: Conversion rate from \"draft\" to \"published\"? - Question: How long does content stay in review? - Question: Which authors publish fastest?  **Safety Compliance Monitoring:** - Question: Time from violation detection to resolution? - Question: Success rate for remediation efforts?  ## Requirements  - Taxonomy must have `step_analytics` configured (or provide `override_step_analytics`) - Collection must contain documents enriched with this taxonomy - Documents must have timestamp and sequence grouping fields configured  ## Returns  **Conversion Metrics:** - `count`: Total sequences starting at from_step - `converted`: Number reaching to_step - `conversion_rate`: Percentage that converted  **Duration Statistics (if converted > 0):** - `mean`, `median`: Average and middle duration - `p90`, `p95`: 90th and 95th percentile durations - `std_dev`, `min`, `max`: Distribution statistics  **Top Predictors:** - Covariates with highest impact on conversion - Lift values (>1.0 = increases conversion, <1.0 = decreases) - Statistical significance via minimum support threshold  ## Example Request  ```json {     \"collection_id\": \"col_emails\",     \"taxonomy_id\": \"tax_sales_stages\",     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"max_window_days\": 90,     \"min_support\": 10 } ```  ## Example Response  ```json {     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"count\": 1000,     \"converted\": 350,     \"conversion_rate\": 0.35,     \"durations_sec\": {         \"mean\": 432000.0,         \"median\": 345600.0,         \"p50\": 345600.0,         \"p90\": 691200.0,         \"p95\": 864000.0     },     \"top_predictors\": [         {             \"field\": \"Sender Domain\",             \"value\": \"enterprise.com\",             \"count\": 150,             \"conversion_rate\": 0.75,             \"lift\": 2.14         }     ] } ```
+     * @summary Compute step transition analytics
+     * @param {string} taxonomyId
+     * @param {StepTransitionRequest} stepTransitionRequest
+     * @param {string} [authorization] REQUIRED: Bearer token authentication using your API key. Format: \&#39;Bearer sk_xxxxxxxxxxxxx\&#39;. You can create API keys in the Mixpeek dashboard under Organization Settings.
+     * @param {string} [authorization2]
+     * @param {string} [xNamespace] REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like \&#39;my-namespace\&#39;
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    computeStepTransitionsTaxonomiesTaxonomyIdAnalytics: (taxonomyId: string, stepTransitionRequest: StepTransitionRequest, authorization?: string, authorization2?: string, xNamespace?: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Analyze how documents progress from one taxonomy step to another.  This endpoint computes conversion rates, duration statistics, and predictor lifts for documents transitioning between taxonomy labels.  ## Use Cases  **Email Thread Analysis:** - Question: How long from \"inquiry\" to \"closed_won\"? - Question: What % of inquiries result in sales? - Question: Which sender domains have highest conversion?  **Content Workflow Tracking:** - Question: Conversion rate from \"draft\" to \"published\"? - Question: How long does content stay in review? - Question: Which authors publish fastest?  **Safety Compliance Monitoring:** - Question: Time from violation detection to resolution? - Question: Success rate for remediation efforts?  ## Requirements  - Taxonomy must have `step_analytics` configured (or provide `override_step_analytics`) - Collection must contain documents enriched with this taxonomy - Documents must have timestamp and sequence grouping fields configured  ## Returns  **Conversion Metrics:** - `count`: Total sequences starting at from_step - `converted`: Number reaching to_step - `conversion_rate`: Percentage that converted  **Duration Statistics (if converted > 0):** - `mean`, `median`: Average and middle duration - `p90`, `p95`: 90th and 95th percentile durations - `std_dev`, `min`, `max`: Distribution statistics  **Top Predictors:** - Covariates with highest impact on conversion - Lift values (>1.0 = increases conversion, <1.0 = decreases) - Statistical significance via minimum support threshold  ## Example Request  ```json {     \"collection_id\": \"col_emails\",     \"taxonomy_id\": \"tax_sales_stages\",     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"max_window_days\": 90,     \"min_support\": 10 } ```  ## Example Response  ```json {     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"count\": 1000,     \"converted\": 350,     \"conversion_rate\": 0.35,     \"durations_sec\": {         \"mean\": 432000.0,         \"median\": 345600.0,         \"p50\": 345600.0,         \"p90\": 691200.0,         \"p95\": 864000.0     },     \"top_predictors\": [         {             \"field\": \"Sender Domain\",             \"value\": \"enterprise.com\",             \"count\": 150,             \"conversion_rate\": 0.75,             \"lift\": 2.14         }     ] } ```
+     * @summary Compute step transition analytics
+     * @param {string} taxonomyId
+     * @param {StepTransitionRequest} stepTransitionRequest
+     * @param {string} [authorization] REQUIRED: Bearer token authentication using your API key. Format: \&#39;Bearer sk_xxxxxxxxxxxxx\&#39;. You can create API keys in the Mixpeek dashboard under Organization Settings.
+     * @param {string} [authorization2]
+     * @param {string} [xNamespace] REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like \&#39;my-namespace\&#39;
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    computeStepTransitionsTaxonomiesTaxonomyIdAnalytics_2: (taxonomyId: string, stepTransitionRequest: StepTransitionRequest, authorization?: string, authorization2?: string, xNamespace?: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Get all available steps for a taxonomy and collection.  This endpoint discovers what steps exist in your analytics data by querying the ClickHouse taxonomy_events table. Use this before querying transitions or paths to understand what step values you can use.  **Use Cases:** - Discover available steps before querying analytics - Validate step names (avoid typos in from_step/to_step) - See which steps have the most events - Check data freshness (first_seen/last_seen timestamps)  **Example Usage:** ```python # 1. Get available steps GET /v1/taxonomies/tax_sales/analytics/available-steps?collection_id=col_emails  # Response: {     \"taxonomy_id\": \"tax_sales\",     \"collection_id\": \"col_emails\",     \"total_events\": 5432,     \"total_sequences\": 1000,     \"steps\": [         {\"step_key\": \"inquiry\", \"event_count\": 1000, ...},         {\"step_key\": \"followup\", \"event_count\": 450, ...},         {\"step_key\": \"closed_won\", \"event_count\": 350, ...}     ] }  # 2. Use discovered steps in transition query POST /v1/taxonomies/tax_sales/analytics/transitions {     \"collection_id\": \"col_emails\",     \"from_step\": \"inquiry\",      # From available steps     \"to_step\": \"closed_won\"      # From available steps } ```  Args:     request: FastAPI request object (contains tenant context)     taxonomy_id: Taxonomy ID to query     collection_id: Collection ID for filtering events  Returns:     AvailableStepsResponse with all steps sorted by event count (descending)  Raises:     NotFoundError: If taxonomy not found     ValidationError: If unable to query ClickHouse
+     * @summary Get Available Steps
+     * @param {string} taxonomyId
+     * @param {string} collectionId Collection ID to analyze
+     * @param {string} [authorization] REQUIRED: Bearer token authentication using your API key. Format: \&#39;Bearer sk_xxxxxxxxxxxxx\&#39;. You can create API keys in the Mixpeek dashboard under Organization Settings.
+     * @param {string} [authorization2]
+     * @param {string} [xNamespace] REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like \&#39;my-namespace\&#39;
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getAvailableStepsTaxonomiesTaxonomyIdAnalytics: (taxonomyId: string, collectionId: string, authorization?: string, authorization2?: string, xNamespace?: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Get all available steps for a taxonomy and collection.  This endpoint discovers what steps exist in your analytics data by querying the ClickHouse taxonomy_events table. Use this before querying transitions or paths to understand what step values you can use.  **Use Cases:** - Discover available steps before querying analytics - Validate step names (avoid typos in from_step/to_step) - See which steps have the most events - Check data freshness (first_seen/last_seen timestamps)  **Example Usage:** ```python # 1. Get available steps GET /v1/taxonomies/tax_sales/analytics/available-steps?collection_id=col_emails  # Response: {     \"taxonomy_id\": \"tax_sales\",     \"collection_id\": \"col_emails\",     \"total_events\": 5432,     \"total_sequences\": 1000,     \"steps\": [         {\"step_key\": \"inquiry\", \"event_count\": 1000, ...},         {\"step_key\": \"followup\", \"event_count\": 450, ...},         {\"step_key\": \"closed_won\", \"event_count\": 350, ...}     ] }  # 2. Use discovered steps in transition query POST /v1/taxonomies/tax_sales/analytics/transitions {     \"collection_id\": \"col_emails\",     \"from_step\": \"inquiry\",      # From available steps     \"to_step\": \"closed_won\"      # From available steps } ```  Args:     request: FastAPI request object (contains tenant context)     taxonomy_id: Taxonomy ID to query     collection_id: Collection ID for filtering events  Returns:     AvailableStepsResponse with all steps sorted by event count (descending)  Raises:     NotFoundError: If taxonomy not found     ValidationError: If unable to query ClickHouse
+     * @summary Get Available Steps
+     * @param {string} taxonomyId
+     * @param {string} collectionId Collection ID to analyze
+     * @param {string} [authorization] REQUIRED: Bearer token authentication using your API key. Format: \&#39;Bearer sk_xxxxxxxxxxxxx\&#39;. You can create API keys in the Mixpeek dashboard under Organization Settings.
+     * @param {string} [authorization2]
+     * @param {string} [xNamespace] REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like \&#39;my-namespace\&#39;
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getAvailableStepsTaxonomiesTaxonomyIdAnalytics_3: (taxonomyId: string, collectionId: string, authorization?: string, authorization2?: string, xNamespace?: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+};
+/**
+ * TaxonomyAnalyticsApi - functional programming interface
+ * @export
+ */
+export declare const TaxonomyAnalyticsApiFp: (configuration?: Configuration) => {
+    /**
+     * Discover the most common multi-step paths documents take between two taxonomy steps.  Unlike the `/transitions` endpoint which only analyzes direct A→B transitions, this endpoint reveals the intermediate steps documents actually take.  ## Use Cases  **Email Thread Analysis:** - Question: What paths do emails take from \"inquiry\" to \"closed_won\"? - Discover: Some go inquiry → followup → proposal → closed_won - Discover: Others skip steps: inquiry → proposal → closed_won - Discover: Fast track: inquiry → closed_won  **Content Editorial Paths:** - Question: Common paths from \"draft\" to \"published\"? - Discover: draft → review → edit → review → published - Discover: draft → review → published (expedited) - Discover: Paths that loop back (draft → review → draft → review)  **Compliance Resolution Paths:** - Question: How do violations get resolved? - Discover: violation → investigated → remediated → resolved - Discover: violation → false_positive → closed - Discover: Escalation paths: violation → escalated → legal_review → resolved  ## Requirements  - Taxonomy must have `step_analytics` configured - Collection must contain documents with timestamp and sequence_id fields  ## Returns  **Completion Metrics:** - `total_sequences`: Sequences starting at from_step - `completed_sequences`: Number reaching to_step - `completion_rate`: Percentage that completed  **Paths (sorted by frequency):** - `path`: Ordered sequence of steps - `count`: Number of sequences following this path - `percentage`: Percentage of completing sequences - `avg_duration_sec`: Average time for this path  ## Example Request  ```json {     \"collection_id\": \"col_emails\",     \"taxonomy_id\": \"tax_sales_stages\",     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"max_path_length\": 10,     \"min_support\": 5 } ```  ## Example Response  ```json {     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"total_sequences\": 1000,     \"completed_sequences\": 350,     \"completion_rate\": 0.35,     \"paths\": [         {             \"path\": [\"inquiry\", \"followup\", \"proposal\", \"closed_won\"],             \"count\": 120,             \"percentage\": 34.3,             \"avg_duration_sec\": 604800.0         },         {             \"path\": [\"inquiry\", \"proposal\", \"closed_won\"],             \"count\": 90,             \"percentage\": 25.7,             \"avg_duration_sec\": 432000.0         },         {             \"path\": [\"inquiry\", \"closed_won\"],             \"count\": 70,             \"percentage\": 20.0,             \"avg_duration_sec\": 172800.0         }     ] } ```  ## Path Interpretation  **Length Analysis:** - Shorter paths indicate efficient progression - Longer paths may indicate complexity or bottlenecks - Loops (repeated steps) indicate rework or revisions  **Duration Analysis:** - Compare avg_duration_sec across paths - Shorter paths may not always be faster - Identify optimization opportunities  **Frequency Analysis:** - High-percentage paths are \"happy paths\" - Low-percentage paths may be edge cases or exceptions - Missing expected paths indicate drop-off points
+     * @summary Analyze multi-step transition paths
+     * @param {string} taxonomyId
+     * @param {PathAnalysisRequest} pathAnalysisRequest
+     * @param {string} [authorization] REQUIRED: Bearer token authentication using your API key. Format: \&#39;Bearer sk_xxxxxxxxxxxxx\&#39;. You can create API keys in the Mixpeek dashboard under Organization Settings.
+     * @param {string} [authorization2]
+     * @param {string} [xNamespace] REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like \&#39;my-namespace\&#39;
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    analyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics(taxonomyId: string, pathAnalysisRequest: PathAnalysisRequest, authorization?: string, authorization2?: string, xNamespace?: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<PathAnalysisResponse>>;
+    /**
+     * Discover the most common multi-step paths documents take between two taxonomy steps.  Unlike the `/transitions` endpoint which only analyzes direct A→B transitions, this endpoint reveals the intermediate steps documents actually take.  ## Use Cases  **Email Thread Analysis:** - Question: What paths do emails take from \"inquiry\" to \"closed_won\"? - Discover: Some go inquiry → followup → proposal → closed_won - Discover: Others skip steps: inquiry → proposal → closed_won - Discover: Fast track: inquiry → closed_won  **Content Editorial Paths:** - Question: Common paths from \"draft\" to \"published\"? - Discover: draft → review → edit → review → published - Discover: draft → review → published (expedited) - Discover: Paths that loop back (draft → review → draft → review)  **Compliance Resolution Paths:** - Question: How do violations get resolved? - Discover: violation → investigated → remediated → resolved - Discover: violation → false_positive → closed - Discover: Escalation paths: violation → escalated → legal_review → resolved  ## Requirements  - Taxonomy must have `step_analytics` configured - Collection must contain documents with timestamp and sequence_id fields  ## Returns  **Completion Metrics:** - `total_sequences`: Sequences starting at from_step - `completed_sequences`: Number reaching to_step - `completion_rate`: Percentage that completed  **Paths (sorted by frequency):** - `path`: Ordered sequence of steps - `count`: Number of sequences following this path - `percentage`: Percentage of completing sequences - `avg_duration_sec`: Average time for this path  ## Example Request  ```json {     \"collection_id\": \"col_emails\",     \"taxonomy_id\": \"tax_sales_stages\",     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"max_path_length\": 10,     \"min_support\": 5 } ```  ## Example Response  ```json {     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"total_sequences\": 1000,     \"completed_sequences\": 350,     \"completion_rate\": 0.35,     \"paths\": [         {             \"path\": [\"inquiry\", \"followup\", \"proposal\", \"closed_won\"],             \"count\": 120,             \"percentage\": 34.3,             \"avg_duration_sec\": 604800.0         },         {             \"path\": [\"inquiry\", \"proposal\", \"closed_won\"],             \"count\": 90,             \"percentage\": 25.7,             \"avg_duration_sec\": 432000.0         },         {             \"path\": [\"inquiry\", \"closed_won\"],             \"count\": 70,             \"percentage\": 20.0,             \"avg_duration_sec\": 172800.0         }     ] } ```  ## Path Interpretation  **Length Analysis:** - Shorter paths indicate efficient progression - Longer paths may indicate complexity or bottlenecks - Loops (repeated steps) indicate rework or revisions  **Duration Analysis:** - Compare avg_duration_sec across paths - Shorter paths may not always be faster - Identify optimization opportunities  **Frequency Analysis:** - High-percentage paths are \"happy paths\" - Low-percentage paths may be edge cases or exceptions - Missing expected paths indicate drop-off points
+     * @summary Analyze multi-step transition paths
+     * @param {string} taxonomyId
+     * @param {PathAnalysisRequest} pathAnalysisRequest
+     * @param {string} [authorization] REQUIRED: Bearer token authentication using your API key. Format: \&#39;Bearer sk_xxxxxxxxxxxxx\&#39;. You can create API keys in the Mixpeek dashboard under Organization Settings.
+     * @param {string} [authorization2]
+     * @param {string} [xNamespace] REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like \&#39;my-namespace\&#39;
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    analyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics_1(taxonomyId: string, pathAnalysisRequest: PathAnalysisRequest, authorization?: string, authorization2?: string, xNamespace?: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<PathAnalysisResponse>>;
+    /**
+     * Analyze how documents progress from one taxonomy step to another.  This endpoint computes conversion rates, duration statistics, and predictor lifts for documents transitioning between taxonomy labels.  ## Use Cases  **Email Thread Analysis:** - Question: How long from \"inquiry\" to \"closed_won\"? - Question: What % of inquiries result in sales? - Question: Which sender domains have highest conversion?  **Content Workflow Tracking:** - Question: Conversion rate from \"draft\" to \"published\"? - Question: How long does content stay in review? - Question: Which authors publish fastest?  **Safety Compliance Monitoring:** - Question: Time from violation detection to resolution? - Question: Success rate for remediation efforts?  ## Requirements  - Taxonomy must have `step_analytics` configured (or provide `override_step_analytics`) - Collection must contain documents enriched with this taxonomy - Documents must have timestamp and sequence grouping fields configured  ## Returns  **Conversion Metrics:** - `count`: Total sequences starting at from_step - `converted`: Number reaching to_step - `conversion_rate`: Percentage that converted  **Duration Statistics (if converted > 0):** - `mean`, `median`: Average and middle duration - `p90`, `p95`: 90th and 95th percentile durations - `std_dev`, `min`, `max`: Distribution statistics  **Top Predictors:** - Covariates with highest impact on conversion - Lift values (>1.0 = increases conversion, <1.0 = decreases) - Statistical significance via minimum support threshold  ## Example Request  ```json {     \"collection_id\": \"col_emails\",     \"taxonomy_id\": \"tax_sales_stages\",     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"max_window_days\": 90,     \"min_support\": 10 } ```  ## Example Response  ```json {     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"count\": 1000,     \"converted\": 350,     \"conversion_rate\": 0.35,     \"durations_sec\": {         \"mean\": 432000.0,         \"median\": 345600.0,         \"p50\": 345600.0,         \"p90\": 691200.0,         \"p95\": 864000.0     },     \"top_predictors\": [         {             \"field\": \"Sender Domain\",             \"value\": \"enterprise.com\",             \"count\": 150,             \"conversion_rate\": 0.75,             \"lift\": 2.14         }     ] } ```
+     * @summary Compute step transition analytics
+     * @param {string} taxonomyId
+     * @param {StepTransitionRequest} stepTransitionRequest
+     * @param {string} [authorization] REQUIRED: Bearer token authentication using your API key. Format: \&#39;Bearer sk_xxxxxxxxxxxxx\&#39;. You can create API keys in the Mixpeek dashboard under Organization Settings.
+     * @param {string} [authorization2]
+     * @param {string} [xNamespace] REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like \&#39;my-namespace\&#39;
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    computeStepTransitionsTaxonomiesTaxonomyIdAnalytics(taxonomyId: string, stepTransitionRequest: StepTransitionRequest, authorization?: string, authorization2?: string, xNamespace?: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<StepTransitionResponse>>;
+    /**
+     * Analyze how documents progress from one taxonomy step to another.  This endpoint computes conversion rates, duration statistics, and predictor lifts for documents transitioning between taxonomy labels.  ## Use Cases  **Email Thread Analysis:** - Question: How long from \"inquiry\" to \"closed_won\"? - Question: What % of inquiries result in sales? - Question: Which sender domains have highest conversion?  **Content Workflow Tracking:** - Question: Conversion rate from \"draft\" to \"published\"? - Question: How long does content stay in review? - Question: Which authors publish fastest?  **Safety Compliance Monitoring:** - Question: Time from violation detection to resolution? - Question: Success rate for remediation efforts?  ## Requirements  - Taxonomy must have `step_analytics` configured (or provide `override_step_analytics`) - Collection must contain documents enriched with this taxonomy - Documents must have timestamp and sequence grouping fields configured  ## Returns  **Conversion Metrics:** - `count`: Total sequences starting at from_step - `converted`: Number reaching to_step - `conversion_rate`: Percentage that converted  **Duration Statistics (if converted > 0):** - `mean`, `median`: Average and middle duration - `p90`, `p95`: 90th and 95th percentile durations - `std_dev`, `min`, `max`: Distribution statistics  **Top Predictors:** - Covariates with highest impact on conversion - Lift values (>1.0 = increases conversion, <1.0 = decreases) - Statistical significance via minimum support threshold  ## Example Request  ```json {     \"collection_id\": \"col_emails\",     \"taxonomy_id\": \"tax_sales_stages\",     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"max_window_days\": 90,     \"min_support\": 10 } ```  ## Example Response  ```json {     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"count\": 1000,     \"converted\": 350,     \"conversion_rate\": 0.35,     \"durations_sec\": {         \"mean\": 432000.0,         \"median\": 345600.0,         \"p50\": 345600.0,         \"p90\": 691200.0,         \"p95\": 864000.0     },     \"top_predictors\": [         {             \"field\": \"Sender Domain\",             \"value\": \"enterprise.com\",             \"count\": 150,             \"conversion_rate\": 0.75,             \"lift\": 2.14         }     ] } ```
+     * @summary Compute step transition analytics
+     * @param {string} taxonomyId
+     * @param {StepTransitionRequest} stepTransitionRequest
+     * @param {string} [authorization] REQUIRED: Bearer token authentication using your API key. Format: \&#39;Bearer sk_xxxxxxxxxxxxx\&#39;. You can create API keys in the Mixpeek dashboard under Organization Settings.
+     * @param {string} [authorization2]
+     * @param {string} [xNamespace] REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like \&#39;my-namespace\&#39;
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    computeStepTransitionsTaxonomiesTaxonomyIdAnalytics_2(taxonomyId: string, stepTransitionRequest: StepTransitionRequest, authorization?: string, authorization2?: string, xNamespace?: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<StepTransitionResponse>>;
+    /**
+     * Get all available steps for a taxonomy and collection.  This endpoint discovers what steps exist in your analytics data by querying the ClickHouse taxonomy_events table. Use this before querying transitions or paths to understand what step values you can use.  **Use Cases:** - Discover available steps before querying analytics - Validate step names (avoid typos in from_step/to_step) - See which steps have the most events - Check data freshness (first_seen/last_seen timestamps)  **Example Usage:** ```python # 1. Get available steps GET /v1/taxonomies/tax_sales/analytics/available-steps?collection_id=col_emails  # Response: {     \"taxonomy_id\": \"tax_sales\",     \"collection_id\": \"col_emails\",     \"total_events\": 5432,     \"total_sequences\": 1000,     \"steps\": [         {\"step_key\": \"inquiry\", \"event_count\": 1000, ...},         {\"step_key\": \"followup\", \"event_count\": 450, ...},         {\"step_key\": \"closed_won\", \"event_count\": 350, ...}     ] }  # 2. Use discovered steps in transition query POST /v1/taxonomies/tax_sales/analytics/transitions {     \"collection_id\": \"col_emails\",     \"from_step\": \"inquiry\",      # From available steps     \"to_step\": \"closed_won\"      # From available steps } ```  Args:     request: FastAPI request object (contains tenant context)     taxonomy_id: Taxonomy ID to query     collection_id: Collection ID for filtering events  Returns:     AvailableStepsResponse with all steps sorted by event count (descending)  Raises:     NotFoundError: If taxonomy not found     ValidationError: If unable to query ClickHouse
+     * @summary Get Available Steps
+     * @param {string} taxonomyId
+     * @param {string} collectionId Collection ID to analyze
+     * @param {string} [authorization] REQUIRED: Bearer token authentication using your API key. Format: \&#39;Bearer sk_xxxxxxxxxxxxx\&#39;. You can create API keys in the Mixpeek dashboard under Organization Settings.
+     * @param {string} [authorization2]
+     * @param {string} [xNamespace] REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like \&#39;my-namespace\&#39;
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getAvailableStepsTaxonomiesTaxonomyIdAnalytics(taxonomyId: string, collectionId: string, authorization?: string, authorization2?: string, xNamespace?: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<AvailableStepsResponse>>;
+    /**
+     * Get all available steps for a taxonomy and collection.  This endpoint discovers what steps exist in your analytics data by querying the ClickHouse taxonomy_events table. Use this before querying transitions or paths to understand what step values you can use.  **Use Cases:** - Discover available steps before querying analytics - Validate step names (avoid typos in from_step/to_step) - See which steps have the most events - Check data freshness (first_seen/last_seen timestamps)  **Example Usage:** ```python # 1. Get available steps GET /v1/taxonomies/tax_sales/analytics/available-steps?collection_id=col_emails  # Response: {     \"taxonomy_id\": \"tax_sales\",     \"collection_id\": \"col_emails\",     \"total_events\": 5432,     \"total_sequences\": 1000,     \"steps\": [         {\"step_key\": \"inquiry\", \"event_count\": 1000, ...},         {\"step_key\": \"followup\", \"event_count\": 450, ...},         {\"step_key\": \"closed_won\", \"event_count\": 350, ...}     ] }  # 2. Use discovered steps in transition query POST /v1/taxonomies/tax_sales/analytics/transitions {     \"collection_id\": \"col_emails\",     \"from_step\": \"inquiry\",      # From available steps     \"to_step\": \"closed_won\"      # From available steps } ```  Args:     request: FastAPI request object (contains tenant context)     taxonomy_id: Taxonomy ID to query     collection_id: Collection ID for filtering events  Returns:     AvailableStepsResponse with all steps sorted by event count (descending)  Raises:     NotFoundError: If taxonomy not found     ValidationError: If unable to query ClickHouse
+     * @summary Get Available Steps
+     * @param {string} taxonomyId
+     * @param {string} collectionId Collection ID to analyze
+     * @param {string} [authorization] REQUIRED: Bearer token authentication using your API key. Format: \&#39;Bearer sk_xxxxxxxxxxxxx\&#39;. You can create API keys in the Mixpeek dashboard under Organization Settings.
+     * @param {string} [authorization2]
+     * @param {string} [xNamespace] REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like \&#39;my-namespace\&#39;
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getAvailableStepsTaxonomiesTaxonomyIdAnalytics_3(taxonomyId: string, collectionId: string, authorization?: string, authorization2?: string, xNamespace?: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<AvailableStepsResponse>>;
+};
+/**
+ * TaxonomyAnalyticsApi - factory interface
+ * @export
+ */
+export declare const TaxonomyAnalyticsApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
+    /**
+     * Discover the most common multi-step paths documents take between two taxonomy steps.  Unlike the `/transitions` endpoint which only analyzes direct A→B transitions, this endpoint reveals the intermediate steps documents actually take.  ## Use Cases  **Email Thread Analysis:** - Question: What paths do emails take from \"inquiry\" to \"closed_won\"? - Discover: Some go inquiry → followup → proposal → closed_won - Discover: Others skip steps: inquiry → proposal → closed_won - Discover: Fast track: inquiry → closed_won  **Content Editorial Paths:** - Question: Common paths from \"draft\" to \"published\"? - Discover: draft → review → edit → review → published - Discover: draft → review → published (expedited) - Discover: Paths that loop back (draft → review → draft → review)  **Compliance Resolution Paths:** - Question: How do violations get resolved? - Discover: violation → investigated → remediated → resolved - Discover: violation → false_positive → closed - Discover: Escalation paths: violation → escalated → legal_review → resolved  ## Requirements  - Taxonomy must have `step_analytics` configured - Collection must contain documents with timestamp and sequence_id fields  ## Returns  **Completion Metrics:** - `total_sequences`: Sequences starting at from_step - `completed_sequences`: Number reaching to_step - `completion_rate`: Percentage that completed  **Paths (sorted by frequency):** - `path`: Ordered sequence of steps - `count`: Number of sequences following this path - `percentage`: Percentage of completing sequences - `avg_duration_sec`: Average time for this path  ## Example Request  ```json {     \"collection_id\": \"col_emails\",     \"taxonomy_id\": \"tax_sales_stages\",     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"max_path_length\": 10,     \"min_support\": 5 } ```  ## Example Response  ```json {     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"total_sequences\": 1000,     \"completed_sequences\": 350,     \"completion_rate\": 0.35,     \"paths\": [         {             \"path\": [\"inquiry\", \"followup\", \"proposal\", \"closed_won\"],             \"count\": 120,             \"percentage\": 34.3,             \"avg_duration_sec\": 604800.0         },         {             \"path\": [\"inquiry\", \"proposal\", \"closed_won\"],             \"count\": 90,             \"percentage\": 25.7,             \"avg_duration_sec\": 432000.0         },         {             \"path\": [\"inquiry\", \"closed_won\"],             \"count\": 70,             \"percentage\": 20.0,             \"avg_duration_sec\": 172800.0         }     ] } ```  ## Path Interpretation  **Length Analysis:** - Shorter paths indicate efficient progression - Longer paths may indicate complexity or bottlenecks - Loops (repeated steps) indicate rework or revisions  **Duration Analysis:** - Compare avg_duration_sec across paths - Shorter paths may not always be faster - Identify optimization opportunities  **Frequency Analysis:** - High-percentage paths are \"happy paths\" - Low-percentage paths may be edge cases or exceptions - Missing expected paths indicate drop-off points
+     * @summary Analyze multi-step transition paths
+     * @param {TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalyticsRequest} requestParameters Request parameters.
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    analyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics(requestParameters: TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalyticsRequest, options?: RawAxiosRequestConfig): AxiosPromise<PathAnalysisResponse>;
+    /**
+     * Discover the most common multi-step paths documents take between two taxonomy steps.  Unlike the `/transitions` endpoint which only analyzes direct A→B transitions, this endpoint reveals the intermediate steps documents actually take.  ## Use Cases  **Email Thread Analysis:** - Question: What paths do emails take from \"inquiry\" to \"closed_won\"? - Discover: Some go inquiry → followup → proposal → closed_won - Discover: Others skip steps: inquiry → proposal → closed_won - Discover: Fast track: inquiry → closed_won  **Content Editorial Paths:** - Question: Common paths from \"draft\" to \"published\"? - Discover: draft → review → edit → review → published - Discover: draft → review → published (expedited) - Discover: Paths that loop back (draft → review → draft → review)  **Compliance Resolution Paths:** - Question: How do violations get resolved? - Discover: violation → investigated → remediated → resolved - Discover: violation → false_positive → closed - Discover: Escalation paths: violation → escalated → legal_review → resolved  ## Requirements  - Taxonomy must have `step_analytics` configured - Collection must contain documents with timestamp and sequence_id fields  ## Returns  **Completion Metrics:** - `total_sequences`: Sequences starting at from_step - `completed_sequences`: Number reaching to_step - `completion_rate`: Percentage that completed  **Paths (sorted by frequency):** - `path`: Ordered sequence of steps - `count`: Number of sequences following this path - `percentage`: Percentage of completing sequences - `avg_duration_sec`: Average time for this path  ## Example Request  ```json {     \"collection_id\": \"col_emails\",     \"taxonomy_id\": \"tax_sales_stages\",     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"max_path_length\": 10,     \"min_support\": 5 } ```  ## Example Response  ```json {     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"total_sequences\": 1000,     \"completed_sequences\": 350,     \"completion_rate\": 0.35,     \"paths\": [         {             \"path\": [\"inquiry\", \"followup\", \"proposal\", \"closed_won\"],             \"count\": 120,             \"percentage\": 34.3,             \"avg_duration_sec\": 604800.0         },         {             \"path\": [\"inquiry\", \"proposal\", \"closed_won\"],             \"count\": 90,             \"percentage\": 25.7,             \"avg_duration_sec\": 432000.0         },         {             \"path\": [\"inquiry\", \"closed_won\"],             \"count\": 70,             \"percentage\": 20.0,             \"avg_duration_sec\": 172800.0         }     ] } ```  ## Path Interpretation  **Length Analysis:** - Shorter paths indicate efficient progression - Longer paths may indicate complexity or bottlenecks - Loops (repeated steps) indicate rework or revisions  **Duration Analysis:** - Compare avg_duration_sec across paths - Shorter paths may not always be faster - Identify optimization opportunities  **Frequency Analysis:** - High-percentage paths are \"happy paths\" - Low-percentage paths may be edge cases or exceptions - Missing expected paths indicate drop-off points
+     * @summary Analyze multi-step transition paths
+     * @param {TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics0Request} requestParameters Request parameters.
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    analyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics_1(requestParameters: TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics0Request, options?: RawAxiosRequestConfig): AxiosPromise<PathAnalysisResponse>;
+    /**
+     * Analyze how documents progress from one taxonomy step to another.  This endpoint computes conversion rates, duration statistics, and predictor lifts for documents transitioning between taxonomy labels.  ## Use Cases  **Email Thread Analysis:** - Question: How long from \"inquiry\" to \"closed_won\"? - Question: What % of inquiries result in sales? - Question: Which sender domains have highest conversion?  **Content Workflow Tracking:** - Question: Conversion rate from \"draft\" to \"published\"? - Question: How long does content stay in review? - Question: Which authors publish fastest?  **Safety Compliance Monitoring:** - Question: Time from violation detection to resolution? - Question: Success rate for remediation efforts?  ## Requirements  - Taxonomy must have `step_analytics` configured (or provide `override_step_analytics`) - Collection must contain documents enriched with this taxonomy - Documents must have timestamp and sequence grouping fields configured  ## Returns  **Conversion Metrics:** - `count`: Total sequences starting at from_step - `converted`: Number reaching to_step - `conversion_rate`: Percentage that converted  **Duration Statistics (if converted > 0):** - `mean`, `median`: Average and middle duration - `p90`, `p95`: 90th and 95th percentile durations - `std_dev`, `min`, `max`: Distribution statistics  **Top Predictors:** - Covariates with highest impact on conversion - Lift values (>1.0 = increases conversion, <1.0 = decreases) - Statistical significance via minimum support threshold  ## Example Request  ```json {     \"collection_id\": \"col_emails\",     \"taxonomy_id\": \"tax_sales_stages\",     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"max_window_days\": 90,     \"min_support\": 10 } ```  ## Example Response  ```json {     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"count\": 1000,     \"converted\": 350,     \"conversion_rate\": 0.35,     \"durations_sec\": {         \"mean\": 432000.0,         \"median\": 345600.0,         \"p50\": 345600.0,         \"p90\": 691200.0,         \"p95\": 864000.0     },     \"top_predictors\": [         {             \"field\": \"Sender Domain\",             \"value\": \"enterprise.com\",             \"count\": 150,             \"conversion_rate\": 0.75,             \"lift\": 2.14         }     ] } ```
+     * @summary Compute step transition analytics
+     * @param {TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalyticsRequest} requestParameters Request parameters.
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    computeStepTransitionsTaxonomiesTaxonomyIdAnalytics(requestParameters: TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalyticsRequest, options?: RawAxiosRequestConfig): AxiosPromise<StepTransitionResponse>;
+    /**
+     * Analyze how documents progress from one taxonomy step to another.  This endpoint computes conversion rates, duration statistics, and predictor lifts for documents transitioning between taxonomy labels.  ## Use Cases  **Email Thread Analysis:** - Question: How long from \"inquiry\" to \"closed_won\"? - Question: What % of inquiries result in sales? - Question: Which sender domains have highest conversion?  **Content Workflow Tracking:** - Question: Conversion rate from \"draft\" to \"published\"? - Question: How long does content stay in review? - Question: Which authors publish fastest?  **Safety Compliance Monitoring:** - Question: Time from violation detection to resolution? - Question: Success rate for remediation efforts?  ## Requirements  - Taxonomy must have `step_analytics` configured (or provide `override_step_analytics`) - Collection must contain documents enriched with this taxonomy - Documents must have timestamp and sequence grouping fields configured  ## Returns  **Conversion Metrics:** - `count`: Total sequences starting at from_step - `converted`: Number reaching to_step - `conversion_rate`: Percentage that converted  **Duration Statistics (if converted > 0):** - `mean`, `median`: Average and middle duration - `p90`, `p95`: 90th and 95th percentile durations - `std_dev`, `min`, `max`: Distribution statistics  **Top Predictors:** - Covariates with highest impact on conversion - Lift values (>1.0 = increases conversion, <1.0 = decreases) - Statistical significance via minimum support threshold  ## Example Request  ```json {     \"collection_id\": \"col_emails\",     \"taxonomy_id\": \"tax_sales_stages\",     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"max_window_days\": 90,     \"min_support\": 10 } ```  ## Example Response  ```json {     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"count\": 1000,     \"converted\": 350,     \"conversion_rate\": 0.35,     \"durations_sec\": {         \"mean\": 432000.0,         \"median\": 345600.0,         \"p50\": 345600.0,         \"p90\": 691200.0,         \"p95\": 864000.0     },     \"top_predictors\": [         {             \"field\": \"Sender Domain\",             \"value\": \"enterprise.com\",             \"count\": 150,             \"conversion_rate\": 0.75,             \"lift\": 2.14         }     ] } ```
+     * @summary Compute step transition analytics
+     * @param {TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalytics0Request} requestParameters Request parameters.
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    computeStepTransitionsTaxonomiesTaxonomyIdAnalytics_2(requestParameters: TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalytics0Request, options?: RawAxiosRequestConfig): AxiosPromise<StepTransitionResponse>;
+    /**
+     * Get all available steps for a taxonomy and collection.  This endpoint discovers what steps exist in your analytics data by querying the ClickHouse taxonomy_events table. Use this before querying transitions or paths to understand what step values you can use.  **Use Cases:** - Discover available steps before querying analytics - Validate step names (avoid typos in from_step/to_step) - See which steps have the most events - Check data freshness (first_seen/last_seen timestamps)  **Example Usage:** ```python # 1. Get available steps GET /v1/taxonomies/tax_sales/analytics/available-steps?collection_id=col_emails  # Response: {     \"taxonomy_id\": \"tax_sales\",     \"collection_id\": \"col_emails\",     \"total_events\": 5432,     \"total_sequences\": 1000,     \"steps\": [         {\"step_key\": \"inquiry\", \"event_count\": 1000, ...},         {\"step_key\": \"followup\", \"event_count\": 450, ...},         {\"step_key\": \"closed_won\", \"event_count\": 350, ...}     ] }  # 2. Use discovered steps in transition query POST /v1/taxonomies/tax_sales/analytics/transitions {     \"collection_id\": \"col_emails\",     \"from_step\": \"inquiry\",      # From available steps     \"to_step\": \"closed_won\"      # From available steps } ```  Args:     request: FastAPI request object (contains tenant context)     taxonomy_id: Taxonomy ID to query     collection_id: Collection ID for filtering events  Returns:     AvailableStepsResponse with all steps sorted by event count (descending)  Raises:     NotFoundError: If taxonomy not found     ValidationError: If unable to query ClickHouse
+     * @summary Get Available Steps
+     * @param {TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalyticsRequest} requestParameters Request parameters.
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getAvailableStepsTaxonomiesTaxonomyIdAnalytics(requestParameters: TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalyticsRequest, options?: RawAxiosRequestConfig): AxiosPromise<AvailableStepsResponse>;
+    /**
+     * Get all available steps for a taxonomy and collection.  This endpoint discovers what steps exist in your analytics data by querying the ClickHouse taxonomy_events table. Use this before querying transitions or paths to understand what step values you can use.  **Use Cases:** - Discover available steps before querying analytics - Validate step names (avoid typos in from_step/to_step) - See which steps have the most events - Check data freshness (first_seen/last_seen timestamps)  **Example Usage:** ```python # 1. Get available steps GET /v1/taxonomies/tax_sales/analytics/available-steps?collection_id=col_emails  # Response: {     \"taxonomy_id\": \"tax_sales\",     \"collection_id\": \"col_emails\",     \"total_events\": 5432,     \"total_sequences\": 1000,     \"steps\": [         {\"step_key\": \"inquiry\", \"event_count\": 1000, ...},         {\"step_key\": \"followup\", \"event_count\": 450, ...},         {\"step_key\": \"closed_won\", \"event_count\": 350, ...}     ] }  # 2. Use discovered steps in transition query POST /v1/taxonomies/tax_sales/analytics/transitions {     \"collection_id\": \"col_emails\",     \"from_step\": \"inquiry\",      # From available steps     \"to_step\": \"closed_won\"      # From available steps } ```  Args:     request: FastAPI request object (contains tenant context)     taxonomy_id: Taxonomy ID to query     collection_id: Collection ID for filtering events  Returns:     AvailableStepsResponse with all steps sorted by event count (descending)  Raises:     NotFoundError: If taxonomy not found     ValidationError: If unable to query ClickHouse
+     * @summary Get Available Steps
+     * @param {TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalytics0Request} requestParameters Request parameters.
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getAvailableStepsTaxonomiesTaxonomyIdAnalytics_3(requestParameters: TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalytics0Request, options?: RawAxiosRequestConfig): AxiosPromise<AvailableStepsResponse>;
+};
+/**
+ * Request parameters for analyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics operation in TaxonomyAnalyticsApi.
+ * @export
+ * @interface TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalyticsRequest
+ */
+export interface TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalyticsRequest {
+    /**
+     *
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics
+     */
+    readonly taxonomyId: string;
+    /**
+     *
+     * @type {PathAnalysisRequest}
+     * @memberof TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics
+     */
+    readonly pathAnalysisRequest: PathAnalysisRequest;
+    /**
+     * REQUIRED: Bearer token authentication using your API key. Format: \&#39;Bearer sk_xxxxxxxxxxxxx\&#39;. You can create API keys in the Mixpeek dashboard under Organization Settings.
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics
+     */
+    readonly authorization?: string;
+    /**
+     *
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics
+     */
+    readonly authorization2?: string;
+    /**
+     * REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like \&#39;my-namespace\&#39;
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics
+     */
+    readonly xNamespace?: string;
+}
+/**
+ * Request parameters for analyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics_1 operation in TaxonomyAnalyticsApi.
+ * @export
+ * @interface TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics0Request
+ */
+export interface TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics0Request {
+    /**
+     *
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics0
+     */
+    readonly taxonomyId: string;
+    /**
+     *
+     * @type {PathAnalysisRequest}
+     * @memberof TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics0
+     */
+    readonly pathAnalysisRequest: PathAnalysisRequest;
+    /**
+     * REQUIRED: Bearer token authentication using your API key. Format: \&#39;Bearer sk_xxxxxxxxxxxxx\&#39;. You can create API keys in the Mixpeek dashboard under Organization Settings.
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics0
+     */
+    readonly authorization?: string;
+    /**
+     *
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics0
+     */
+    readonly authorization2?: string;
+    /**
+     * REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like \&#39;my-namespace\&#39;
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics0
+     */
+    readonly xNamespace?: string;
+}
+/**
+ * Request parameters for computeStepTransitionsTaxonomiesTaxonomyIdAnalytics operation in TaxonomyAnalyticsApi.
+ * @export
+ * @interface TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalyticsRequest
+ */
+export interface TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalyticsRequest {
+    /**
+     *
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalytics
+     */
+    readonly taxonomyId: string;
+    /**
+     *
+     * @type {StepTransitionRequest}
+     * @memberof TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalytics
+     */
+    readonly stepTransitionRequest: StepTransitionRequest;
+    /**
+     * REQUIRED: Bearer token authentication using your API key. Format: \&#39;Bearer sk_xxxxxxxxxxxxx\&#39;. You can create API keys in the Mixpeek dashboard under Organization Settings.
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalytics
+     */
+    readonly authorization?: string;
+    /**
+     *
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalytics
+     */
+    readonly authorization2?: string;
+    /**
+     * REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like \&#39;my-namespace\&#39;
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalytics
+     */
+    readonly xNamespace?: string;
+}
+/**
+ * Request parameters for computeStepTransitionsTaxonomiesTaxonomyIdAnalytics_2 operation in TaxonomyAnalyticsApi.
+ * @export
+ * @interface TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalytics0Request
+ */
+export interface TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalytics0Request {
+    /**
+     *
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalytics0
+     */
+    readonly taxonomyId: string;
+    /**
+     *
+     * @type {StepTransitionRequest}
+     * @memberof TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalytics0
+     */
+    readonly stepTransitionRequest: StepTransitionRequest;
+    /**
+     * REQUIRED: Bearer token authentication using your API key. Format: \&#39;Bearer sk_xxxxxxxxxxxxx\&#39;. You can create API keys in the Mixpeek dashboard under Organization Settings.
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalytics0
+     */
+    readonly authorization?: string;
+    /**
+     *
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalytics0
+     */
+    readonly authorization2?: string;
+    /**
+     * REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like \&#39;my-namespace\&#39;
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalytics0
+     */
+    readonly xNamespace?: string;
+}
+/**
+ * Request parameters for getAvailableStepsTaxonomiesTaxonomyIdAnalytics operation in TaxonomyAnalyticsApi.
+ * @export
+ * @interface TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalyticsRequest
+ */
+export interface TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalyticsRequest {
+    /**
+     *
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalytics
+     */
+    readonly taxonomyId: string;
+    /**
+     * Collection ID to analyze
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalytics
+     */
+    readonly collectionId: string;
+    /**
+     * REQUIRED: Bearer token authentication using your API key. Format: \&#39;Bearer sk_xxxxxxxxxxxxx\&#39;. You can create API keys in the Mixpeek dashboard under Organization Settings.
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalytics
+     */
+    readonly authorization?: string;
+    /**
+     *
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalytics
+     */
+    readonly authorization2?: string;
+    /**
+     * REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like \&#39;my-namespace\&#39;
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalytics
+     */
+    readonly xNamespace?: string;
+}
+/**
+ * Request parameters for getAvailableStepsTaxonomiesTaxonomyIdAnalytics_3 operation in TaxonomyAnalyticsApi.
+ * @export
+ * @interface TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalytics0Request
+ */
+export interface TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalytics0Request {
+    /**
+     *
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalytics0
+     */
+    readonly taxonomyId: string;
+    /**
+     * Collection ID to analyze
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalytics0
+     */
+    readonly collectionId: string;
+    /**
+     * REQUIRED: Bearer token authentication using your API key. Format: \&#39;Bearer sk_xxxxxxxxxxxxx\&#39;. You can create API keys in the Mixpeek dashboard under Organization Settings.
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalytics0
+     */
+    readonly authorization?: string;
+    /**
+     *
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalytics0
+     */
+    readonly authorization2?: string;
+    /**
+     * REQUIRED: Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like \&#39;my-namespace\&#39;
+     * @type {string}
+     * @memberof TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalytics0
+     */
+    readonly xNamespace?: string;
+}
+/**
+ * TaxonomyAnalyticsApi - object-oriented interface
+ * @export
+ * @class TaxonomyAnalyticsApi
+ * @extends {BaseAPI}
+ */
+export declare class TaxonomyAnalyticsApi extends BaseAPI {
+    /**
+     * Discover the most common multi-step paths documents take between two taxonomy steps.  Unlike the `/transitions` endpoint which only analyzes direct A→B transitions, this endpoint reveals the intermediate steps documents actually take.  ## Use Cases  **Email Thread Analysis:** - Question: What paths do emails take from \"inquiry\" to \"closed_won\"? - Discover: Some go inquiry → followup → proposal → closed_won - Discover: Others skip steps: inquiry → proposal → closed_won - Discover: Fast track: inquiry → closed_won  **Content Editorial Paths:** - Question: Common paths from \"draft\" to \"published\"? - Discover: draft → review → edit → review → published - Discover: draft → review → published (expedited) - Discover: Paths that loop back (draft → review → draft → review)  **Compliance Resolution Paths:** - Question: How do violations get resolved? - Discover: violation → investigated → remediated → resolved - Discover: violation → false_positive → closed - Discover: Escalation paths: violation → escalated → legal_review → resolved  ## Requirements  - Taxonomy must have `step_analytics` configured - Collection must contain documents with timestamp and sequence_id fields  ## Returns  **Completion Metrics:** - `total_sequences`: Sequences starting at from_step - `completed_sequences`: Number reaching to_step - `completion_rate`: Percentage that completed  **Paths (sorted by frequency):** - `path`: Ordered sequence of steps - `count`: Number of sequences following this path - `percentage`: Percentage of completing sequences - `avg_duration_sec`: Average time for this path  ## Example Request  ```json {     \"collection_id\": \"col_emails\",     \"taxonomy_id\": \"tax_sales_stages\",     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"max_path_length\": 10,     \"min_support\": 5 } ```  ## Example Response  ```json {     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"total_sequences\": 1000,     \"completed_sequences\": 350,     \"completion_rate\": 0.35,     \"paths\": [         {             \"path\": [\"inquiry\", \"followup\", \"proposal\", \"closed_won\"],             \"count\": 120,             \"percentage\": 34.3,             \"avg_duration_sec\": 604800.0         },         {             \"path\": [\"inquiry\", \"proposal\", \"closed_won\"],             \"count\": 90,             \"percentage\": 25.7,             \"avg_duration_sec\": 432000.0         },         {             \"path\": [\"inquiry\", \"closed_won\"],             \"count\": 70,             \"percentage\": 20.0,             \"avg_duration_sec\": 172800.0         }     ] } ```  ## Path Interpretation  **Length Analysis:** - Shorter paths indicate efficient progression - Longer paths may indicate complexity or bottlenecks - Loops (repeated steps) indicate rework or revisions  **Duration Analysis:** - Compare avg_duration_sec across paths - Shorter paths may not always be faster - Identify optimization opportunities  **Frequency Analysis:** - High-percentage paths are \"happy paths\" - Low-percentage paths may be edge cases or exceptions - Missing expected paths indicate drop-off points
+     * @summary Analyze multi-step transition paths
+     * @param {TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalyticsRequest} requestParameters Request parameters.
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof TaxonomyAnalyticsApi
+     */
+    analyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics(requestParameters: TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalyticsRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<PathAnalysisResponse, any, {}>>;
+    /**
+     * Discover the most common multi-step paths documents take between two taxonomy steps.  Unlike the `/transitions` endpoint which only analyzes direct A→B transitions, this endpoint reveals the intermediate steps documents actually take.  ## Use Cases  **Email Thread Analysis:** - Question: What paths do emails take from \"inquiry\" to \"closed_won\"? - Discover: Some go inquiry → followup → proposal → closed_won - Discover: Others skip steps: inquiry → proposal → closed_won - Discover: Fast track: inquiry → closed_won  **Content Editorial Paths:** - Question: Common paths from \"draft\" to \"published\"? - Discover: draft → review → edit → review → published - Discover: draft → review → published (expedited) - Discover: Paths that loop back (draft → review → draft → review)  **Compliance Resolution Paths:** - Question: How do violations get resolved? - Discover: violation → investigated → remediated → resolved - Discover: violation → false_positive → closed - Discover: Escalation paths: violation → escalated → legal_review → resolved  ## Requirements  - Taxonomy must have `step_analytics` configured - Collection must contain documents with timestamp and sequence_id fields  ## Returns  **Completion Metrics:** - `total_sequences`: Sequences starting at from_step - `completed_sequences`: Number reaching to_step - `completion_rate`: Percentage that completed  **Paths (sorted by frequency):** - `path`: Ordered sequence of steps - `count`: Number of sequences following this path - `percentage`: Percentage of completing sequences - `avg_duration_sec`: Average time for this path  ## Example Request  ```json {     \"collection_id\": \"col_emails\",     \"taxonomy_id\": \"tax_sales_stages\",     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"max_path_length\": 10,     \"min_support\": 5 } ```  ## Example Response  ```json {     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"total_sequences\": 1000,     \"completed_sequences\": 350,     \"completion_rate\": 0.35,     \"paths\": [         {             \"path\": [\"inquiry\", \"followup\", \"proposal\", \"closed_won\"],             \"count\": 120,             \"percentage\": 34.3,             \"avg_duration_sec\": 604800.0         },         {             \"path\": [\"inquiry\", \"proposal\", \"closed_won\"],             \"count\": 90,             \"percentage\": 25.7,             \"avg_duration_sec\": 432000.0         },         {             \"path\": [\"inquiry\", \"closed_won\"],             \"count\": 70,             \"percentage\": 20.0,             \"avg_duration_sec\": 172800.0         }     ] } ```  ## Path Interpretation  **Length Analysis:** - Shorter paths indicate efficient progression - Longer paths may indicate complexity or bottlenecks - Loops (repeated steps) indicate rework or revisions  **Duration Analysis:** - Compare avg_duration_sec across paths - Shorter paths may not always be faster - Identify optimization opportunities  **Frequency Analysis:** - High-percentage paths are \"happy paths\" - Low-percentage paths may be edge cases or exceptions - Missing expected paths indicate drop-off points
+     * @summary Analyze multi-step transition paths
+     * @param {TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics0Request} requestParameters Request parameters.
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof TaxonomyAnalyticsApi
+     */
+    analyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics_1(requestParameters: TaxonomyAnalyticsApiAnalyzeTransitionPathsTaxonomiesTaxonomyIdAnalytics0Request, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<PathAnalysisResponse, any, {}>>;
+    /**
+     * Analyze how documents progress from one taxonomy step to another.  This endpoint computes conversion rates, duration statistics, and predictor lifts for documents transitioning between taxonomy labels.  ## Use Cases  **Email Thread Analysis:** - Question: How long from \"inquiry\" to \"closed_won\"? - Question: What % of inquiries result in sales? - Question: Which sender domains have highest conversion?  **Content Workflow Tracking:** - Question: Conversion rate from \"draft\" to \"published\"? - Question: How long does content stay in review? - Question: Which authors publish fastest?  **Safety Compliance Monitoring:** - Question: Time from violation detection to resolution? - Question: Success rate for remediation efforts?  ## Requirements  - Taxonomy must have `step_analytics` configured (or provide `override_step_analytics`) - Collection must contain documents enriched with this taxonomy - Documents must have timestamp and sequence grouping fields configured  ## Returns  **Conversion Metrics:** - `count`: Total sequences starting at from_step - `converted`: Number reaching to_step - `conversion_rate`: Percentage that converted  **Duration Statistics (if converted > 0):** - `mean`, `median`: Average and middle duration - `p90`, `p95`: 90th and 95th percentile durations - `std_dev`, `min`, `max`: Distribution statistics  **Top Predictors:** - Covariates with highest impact on conversion - Lift values (>1.0 = increases conversion, <1.0 = decreases) - Statistical significance via minimum support threshold  ## Example Request  ```json {     \"collection_id\": \"col_emails\",     \"taxonomy_id\": \"tax_sales_stages\",     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"max_window_days\": 90,     \"min_support\": 10 } ```  ## Example Response  ```json {     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"count\": 1000,     \"converted\": 350,     \"conversion_rate\": 0.35,     \"durations_sec\": {         \"mean\": 432000.0,         \"median\": 345600.0,         \"p50\": 345600.0,         \"p90\": 691200.0,         \"p95\": 864000.0     },     \"top_predictors\": [         {             \"field\": \"Sender Domain\",             \"value\": \"enterprise.com\",             \"count\": 150,             \"conversion_rate\": 0.75,             \"lift\": 2.14         }     ] } ```
+     * @summary Compute step transition analytics
+     * @param {TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalyticsRequest} requestParameters Request parameters.
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof TaxonomyAnalyticsApi
+     */
+    computeStepTransitionsTaxonomiesTaxonomyIdAnalytics(requestParameters: TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalyticsRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<StepTransitionResponse, any, {}>>;
+    /**
+     * Analyze how documents progress from one taxonomy step to another.  This endpoint computes conversion rates, duration statistics, and predictor lifts for documents transitioning between taxonomy labels.  ## Use Cases  **Email Thread Analysis:** - Question: How long from \"inquiry\" to \"closed_won\"? - Question: What % of inquiries result in sales? - Question: Which sender domains have highest conversion?  **Content Workflow Tracking:** - Question: Conversion rate from \"draft\" to \"published\"? - Question: How long does content stay in review? - Question: Which authors publish fastest?  **Safety Compliance Monitoring:** - Question: Time from violation detection to resolution? - Question: Success rate for remediation efforts?  ## Requirements  - Taxonomy must have `step_analytics` configured (or provide `override_step_analytics`) - Collection must contain documents enriched with this taxonomy - Documents must have timestamp and sequence grouping fields configured  ## Returns  **Conversion Metrics:** - `count`: Total sequences starting at from_step - `converted`: Number reaching to_step - `conversion_rate`: Percentage that converted  **Duration Statistics (if converted > 0):** - `mean`, `median`: Average and middle duration - `p90`, `p95`: 90th and 95th percentile durations - `std_dev`, `min`, `max`: Distribution statistics  **Top Predictors:** - Covariates with highest impact on conversion - Lift values (>1.0 = increases conversion, <1.0 = decreases) - Statistical significance via minimum support threshold  ## Example Request  ```json {     \"collection_id\": \"col_emails\",     \"taxonomy_id\": \"tax_sales_stages\",     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"max_window_days\": 90,     \"min_support\": 10 } ```  ## Example Response  ```json {     \"from_step\": \"inquiry\",     \"to_step\": \"closed_won\",     \"count\": 1000,     \"converted\": 350,     \"conversion_rate\": 0.35,     \"durations_sec\": {         \"mean\": 432000.0,         \"median\": 345600.0,         \"p50\": 345600.0,         \"p90\": 691200.0,         \"p95\": 864000.0     },     \"top_predictors\": [         {             \"field\": \"Sender Domain\",             \"value\": \"enterprise.com\",             \"count\": 150,             \"conversion_rate\": 0.75,             \"lift\": 2.14         }     ] } ```
+     * @summary Compute step transition analytics
+     * @param {TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalytics0Request} requestParameters Request parameters.
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof TaxonomyAnalyticsApi
+     */
+    computeStepTransitionsTaxonomiesTaxonomyIdAnalytics_2(requestParameters: TaxonomyAnalyticsApiComputeStepTransitionsTaxonomiesTaxonomyIdAnalytics0Request, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<StepTransitionResponse, any, {}>>;
+    /**
+     * Get all available steps for a taxonomy and collection.  This endpoint discovers what steps exist in your analytics data by querying the ClickHouse taxonomy_events table. Use this before querying transitions or paths to understand what step values you can use.  **Use Cases:** - Discover available steps before querying analytics - Validate step names (avoid typos in from_step/to_step) - See which steps have the most events - Check data freshness (first_seen/last_seen timestamps)  **Example Usage:** ```python # 1. Get available steps GET /v1/taxonomies/tax_sales/analytics/available-steps?collection_id=col_emails  # Response: {     \"taxonomy_id\": \"tax_sales\",     \"collection_id\": \"col_emails\",     \"total_events\": 5432,     \"total_sequences\": 1000,     \"steps\": [         {\"step_key\": \"inquiry\", \"event_count\": 1000, ...},         {\"step_key\": \"followup\", \"event_count\": 450, ...},         {\"step_key\": \"closed_won\", \"event_count\": 350, ...}     ] }  # 2. Use discovered steps in transition query POST /v1/taxonomies/tax_sales/analytics/transitions {     \"collection_id\": \"col_emails\",     \"from_step\": \"inquiry\",      # From available steps     \"to_step\": \"closed_won\"      # From available steps } ```  Args:     request: FastAPI request object (contains tenant context)     taxonomy_id: Taxonomy ID to query     collection_id: Collection ID for filtering events  Returns:     AvailableStepsResponse with all steps sorted by event count (descending)  Raises:     NotFoundError: If taxonomy not found     ValidationError: If unable to query ClickHouse
+     * @summary Get Available Steps
+     * @param {TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalyticsRequest} requestParameters Request parameters.
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof TaxonomyAnalyticsApi
+     */
+    getAvailableStepsTaxonomiesTaxonomyIdAnalytics(requestParameters: TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalyticsRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<AvailableStepsResponse, any, {}>>;
+    /**
+     * Get all available steps for a taxonomy and collection.  This endpoint discovers what steps exist in your analytics data by querying the ClickHouse taxonomy_events table. Use this before querying transitions or paths to understand what step values you can use.  **Use Cases:** - Discover available steps before querying analytics - Validate step names (avoid typos in from_step/to_step) - See which steps have the most events - Check data freshness (first_seen/last_seen timestamps)  **Example Usage:** ```python # 1. Get available steps GET /v1/taxonomies/tax_sales/analytics/available-steps?collection_id=col_emails  # Response: {     \"taxonomy_id\": \"tax_sales\",     \"collection_id\": \"col_emails\",     \"total_events\": 5432,     \"total_sequences\": 1000,     \"steps\": [         {\"step_key\": \"inquiry\", \"event_count\": 1000, ...},         {\"step_key\": \"followup\", \"event_count\": 450, ...},         {\"step_key\": \"closed_won\", \"event_count\": 350, ...}     ] }  # 2. Use discovered steps in transition query POST /v1/taxonomies/tax_sales/analytics/transitions {     \"collection_id\": \"col_emails\",     \"from_step\": \"inquiry\",      # From available steps     \"to_step\": \"closed_won\"      # From available steps } ```  Args:     request: FastAPI request object (contains tenant context)     taxonomy_id: Taxonomy ID to query     collection_id: Collection ID for filtering events  Returns:     AvailableStepsResponse with all steps sorted by event count (descending)  Raises:     NotFoundError: If taxonomy not found     ValidationError: If unable to query ClickHouse
+     * @summary Get Available Steps
+     * @param {TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalytics0Request} requestParameters Request parameters.
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof TaxonomyAnalyticsApi
+     */
+    getAvailableStepsTaxonomiesTaxonomyIdAnalytics_3(requestParameters: TaxonomyAnalyticsApiGetAvailableStepsTaxonomiesTaxonomyIdAnalytics0Request, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<AvailableStepsResponse, any, {}>>;
+}
+//# sourceMappingURL=taxonomy-analytics-api.d.ts.map