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.
Studio is the visual interface for the multimodal data warehouse, where you manage namespaces, collections, retrievers, and storage tiers.
Use the Studio to manage your organization
- Set active namespace: Use the top bar namespace switcher. All actions scope to this selection. Namespaces mirror API behavior for
X-Namespace. Create one in Studio or via Create Namespace. - Create buckets: Define schemas to validate your objects. Buckets are the entry point for raw data. See Create Bucket and Create Object.
- Create collections: Point to a source and choose feature extractors. Collections produce searchable documents and vectors. See Create Collection and Describe Features.
- Ingest data: Upload objects to buckets, optionally in batches. Processing runs in the Engine and writes documents to your namespace.
- Explore results: Use
Explorerto search, filter, and preview documents with presigned URLs. - Build retrievers: Configure stages, test inputs, and save pipelines to power your apps. See Create Retriever and Execute Retriever.
- Enrich with taxonomies: Attach flat or hierarchical taxonomies on-demand or materialized. See Create Taxonomy and Test Taxonomy.
- Discover with clusters: Run clustering jobs and apply enrichment back to collections. See Create Cluster and Execute Clustering.
Tips
- Auth is automatic in Studio: Your API key and
X-Namespaceheader are handled for you. When calling APIs directly, include both. - Rate limits and health: Check
Operationsfor service health and limits. API reference: Healthcheck and Limits.
Set active namespace
Use the top bar switcher. This scopes all actions and mirrors the
X-Namespace header.Create collections
Choose feature extractors and index configs; this produces searchable documents and vectors.
Ingest and process
Upload objects or submit batches; the Engine writes vectors and payloads to MVS.
Studio follows Mintlify component patterns for clarity and scannability; see the Mintlify starter for examples.

