Files & Collections

Metadata Fields

Metadata fields allow you to attach structured attributes to documents in a collection. These fields enable:

• Filtered retrieval — Narrow search results to documents matching specific criteria (e.g., author="Sandra Kim")
• Contextual embeddings — Inject metadata into chunks to improve retrieval accuracy (e.g., prepending document title to each chunk)
• Data integrity constraints — Enforce required fields or uniqueness across documents

Creating a Collection with Metadata Fields

Define metadata fields using field_definitions when creating a collection:

curl -X POST "https://management-api.x.ai/v1/collections" \
  -H "Authorization: Bearer $XAI_MANAGEMENT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "collection_name": "research_papers",
    "field_definitions": [
      { "key": "author", "required": true },
      { "key": "year", "required": true, "unique": true },
      { "key": "title", "inject_into_chunk": true }
    ]
  }'

Field Definition Options

Uploading Documents with Metadata

Include metadata as a JSON object in the fields parameter:

curl -X POST "https://management-api.x.ai/v1/collections/{collection_id}/documents" \
  -H "Authorization: Bearer $XAI_MANAGEMENT_API_KEY" \
  -F "name=paper.pdf" \
  -F "[email protected]" \
  -F "content_type=application/pdf" \
  -F 'fields={"author": "Sandra Kim", "year": "2024", "title": "Q3 Revenue Analysis"}'

Filtering Documents in Search

Use the filter parameter to restrict search results based on metadata values. The filter uses AIP-160 syntax:

curl -X POST "https://api.x.ai/v1/documents/search" \
  -H "Authorization: Bearer $XAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "revenue growth",
    "source": { "collection_ids": ["collection_xxx"] },
    "filter": "author=\"Sandra Kim\" AND year>=2020"
  }'

Supported Filter Operators

[!NOTE]

AND has higher precedence than OR, so a="x" OR b="y" AND c="z" is evaluated as a="x" OR (b="y" AND c="z"). Use parentheses to make grouping explicit.

[!WARNING]

Wildcard matching (e.g., author="E*") is not supported. All string comparisons are exact matches.

[!WARNING]

Filtering on fields that don't exist in your documents returns no results. Double-check that field names match your collection's field_definitions.

AIP-160 Filter String Examples

Basic Examples

# Equality (double or single quotes for strings with spaces)
author="Sandra Kim"
author='Sandra Kim'

# Equality (no quotes needed for simple values)
year=2024
status=active

# Not equal
status!="archived"
status!='archived'

Comparison Operators

# Numeric comparisons
year>=2020
year>2019
score<=0.95
price<100

# Combined comparisons (range)
year>=2020 AND year<=2024

Logical Operators

# AND - both conditions must match
author="Sandra Kim" AND year=2024

# OR - either condition matches
status="pending" OR status="in_progress"

# Combined (OR has higher precedence than AND)
department="Engineering" AND status="active" OR status="pending"

# Use parentheses for clarity
department="Engineering" AND (status="active" OR status="pending")

Complex Examples

# Multiple conditions
author="Sandra Kim" AND year>=2020 AND status!="draft"

# Nested logic with parentheses
(author="Sandra Kim" OR author="John Doe") AND year>=2020

# Multiple fields with mixed operators
category="finance" AND (year=2023 OR year=2024) AND status!="archived"

Quick Reference