List Available Feature Extractors
Discover all available feature extractors with their capabilities, supported modalities, output features, and example usage. Use this to understand what extractors are available when configuring namespaces and collections in manifests.
Documentation Index
Fetch the complete documentation index at: https://docs.mixpeek.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Response
Successful Response
Feature extractor name (e.g., 'multimodal_extractor')
Feature extractor version (e.g., 'v1')
Human-readable description of what this extractor does
List of supported input modalities (text, image, video, audio)
List of features produced by this extractor
JSON Schema for extractor inputs — what fields the extractor reads from source objects
JSON Schema for tunable parameters (defaults, ranges, descriptions for every knob)
JSON Schema for output documents — what fields appear in extracted documents
Credit cost information (tier, per-unit rates)
What input types this extractor can handle: 'type_specific' (only one type, e.g. video-only) or 'multimodal' (handles multiple types with conditional processing). Type-specific extractors cannot use automatic-typed bucket properties.
For type-specific extractors: maps input keys to required types (e.g., {'video': 'video', 'thumbnail': 'image'}). For multimodal extractors: null.
Kind of real-time inference this extractor provides: 'embedding', 'rerank', 'classify', 'generate', or 'general'. Determines which retriever stages are compatible. Null if the extractor is batch-only.
Accepted input types (e.g., ['video', 'image'])
Maximum number of inputs per type (e.g., {'video': 1})
Default parameter values — use as a starting point for tuning
Vector indexes produced by this extractor (name, dimensions, distance metric, feature_uri)
Fields that uniquely identify each output document within a source object
What this extractor can do: 'batch' (feature extraction during ingestion), 'realtime' (query-time inference for retriever stages)
Minimal working configuration for namespace + collection + input_mappings + parameters

