NEWVectors or files. Pick a path.Start →
    Back to Glossary

    What is Feature URI

    Feature URI - A universal address for any feature emitted by a Mixpeek extractor, enabling query-time model compatibility across the warehouse.

    URI Format

    • mixpeek://{extractor_name}@{version}/{output_name}
    • extractor_name: the feature extractor that produced the output (e.g., text_extractor, clip_vit_l_14, face_identity_extractor)
    • version: the extractor version (e.g., v1, v2), which guarantees embedding compatibility
    • output_name: the specific output of the extractor (e.g., text_embedding, image_embedding, face_embedding)

    Examples

    • mixpeek://text_extractor@v1/text_embedding - 1024D E5 text embedding
    • mixpeek://clip_vit_l_14@v1/image_embedding - 768D CLIP image embedding
    • mixpeek://video_extractor@v1/scene_embeddings - scene-level multimodal embedding
    • mixpeek://face_identity_extractor@v1/face_embedding - 512D ArcFace identity vector
    • mixpeek://audio_fingerprint_extractor@v1/fingerprint - audio fingerprint feature

    Where Feature URIs Are Used

    • Collection output schemas: define which features a collection produces
    • Retriever stages: the feature_address field in feature_search stages specifies which embedding to query
    • Taxonomies: reference which feature to classify against
    • Clustering jobs: specify the embedding space for vector grouping
    • Caching: inference cache uses URIs to shortcut repeated embedding requests

    Why Feature URIs Matter

    • Model compatibility: prevents querying a CLIP embedding with an E5 query vector
    • Version safety: upgrading an extractor version creates new URIs, so old and new embeddings coexist
    • Lineage tracking: every feature in the warehouse can be traced back to its source extractor and version
    • Cross-collection queries: retrievers can reference features from multiple collections in the same pipeline

    Related Pages

    • Core Concepts - Feature URIs: /docs/overview/concepts
    • Feature Extractors: /docs/processing/feature-extractors
    • Retriever Stages - Feature Search: /docs/retrieval/stages/feature-search
    • Warehouse Architecture: /docs/overview/warehouse-architecture
    Managed Mixpeek

    Put multimodal search to work

    Connect a bucket and Mixpeek runs the whole multimodal search pipeline for you: extraction, indexing, and search over your own objects. No models to wire up, nothing to host.

    Start with Managed
    MVS · bring your own

    Already have vectors?

    Keep your embeddings on your own cloud and run dense, sparse, and BM25 search directly on object storage. First 1M vectors free.

    Start with MVS
    Building an agent? Connect Mixpeek over MCP

    Related Terms

    ACIDAPIBlob StorageCLIPEmbedding