mixpeek 0.81.1

package/dist/models/health-status-input.d.ts

@@ -0,0 +1,23 @@
+/**
+ * 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.
+ */
+/**
+ * Health status of a retriever.
+ * @export
+ * @enum {string}
+ */
+export declare const HealthStatusInput: {
+    readonly Healthy: "healthy";
+    readonly Degraded: "degraded";
+    readonly Unhealthy: "unhealthy";
+};
+export type HealthStatusInput = typeof HealthStatusInput[keyof typeof HealthStatusInput];
+//# sourceMappingURL=health-status-input.d.ts.map

package/dist/models/health-status-input.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"health-status-input.d.ts","sourceRoot":"","sources":["../../models/health-status-input.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAIH;;;;GAIG;AAEH,eAAO,MAAM,iBAAiB;;;;CAIpB,CAAC;AAEX,MAAM,MAAM,iBAAiB,GAAG,OAAO,iBAAiB,CAAC,MAAM,OAAO,iBAAiB,CAAC,CAAC"}

package/dist/models/health-status-output.d.ts

@@ -0,0 +1,22 @@
+/**
+ * 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.
+ */
+/**
+ * Overall health status.
+ * @export
+ * @enum {string}
+ */
+export declare const HealthStatusOutput: {
+    readonly Ok: "OK";
+    readonly Degraded: "DEGRADED";
+};
+export type HealthStatusOutput = typeof HealthStatusOutput[keyof typeof HealthStatusOutput];
+//# sourceMappingURL=health-status-output.d.ts.map

package/dist/models/health-status-output.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"health-status-output.d.ts","sourceRoot":"","sources":["../../models/health-status-output.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAIH;;;;GAIG;AAEH,eAAO,MAAM,kBAAkB;;;CAGrB,CAAC;AAEX,MAAM,MAAM,kBAAkB,GAAG,OAAO,kBAAkB,CAAC,MAAM,OAAO,kBAAkB,CAAC,CAAC"}

package/dist/models/hero-config.d.ts

@@ -0,0 +1,86 @@
+/**
+ * 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.
+ */
+/**
+ * Hero section configuration for a page.
+ * @export
+ * @interface HeroConfig
+ */
+export interface HeroConfig {
+    /**
+     * Main headline text
+     * @type {string}
+     * @memberof HeroConfig
+     */
+    'headline': string;
+    /**
+     * Optional subheadline text
+     * @type {string}
+     * @memberof HeroConfig
+     */
+    'subheadline'?: string;
+    /**
+     * Background type
+     * @type {string}
+     * @memberof HeroConfig
+     */
+    'background_type'?: HeroConfigBackgroundTypeEnum;
+    /**
+     * URL for image or video background
+     * @type {string}
+     * @memberof HeroConfig
+     */
+    'background_url'?: string;
+    /**
+     * Background color for solid/gradient
+     * @type {string}
+     * @memberof HeroConfig
+     */
+    'background_color'?: string;
+    /**
+     * Hero text color
+     * @type {string}
+     * @memberof HeroConfig
+     */
+    'text_color'?: string;
+    /**
+     * Logo URL displayed in hero
+     * @type {string}
+     * @memberof HeroConfig
+     */
+    'logo_url'?: string;
+    /**
+     * Hero section height
+     * @type {string}
+     * @memberof HeroConfig
+     */
+    'height'?: string;
+    /**
+     * Call-to-action button label
+     * @type {string}
+     * @memberof HeroConfig
+     */
+    'cta_label'?: string;
+    /**
+     * Call-to-action button URL
+     * @type {string}
+     * @memberof HeroConfig
+     */
+    'cta_url'?: string;
+}
+export declare const HeroConfigBackgroundTypeEnum: {
+    readonly Image: "image";
+    readonly Video: "video";
+    readonly Gradient: "gradient";
+    readonly Solid: "solid";
+};
+export type HeroConfigBackgroundTypeEnum = typeof HeroConfigBackgroundTypeEnum[keyof typeof HeroConfigBackgroundTypeEnum];
+//# sourceMappingURL=hero-config.d.ts.map

package/dist/models/hero-config.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"hero-config.d.ts","sourceRoot":"","sources":["../../models/hero-config.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAIH;;;;GAIG;AACH,MAAM,WAAW,UAAU;IACvB;;;;OAIG;IACH,UAAU,EAAE,MAAM,CAAC;IACnB;;;;OAIG;IACH,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB;;;;OAIG;IACH,iBAAiB,CAAC,EAAE,4BAA4B,CAAC;IACjD;;;;OAIG;IACH,gBAAgB,CAAC,EAAE,MAAM,CAAC;IAC1B;;;;OAIG;IACH,kBAAkB,CAAC,EAAE,MAAM,CAAC;IAC5B;;;;OAIG;IACH,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB;;;;OAIG;IACH,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB;;;;OAIG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB;;;;OAIG;IACH,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB;;;;OAIG;IACH,SAAS,CAAC,EAAE,MAAM,CAAC;CACtB;AAED,eAAO,MAAM,4BAA4B;;;;;CAK/B,CAAC;AAEX,MAAM,MAAM,4BAA4B,GAAG,OAAO,4BAA4B,CAAC,MAAM,OAAO,4BAA4B,CAAC,CAAC"}

package/dist/models/hierarchical-enrichment-style.d.ts

@@ -0,0 +1,23 @@
+/**
+ * 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.
+ */
+/**
+ * How hierarchical taxonomy results should be structured in enriched documents.  Controls the field naming pattern for multi-tier taxonomy enrichment.
+ * @export
+ * @enum {string}
+ */
+export declare const HierarchicalEnrichmentStyle: {
+    readonly FullChain: "full_chain";
+    readonly BestMatch: "best_match";
+    readonly Combined: "combined";
+};
+export type HierarchicalEnrichmentStyle = typeof HierarchicalEnrichmentStyle[keyof typeof HierarchicalEnrichmentStyle];
+//# sourceMappingURL=hierarchical-enrichment-style.d.ts.map

package/dist/models/hierarchical-enrichment-style.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"hierarchical-enrichment-style.d.ts","sourceRoot":"","sources":["../../models/hierarchical-enrichment-style.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAIH;;;;GAIG;AAEH,eAAO,MAAM,2BAA2B;;;;CAI9B,CAAC;AAEX,MAAM,MAAM,2BAA2B,GAAG,OAAO,2BAA2B,CAAC,MAAM,OAAO,2BAA2B,CAAC,CAAC"}

package/dist/models/hierarchical-node-input.d.ts

@@ -0,0 +1,69 @@
+/**
+ * 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 { EnrichmentField } from './enrichment-field';
+import type { InputMapping } from './input-mapping';
+/**
+ * A node in a hierarchical taxonomy representing one level in the tree structure.  Each node represents a collection containing documents at a specific hierarchy level. Nodes form parent-child relationships to create multi-level taxonomies with property inheritance. When a document matches a child node, it inherits all properties from parent nodes up to the root.  Use Cases:     - Define organizational hierarchies: employees → managers → executives     - Create product categorizations: products → electronics → phones → smartphones     - Build classification trees: industries → technology → software     - Implement face recognition hierarchies: people → employees → team members     - Enable property inheritance: child nodes get all parent properties  Hierarchy Behavior:     - Root nodes: parent_collection_id = None (top of hierarchy)     - Child nodes: parent_collection_id references parent node\'s collection_id     - Property inheritance: Children inherit all parent enrichment_fields     - Path construction: Creates path array from root to leaf     - Multi-level matching: Documents matched at deepest applicable level  Configuration:     - Per-node retrievers: Override taxonomy-level retriever for specific nodes     - Per-node enrichment: Override which fields to enrich at each level     - Per-node input mappings: Customize retriever inputs per hierarchy level     - Labels/summaries: Human-readable metadata for UI display  Related Models:     - HierarchicalTaxonomyConfig: Contains list of hierarchical nodes     - TaxonomyAssignment: Result of matching documents to nodes     - EnrichmentField: Specifies which fields to enrich from node  Requirements:     - collection_id: REQUIRED - must reference an existing collection     - parent_collection_id: REQUIRED for non-root nodes (None for root)     - All other fields: OPTIONAL with inheritance from taxonomy-level config
+ * @export
+ * @interface HierarchicalNodeInput
+ */
+export interface HierarchicalNodeInput {
+    /**
+     * REQUIRED. Collection ID representing this node in the hierarchy. Must reference an existing collection containing documents for this hierarchy level. Format: \'col_\' prefix followed by alphanumeric/underscore characters. Used to: Match documents against this level, identify node in path, store enrichment data. Example: \'col_executives\' for executive level, \'col_products_phones\' for phones category.
+     * @type {string}
+     * @memberof HierarchicalNodeInput
+     */
+    'collection_id': string;
+    /**
+     * OPTIONAL. Collection ID of the parent node in the hierarchy. When None: This is a root node (top of hierarchy). When set: References parent node\'s collection_id, creating parent-child relationship. Format: Same as collection_id (\'col_\' prefix). Used to: Build hierarchy tree, determine inheritance order, construct path arrays. Example: \'col_managers\' is parent of \'col_executives\', \'col_products\' is parent of \'col_electronics\'. Validation: Must reference a valid collection_id from another node in same taxonomy.
+     * @type {string}
+     * @memberof HierarchicalNodeInput
+     */
+    'parent_collection_id'?: string;
+    /**
+     * OPTIONAL. Human-readable display name for this hierarchy node. Used in UI, visualizations, and taxonomy assignment results. NOT REQUIRED - When None: collection name or auto-generated label may be used. Format: Free text, typically title case, 2-50 characters. Examples: \'Executive Leadership\', \'Mobile Phones\', \'Engineering Team\'. Can be LLM-generated or manually specified during taxonomy creation.
+     * @type {string}
+     * @memberof HierarchicalNodeInput
+     */
+    'label'?: string;
+    /**
+     * OPTIONAL. Brief description of this hierarchy level and its contents. Used for: Documentation, UI tooltips, understanding hierarchy structure. NOT REQUIRED - When None: no summary available for this node. Format: Free text, typically 1-3 sentences, up to 500 characters. Can be LLM-generated or manually provided.
+     * @type {string}
+     * @memberof HierarchicalNodeInput
+     */
+    'summary'?: string;
+    /**
+     * OPTIONAL. Keywords or tags describing this hierarchy level. Used for: Search, filtering, categorization, LLM understanding. NOT REQUIRED - When None: no keywords defined for this node. Format: List of strings, typically 3-10 keywords per node. Can be LLM-generated from collection contents or manually specified.
+     * @type {Array<string>}
+     * @memberof HierarchicalNodeInput
+     */
+    'keywords'?: Array<string>;
+    /**
+     * OPTIONAL. Retriever to use for matching documents at this hierarchy level. When None: Uses taxonomy-level retriever_id (inheritance from parent config). When set: Overrides taxonomy-level retriever for this specific node. Format: \'ret_\' prefix followed by alphanumeric characters. Use for: Specialized matching at certain levels (e.g., face recognition for employees, semantic search for products). Must reference an existing RetrieverModel.
+     * @type {string}
+     * @memberof HierarchicalNodeInput
+     */
+    'retriever_id'?: string;
+    /**
+     * OPTIONAL. Fields to enrich into documents when they match this hierarchy level. Specifies which properties from node collection to copy to matched documents. When None: No field-level enrichment (only taxonomy assignment recorded). Format: List of EnrichmentField objects with field_path and merge_mode. Inheritance: Child nodes inherit all parent enrichment_fields plus their own. Example: executives node adds \'executive_level\' on top of inherited \'employee_id\', \'department\'.
+     * @type {Array<EnrichmentField>}
+     * @memberof HierarchicalNodeInput
+     */
+    'enrichment_fields'?: Array<EnrichmentField>;
+    /**
+     * OPTIONAL. Custom input mappings for the retriever at this hierarchy level. Specifies how to construct retriever inputs from document features. When None: Uses taxonomy-level input_mappings (inheritance). When set: Overrides taxonomy-level mappings for this specific node. Format: List of InputMapping objects specifying input_key, source_type, path. Use for: Different matching strategies at different levels (e.g., face at employee level, text at department level).
+     * @type {Array<InputMapping>}
+     * @memberof HierarchicalNodeInput
+     */
+    'input_mappings'?: Array<InputMapping>;
+}
+//# sourceMappingURL=hierarchical-node-input.d.ts.map

package/dist/models/hierarchical-node-input.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"hierarchical-node-input.d.ts","sourceRoot":"","sources":["../../models/hierarchical-node-input.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAKH,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,oBAAoB,CAAC;AAG1D,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,iBAAiB,CAAC;AAEpD;;;;GAIG;AACH,MAAM,WAAW,qBAAqB;IAClC;;;;OAIG;IACH,eAAe,EAAE,MAAM,CAAC;IACxB;;;;OAIG;IACH,sBAAsB,CAAC,EAAE,MAAM,CAAC;IAChC;;;;OAIG;IACH,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB;;;;OAIG;IACH,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB;;;;OAIG;IACH,UAAU,CAAC,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;IAC3B;;;;OAIG;IACH,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB;;;;OAIG;IACH,mBAAmB,CAAC,EAAE,KAAK,CAAC,eAAe,CAAC,CAAC;IAC7C;;;;OAIG;IACH,gBAAgB,CAAC,EAAE,KAAK,CAAC,YAAY,CAAC,CAAC;CAC1C"}

package/dist/models/hierarchical-node-output.d.ts

@@ -0,0 +1,69 @@
+/**
+ * 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 { EnrichmentField } from './enrichment-field';
+import type { InputMapping } from './input-mapping';
+/**
+ * A node in a hierarchical taxonomy representing one level in the tree structure.  Each node represents a collection containing documents at a specific hierarchy level. Nodes form parent-child relationships to create multi-level taxonomies with property inheritance. When a document matches a child node, it inherits all properties from parent nodes up to the root.  Use Cases:     - Define organizational hierarchies: employees → managers → executives     - Create product categorizations: products → electronics → phones → smartphones     - Build classification trees: industries → technology → software     - Implement face recognition hierarchies: people → employees → team members     - Enable property inheritance: child nodes get all parent properties  Hierarchy Behavior:     - Root nodes: parent_collection_id = None (top of hierarchy)     - Child nodes: parent_collection_id references parent node\'s collection_id     - Property inheritance: Children inherit all parent enrichment_fields     - Path construction: Creates path array from root to leaf     - Multi-level matching: Documents matched at deepest applicable level  Configuration:     - Per-node retrievers: Override taxonomy-level retriever for specific nodes     - Per-node enrichment: Override which fields to enrich at each level     - Per-node input mappings: Customize retriever inputs per hierarchy level     - Labels/summaries: Human-readable metadata for UI display  Related Models:     - HierarchicalTaxonomyConfig: Contains list of hierarchical nodes     - TaxonomyAssignment: Result of matching documents to nodes     - EnrichmentField: Specifies which fields to enrich from node  Requirements:     - collection_id: REQUIRED - must reference an existing collection     - parent_collection_id: REQUIRED for non-root nodes (None for root)     - All other fields: OPTIONAL with inheritance from taxonomy-level config
+ * @export
+ * @interface HierarchicalNodeOutput
+ */
+export interface HierarchicalNodeOutput {
+    /**
+     * REQUIRED. Collection ID representing this node in the hierarchy. Must reference an existing collection containing documents for this hierarchy level. Format: \'col_\' prefix followed by alphanumeric/underscore characters. Used to: Match documents against this level, identify node in path, store enrichment data. Example: \'col_executives\' for executive level, \'col_products_phones\' for phones category.
+     * @type {string}
+     * @memberof HierarchicalNodeOutput
+     */
+    'collection_id': string;
+    /**
+     * OPTIONAL. Collection ID of the parent node in the hierarchy. When None: This is a root node (top of hierarchy). When set: References parent node\'s collection_id, creating parent-child relationship. Format: Same as collection_id (\'col_\' prefix). Used to: Build hierarchy tree, determine inheritance order, construct path arrays. Example: \'col_managers\' is parent of \'col_executives\', \'col_products\' is parent of \'col_electronics\'. Validation: Must reference a valid collection_id from another node in same taxonomy.
+     * @type {string}
+     * @memberof HierarchicalNodeOutput
+     */
+    'parent_collection_id'?: string;
+    /**
+     * OPTIONAL. Human-readable display name for this hierarchy node. Used in UI, visualizations, and taxonomy assignment results. NOT REQUIRED - When None: collection name or auto-generated label may be used. Format: Free text, typically title case, 2-50 characters. Examples: \'Executive Leadership\', \'Mobile Phones\', \'Engineering Team\'. Can be LLM-generated or manually specified during taxonomy creation.
+     * @type {string}
+     * @memberof HierarchicalNodeOutput
+     */
+    'label'?: string;
+    /**
+     * OPTIONAL. Brief description of this hierarchy level and its contents. Used for: Documentation, UI tooltips, understanding hierarchy structure. NOT REQUIRED - When None: no summary available for this node. Format: Free text, typically 1-3 sentences, up to 500 characters. Can be LLM-generated or manually provided.
+     * @type {string}
+     * @memberof HierarchicalNodeOutput
+     */
+    'summary'?: string;
+    /**
+     * OPTIONAL. Keywords or tags describing this hierarchy level. Used for: Search, filtering, categorization, LLM understanding. NOT REQUIRED - When None: no keywords defined for this node. Format: List of strings, typically 3-10 keywords per node. Can be LLM-generated from collection contents or manually specified.
+     * @type {Array<string>}
+     * @memberof HierarchicalNodeOutput
+     */
+    'keywords'?: Array<string>;
+    /**
+     * OPTIONAL. Retriever to use for matching documents at this hierarchy level. When None: Uses taxonomy-level retriever_id (inheritance from parent config). When set: Overrides taxonomy-level retriever for this specific node. Format: \'ret_\' prefix followed by alphanumeric characters. Use for: Specialized matching at certain levels (e.g., face recognition for employees, semantic search for products). Must reference an existing RetrieverModel.
+     * @type {string}
+     * @memberof HierarchicalNodeOutput
+     */
+    'retriever_id'?: string;
+    /**
+     * OPTIONAL. Fields to enrich into documents when they match this hierarchy level. Specifies which properties from node collection to copy to matched documents. When None: No field-level enrichment (only taxonomy assignment recorded). Format: List of EnrichmentField objects with field_path and merge_mode. Inheritance: Child nodes inherit all parent enrichment_fields plus their own. Example: executives node adds \'executive_level\' on top of inherited \'employee_id\', \'department\'.
+     * @type {Array<EnrichmentField>}
+     * @memberof HierarchicalNodeOutput
+     */
+    'enrichment_fields'?: Array<EnrichmentField>;
+    /**
+     * OPTIONAL. Custom input mappings for the retriever at this hierarchy level. Specifies how to construct retriever inputs from document features. When None: Uses taxonomy-level input_mappings (inheritance). When set: Overrides taxonomy-level mappings for this specific node. Format: List of InputMapping objects specifying input_key, source_type, path. Use for: Different matching strategies at different levels (e.g., face at employee level, text at department level).
+     * @type {Array<InputMapping>}
+     * @memberof HierarchicalNodeOutput
+     */
+    'input_mappings'?: Array<InputMapping>;
+}
+//# sourceMappingURL=hierarchical-node-output.d.ts.map

package/dist/models/hierarchical-node-output.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"hierarchical-node-output.d.ts","sourceRoot":"","sources":["../../models/hierarchical-node-output.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAKH,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,oBAAoB,CAAC;AAG1D,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,iBAAiB,CAAC;AAEpD;;;;GAIG;AACH,MAAM,WAAW,sBAAsB;IACnC;;;;OAIG;IACH,eAAe,EAAE,MAAM,CAAC;IACxB;;;;OAIG;IACH,sBAAsB,CAAC,EAAE,MAAM,CAAC;IAChC;;;;OAIG;IACH,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB;;;;OAIG;IACH,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB;;;;OAIG;IACH,UAAU,CAAC,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;IAC3B;;;;OAIG;IACH,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB;;;;OAIG;IACH,mBAAmB,CAAC,EAAE,KAAK,CAAC,eAAe,CAAC,CAAC;IAC7C;;;;OAIG;IACH,gBAAgB,CAAC,EAAE,KAAK,CAAC,YAAY,CAAC,CAAC;CAC1C"}

package/dist/models/hierarchical-taxonomy-config-input.d.ts

@@ -0,0 +1,109 @@
+/**
+ * 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 { HierarchicalNodeInput } from './hierarchical-node-input';
+import type { HierarchyInferenceStrategy } from './hierarchy-inference-strategy';
+import type { InputMapping } from './input-mapping';
+import type { StepAnalyticsConfigInput } from './step-analytics-config-input';
+/**
+ * Hybrid hierarchical taxonomy configuration supporting inference with manual additions.  All hierarchical taxonomies are hybrid: - Base hierarchy can be inferred via schema, clustering, or LLM - Additional collections can be explicitly added with specific retrievers - Supports mixing inference strategies with manual additions/overrides  Examples: 1. Pure inference: Set inference_strategy + inference_collections 2. Pure manual: Set hierarchical_nodes only 3. Hybrid: Set inference_strategy + inference_collections + hierarchical_nodes    (infers base from collections, adds/overrides with explicit nodes)
+ * @export
+ * @interface HierarchicalTaxonomyConfigInput
+ */
+export interface HierarchicalTaxonomyConfigInput {
+    /**
+     * Discriminator identifying this as a hierarchical taxonomy.
+     * @type {string}
+     * @memberof HierarchicalTaxonomyConfigInput
+     */
+    'taxonomy_type'?: HierarchicalTaxonomyConfigInputTaxonomyTypeEnum;
+    /**
+     * Default retriever to use for all nodes unless overridden per-node.
+     * @type {string}
+     * @memberof HierarchicalTaxonomyConfigInput
+     */
+    'retriever_id'?: string;
+    /**
+     * Default input mappings for all nodes unless overridden per-node.
+     * @type {Array<InputMapping>}
+     * @memberof HierarchicalTaxonomyConfigInput
+     */
+    'input_mappings'?: Array<InputMapping>;
+    /**
+     * Strategy for inferring hierarchy structure from collections. Can be \'schema\' (overlap-based), \'cluster\' (clustering-based), or \'llm\' (AI-based). When set, will infer relationships from inference_collections.
+     * @type {HierarchyInferenceStrategy}
+     * @memberof HierarchicalTaxonomyConfigInput
+     */
+    'inference_strategy'?: HierarchyInferenceStrategy;
+    /**
+     * Collection IDs to use for hierarchy inference. The inference_strategy will analyze these collections to discover relationships. Can be combined with hierarchical_nodes for hybrid configuration.
+     * @type {Array<string>}
+     * @memberof HierarchicalTaxonomyConfigInput
+     */
+    'inference_collections'?: Array<string>;
+    /**
+     * LLM provider to use for hierarchy inference (default openai_chat_v1)
+     * @type {string}
+     * @memberof HierarchicalTaxonomyConfigInput
+     */
+    'llm_provider'?: HierarchicalTaxonomyConfigInputLlmProviderEnum;
+    /**
+     * LLM model name (e.g., gpt-4o-mini)
+     * @type {string}
+     * @memberof HierarchicalTaxonomyConfigInput
+     */
+    'llm_model'?: string;
+    /**
+     * Optional prompt template. Variables available: {collection_id}, {collection_name}.
+     * @type {string}
+     * @memberof HierarchicalTaxonomyConfigInput
+     */
+    'llm_prompt_template'?: string;
+    /**
+     * Optional number of sample docs to include in prompts (0 = disabled).
+     * @type {number}
+     * @memberof HierarchicalTaxonomyConfigInput
+     */
+    'llm_sample_size'?: number;
+    /**
+     * Cluster IDs to use for CLUSTER inference strategy
+     * @type {Array<string>}
+     * @memberof HierarchicalTaxonomyConfigInput
+     */
+    'cluster_ids'?: Array<string>;
+    /**
+     * Minimum overlap ratio to establish parent-child relationship between clusters
+     * @type {number}
+     * @memberof HierarchicalTaxonomyConfigInput
+     */
+    'cluster_overlap_threshold'?: number;
+    /**
+     * Explicit node definitions that either: 1) Define the entire hierarchy (when inference_strategy is None), 2) Add additional nodes to an inferred hierarchy, or 3) Override specific relationships in an inferred hierarchy. Supports true hybrid: infer from some collections, manually add others.
+     * @type {Array<HierarchicalNodeInput>}
+     * @memberof HierarchicalTaxonomyConfigInput
+     */
+    'hierarchical_nodes'?: Array<HierarchicalNodeInput>;
+    /**
+     * Optional configuration for step transition analytics. Enables tracking how documents progress through hierarchical taxonomy nodes over time (e.g., content workflow tracking from \'draft\' to \'published\'). If not provided, only basic assignment events are logged.
+     * @type {StepAnalyticsConfigInput}
+     * @memberof HierarchicalTaxonomyConfigInput
+     */
+    'step_analytics'?: StepAnalyticsConfigInput;
+}
+export declare const HierarchicalTaxonomyConfigInputTaxonomyTypeEnum: {
+    readonly Hierarchical: "hierarchical";
+};
+export type HierarchicalTaxonomyConfigInputTaxonomyTypeEnum = typeof HierarchicalTaxonomyConfigInputTaxonomyTypeEnum[keyof typeof HierarchicalTaxonomyConfigInputTaxonomyTypeEnum];
+export declare const HierarchicalTaxonomyConfigInputLlmProviderEnum: {
+    readonly OpenaiChatV1: "openai_chat_v1";
+};
+export type HierarchicalTaxonomyConfigInputLlmProviderEnum = typeof HierarchicalTaxonomyConfigInputLlmProviderEnum[keyof typeof HierarchicalTaxonomyConfigInputLlmProviderEnum];
+//# sourceMappingURL=hierarchical-taxonomy-config-input.d.ts.map

package/dist/models/hierarchical-taxonomy-config-input.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"hierarchical-taxonomy-config-input.d.ts","sourceRoot":"","sources":["../../models/hierarchical-taxonomy-config-input.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAKH,OAAO,KAAK,EAAE,qBAAqB,EAAE,MAAM,2BAA2B,CAAC;AAGvE,OAAO,KAAK,EAAE,0BAA0B,EAAE,MAAM,gCAAgC,CAAC;AAGjF,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,iBAAiB,CAAC;AAGpD,OAAO,KAAK,EAAE,wBAAwB,EAAE,MAAM,+BAA+B,CAAC;AAE9E;;;;GAIG;AACH,MAAM,WAAW,+BAA+B;IAC5C;;;;OAIG;IACH,eAAe,CAAC,EAAE,+CAA+C,CAAC;IAClE;;;;OAIG;IACH,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB;;;;OAIG;IACH,gBAAgB,CAAC,EAAE,KAAK,CAAC,YAAY,CAAC,CAAC;IACvC;;;;OAIG;IACH,oBAAoB,CAAC,EAAE,0BAA0B,CAAC;IAClD;;;;OAIG;IACH,uBAAuB,CAAC,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;IACxC;;;;OAIG;IACH,cAAc,CAAC,EAAE,8CAA8C,CAAC;IAChE;;;;OAIG;IACH,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB;;;;OAIG;IACH,qBAAqB,CAAC,EAAE,MAAM,CAAC;IAC/B;;;;OAIG;IACH,iBAAiB,CAAC,EAAE,MAAM,CAAC;IAC3B;;;;OAIG;IACH,aAAa,CAAC,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;IAC9B;;;;OAIG;IACH,2BAA2B,CAAC,EAAE,MAAM,CAAC;IACrC;;;;OAIG;IACH,oBAAoB,CAAC,EAAE,KAAK,CAAC,qBAAqB,CAAC,CAAC;IACpD;;;;OAIG;IACH,gBAAgB,CAAC,EAAE,wBAAwB,CAAC;CAC/C;AAED,eAAO,MAAM,+CAA+C;;CAElD,CAAC;AAEX,MAAM,MAAM,+CAA+C,GAAG,OAAO,+CAA+C,CAAC,MAAM,OAAO,+CAA+C,CAAC,CAAC;AACnL,eAAO,MAAM,8CAA8C;;CAEjD,CAAC;AAEX,MAAM,MAAM,8CAA8C,GAAG,OAAO,8CAA8C,CAAC,MAAM,OAAO,8CAA8C,CAAC,CAAC"}

package/dist/models/hierarchical-taxonomy-config-output.d.ts

@@ -0,0 +1,109 @@
+/**
+ * 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 { HierarchicalNodeOutput } from './hierarchical-node-output';
+import type { HierarchyInferenceStrategy } from './hierarchy-inference-strategy';
+import type { InputMapping } from './input-mapping';
+import type { StepAnalyticsConfigOutput } from './step-analytics-config-output';
+/**
+ * Hybrid hierarchical taxonomy configuration supporting inference with manual additions.  All hierarchical taxonomies are hybrid: - Base hierarchy can be inferred via schema, clustering, or LLM - Additional collections can be explicitly added with specific retrievers - Supports mixing inference strategies with manual additions/overrides  Examples: 1. Pure inference: Set inference_strategy + inference_collections 2. Pure manual: Set hierarchical_nodes only 3. Hybrid: Set inference_strategy + inference_collections + hierarchical_nodes    (infers base from collections, adds/overrides with explicit nodes)
+ * @export
+ * @interface HierarchicalTaxonomyConfigOutput
+ */
+export interface HierarchicalTaxonomyConfigOutput {
+    /**
+     * Discriminator identifying this as a hierarchical taxonomy.
+     * @type {string}
+     * @memberof HierarchicalTaxonomyConfigOutput
+     */
+    'taxonomy_type'?: HierarchicalTaxonomyConfigOutputTaxonomyTypeEnum;
+    /**
+     * Default retriever to use for all nodes unless overridden per-node.
+     * @type {string}
+     * @memberof HierarchicalTaxonomyConfigOutput
+     */
+    'retriever_id'?: string;
+    /**
+     * Default input mappings for all nodes unless overridden per-node.
+     * @type {Array<InputMapping>}
+     * @memberof HierarchicalTaxonomyConfigOutput
+     */
+    'input_mappings'?: Array<InputMapping>;
+    /**
+     * Strategy for inferring hierarchy structure from collections. Can be \'schema\' (overlap-based), \'cluster\' (clustering-based), or \'llm\' (AI-based). When set, will infer relationships from inference_collections.
+     * @type {HierarchyInferenceStrategy}
+     * @memberof HierarchicalTaxonomyConfigOutput
+     */
+    'inference_strategy'?: HierarchyInferenceStrategy;
+    /**
+     * Collection IDs to use for hierarchy inference. The inference_strategy will analyze these collections to discover relationships. Can be combined with hierarchical_nodes for hybrid configuration.
+     * @type {Array<string>}
+     * @memberof HierarchicalTaxonomyConfigOutput
+     */
+    'inference_collections'?: Array<string>;
+    /**
+     * LLM provider to use for hierarchy inference (default openai_chat_v1)
+     * @type {string}
+     * @memberof HierarchicalTaxonomyConfigOutput
+     */
+    'llm_provider'?: HierarchicalTaxonomyConfigOutputLlmProviderEnum;
+    /**
+     * LLM model name (e.g., gpt-4o-mini)
+     * @type {string}
+     * @memberof HierarchicalTaxonomyConfigOutput
+     */
+    'llm_model'?: string;
+    /**
+     * Optional prompt template. Variables available: {collection_id}, {collection_name}.
+     * @type {string}
+     * @memberof HierarchicalTaxonomyConfigOutput
+     */
+    'llm_prompt_template'?: string;
+    /**
+     * Optional number of sample docs to include in prompts (0 = disabled).
+     * @type {number}
+     * @memberof HierarchicalTaxonomyConfigOutput
+     */
+    'llm_sample_size'?: number;
+    /**
+     * Cluster IDs to use for CLUSTER inference strategy
+     * @type {Array<string>}
+     * @memberof HierarchicalTaxonomyConfigOutput
+     */
+    'cluster_ids'?: Array<string>;
+    /**
+     * Minimum overlap ratio to establish parent-child relationship between clusters
+     * @type {number}
+     * @memberof HierarchicalTaxonomyConfigOutput
+     */
+    'cluster_overlap_threshold'?: number;
+    /**
+     * Explicit node definitions that either: 1) Define the entire hierarchy (when inference_strategy is None), 2) Add additional nodes to an inferred hierarchy, or 3) Override specific relationships in an inferred hierarchy. Supports true hybrid: infer from some collections, manually add others.
+     * @type {Array<HierarchicalNodeOutput>}
+     * @memberof HierarchicalTaxonomyConfigOutput
+     */
+    'hierarchical_nodes'?: Array<HierarchicalNodeOutput>;
+    /**
+     * Optional configuration for step transition analytics. Enables tracking how documents progress through hierarchical taxonomy nodes over time (e.g., content workflow tracking from \'draft\' to \'published\'). If not provided, only basic assignment events are logged.
+     * @type {StepAnalyticsConfigOutput}
+     * @memberof HierarchicalTaxonomyConfigOutput
+     */
+    'step_analytics'?: StepAnalyticsConfigOutput;
+}
+export declare const HierarchicalTaxonomyConfigOutputTaxonomyTypeEnum: {
+    readonly Hierarchical: "hierarchical";
+};
+export type HierarchicalTaxonomyConfigOutputTaxonomyTypeEnum = typeof HierarchicalTaxonomyConfigOutputTaxonomyTypeEnum[keyof typeof HierarchicalTaxonomyConfigOutputTaxonomyTypeEnum];
+export declare const HierarchicalTaxonomyConfigOutputLlmProviderEnum: {
+    readonly OpenaiChatV1: "openai_chat_v1";
+};
+export type HierarchicalTaxonomyConfigOutputLlmProviderEnum = typeof HierarchicalTaxonomyConfigOutputLlmProviderEnum[keyof typeof HierarchicalTaxonomyConfigOutputLlmProviderEnum];
+//# sourceMappingURL=hierarchical-taxonomy-config-output.d.ts.map

package/dist/models/hierarchical-taxonomy-config-output.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"hierarchical-taxonomy-config-output.d.ts","sourceRoot":"","sources":["../../models/hierarchical-taxonomy-config-output.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAKH,OAAO,KAAK,EAAE,sBAAsB,EAAE,MAAM,4BAA4B,CAAC;AAGzE,OAAO,KAAK,EAAE,0BAA0B,EAAE,MAAM,gCAAgC,CAAC;AAGjF,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,iBAAiB,CAAC;AAGpD,OAAO,KAAK,EAAE,yBAAyB,EAAE,MAAM,gCAAgC,CAAC;AAEhF;;;;GAIG;AACH,MAAM,WAAW,gCAAgC;IAC7C;;;;OAIG;IACH,eAAe,CAAC,EAAE,gDAAgD,CAAC;IACnE;;;;OAIG;IACH,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB;;;;OAIG;IACH,gBAAgB,CAAC,EAAE,KAAK,CAAC,YAAY,CAAC,CAAC;IACvC;;;;OAIG;IACH,oBAAoB,CAAC,EAAE,0BAA0B,CAAC;IAClD;;;;OAIG;IACH,uBAAuB,CAAC,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;IACxC;;;;OAIG;IACH,cAAc,CAAC,EAAE,+CAA+C,CAAC;IACjE;;;;OAIG;IACH,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB;;;;OAIG;IACH,qBAAqB,CAAC,EAAE,MAAM,CAAC;IAC/B;;;;OAIG;IACH,iBAAiB,CAAC,EAAE,MAAM,CAAC;IAC3B;;;;OAIG;IACH,aAAa,CAAC,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;IAC9B;;;;OAIG;IACH,2BAA2B,CAAC,EAAE,MAAM,CAAC;IACrC;;;;OAIG;IACH,oBAAoB,CAAC,EAAE,KAAK,CAAC,sBAAsB,CAAC,CAAC;IACrD;;;;OAIG;IACH,gBAAgB,CAAC,EAAE,yBAAyB,CAAC;CAChD;AAED,eAAO,MAAM,gDAAgD;;CAEnD,CAAC;AAEX,MAAM,MAAM,gDAAgD,GAAG,OAAO,gDAAgD,CAAC,MAAM,OAAO,gDAAgD,CAAC,CAAC;AACtL,eAAO,MAAM,+CAA+C;;CAElD,CAAC;AAEX,MAAM,MAAM,+CAA+C,GAAG,OAAO,+CAA+C,CAAC,MAAM,OAAO,+CAA+C,CAAC,CAAC"}

package/dist/models/hierarchy-inference-strategy.d.ts

@@ -0,0 +1,23 @@
+/**
+ * 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.
+ */
+/**
+ * Strategy for inferring the base hierarchy structure.  Can be combined with manual overrides via hierarchical_nodes for hybrid configuration: - SCHEMA: Infer based on overlapping collection schemas - CLUSTER: Infer based on clustering algorithms and overlap detection - LLM: Infer using AI/language models
+ * @export
+ * @enum {string}
+ */
+export declare const HierarchyInferenceStrategy: {
+    readonly Schema: "schema";
+    readonly Cluster: "cluster";
+    readonly Llm: "llm";
+};
+export type HierarchyInferenceStrategy = typeof HierarchyInferenceStrategy[keyof typeof HierarchyInferenceStrategy];
+//# sourceMappingURL=hierarchy-inference-strategy.d.ts.map

package/dist/models/hierarchy-inference-strategy.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"hierarchy-inference-strategy.d.ts","sourceRoot":"","sources":["../../models/hierarchy-inference-strategy.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAIH;;;;GAIG;AAEH,eAAO,MAAM,0BAA0B;;;;CAI7B,CAAC;AAEX,MAAM,MAAM,0BAA0B,GAAG,OAAO,0BAA0B,CAAC,MAAM,OAAO,0BAA0B,CAAC,CAAC"}