Stage Category: ENRICH (Enriches documents)Transformation: N documents → N documents (with agent-produced classification added)
When to Use
When NOT to Use
Parameters
Available Tools
The agent has access to three tools, auto-enabled based on configuration:Configuration Examples
How It Works
For each document, the stage runs a multi-turn agent loop:- Initialize: Agent receives the document content + system prompt + available tools
- Reason: Agent analyzes the document and optionally calls tools (taxonomy lookup, example search, content analysis)
- Observe: Tool results are fed back to the agent as context
- Iterate: Loop continues until the agent produces a final answer (or
max_turns/timeout_secondsis reached) - Output: The agent’s structured JSON response is merged into the document at
output_field
Output Examples
With Taxonomy + Examples
Simple Classification
Conditional Skip (When Condition)
when condition are passed through unchanged.
Performance
Common Pipeline Patterns
Search + Agentic Classify + Filter
Multimodal Analysis Pipeline
Bring Your Own Key (BYOK)
Use your own LLM API keys instead of Mixpeek’s default keys for both the reasoning agent and the analysis provider.1
Store your API keys as secrets
2
Reference secrets in your stage config
When
api_key is not specified, the stage uses Mixpeek’s default API keys and usage is charged to your Mixpeek account.Stage Metadata
The stage returns execution metadata for observability:Error Handling
Cost Considerations
Related
- LLM Enrich — Single-shot LLM enrichment (faster, cheaper)
- Taxonomy Enrich — Vector-based taxonomy matching (no LLM cost)
- Agent Search — Multi-turn agent for search (different use case)

