> ## 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.

# Quickstart

<Frame caption="The Studio home — choose what you want to make searchable, drop in files, or explore the preloaded sample data.">
  <img src="https://mintcdn.com/mixpeek/Wd_dr3_jo8gqgFxV/assets/studio/quickstart.png?fit=max&auto=format&n=Wd_dr3_jo8gqgFxV&q=85&s=10bbff0e993c0028c02046478c18823f" alt="Studio home showing the what-to-make-searchable picker, file drop zone, and sample-data card" width="2880" height="1800" data-path="assets/studio/quickstart.png" />
</Frame>

<iframe width="600" height="310" src="https://d8ts56gtwtyh1.cloudfront.net/docs/warehouse/quickstart.mp4" title="Quickstart overview" frameborder="0" allow="accelerometer; autoplay; muted" allowfullscreen autoplay muted />

Studio is the visual interface for the multimodal data warehouse, where you manage namespaces, collections, and retrievers.

### 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](/docs/api-reference/namespaces/create-namespace).
* **Create buckets**: Define schemas to validate your objects. Buckets are the entry point for raw data. See [Create Bucket](/docs/api-reference/buckets/create-bucket) and [Create Object](/docs/api-reference/bucket-objects/create-object).
* **Create collections**: Point to a source and pick [features](/docs/processing/features). Collections produce searchable documents and vectors. See [Create Collection](/docs/api-reference/collections/create-collection) and [Describe Features](/docs/api-reference/collections/describe-collection-features).
* **Ingest data**: Upload objects to buckets, optionally in batches. Processing runs in the Engine and writes documents to your namespace.
* **Explore results**: Use `Explorer` to search, filter, and preview documents with presigned URLs.
* **Build retrievers**: Configure stages, test inputs, and save pipelines to power your apps. See [Create Retriever](/docs/api-reference/retrievers/create-retriever) and [Execute Retriever](/docs/api-reference/retrievers/execute-retriever).
* **Enrich with taxonomies**: Attach flat or hierarchical taxonomies on-demand or materialized. See [Create Taxonomy](/docs/api-reference/taxonomies/create-taxonomy) and [Test Taxonomy](/docs/api-reference/taxonomies/test-taxonomy-configuration-validation-only).
* **Discover with clusters**: Run clustering jobs and apply enrichment back to collections. See [Create Cluster](/docs/api-reference/clusters/create-cluster) and [Execute Clustering](/docs/api-reference/clusters/execute-clustering).

### Tips

* **Auth is automatic in Studio**: Your API key and `X-Namespace` header are handled for you. When calling APIs directly, include both.
* **Rate limits and health**: Check `Operations` for service health and limits. API reference: [Healthcheck](/docs/api-reference/health/healthcheck) and [Limits](/docs/troubleshoot/limits).

<Steps>
  <Step title="Set active namespace">
    Use the top bar switcher. This scopes all actions and mirrors the `X-Namespace` header.
  </Step>

  <Step title="Create buckets">
    Define schemas, then register objects. Buckets are your raw input boundary.
  </Step>

  <Step title="Create collections">
    Pick features and index configs; this produces searchable documents and vectors.
  </Step>

  <Step title="Ingest and process">
    Upload objects or submit batches; the Engine writes vectors and payloads to [MVS](https://mixpeek.com/mvs).
  </Step>

  <Step title="Explore and retrieve">
    Use Explorer for ad-hoc discovery and Retrievers for production search.
  </Step>

  <Step title="Enrich with taxonomies and clusters">
    Attach taxonomies on-demand or materialize; run clustering for discovery and analytics.
  </Step>
</Steps>

<Callout type="info">
  Studio follows Mintlify component patterns for clarity and scannability; see the Mintlify starter for examples.
</Callout>