Skip to content

Tiers

LlamaParse offers four different tiers designed to meet various parsing needs, balancing cost and accuracy.

Tiers in LlamaParse v2 are versioned to ensure consistent and predictable behavior. When you specify a tier with a specific version like "agentic" with version="2025-11-18", the parsing behavior will never change - you’ll always get the same model, prompts, and configuration.

This versioning system allows us to introduce new models, update prompts, and add new options in newer versions without breaking existing integrations or changing behavior for previous versions.

Unlike LlamaParse v1, specifying a tier is mandatory when parsing files in v2. You must include both the tier and version parameters in your parsing request.

Use "version": "latest" to always get the most recent version. For production use, we recommend using specific version dates (e.g., "2026-01-08", "2025-12-31", "2025-12-18", "2025-12-11") to ensure consistent results.

The following tier configurations should be included at the root level of your API request. For complete API request examples, see the Getting Started guide.

The most advanced tier with state-of-the-art models for maximum accuracy.

{
"tier": "agentic_plus",
"version": "latest"
}

With explicit version for reproducibility:

{
"tier": "agentic_plus",
"version": "2026-01-08"
}

Advanced parsing with intelligent agents for complex documents.

{
"tier": "agentic",
"version": "latest"
}

Balanced performance and cost using efficient models.

{
"tier": "cost_effective",
"version": "latest"
}

The fastest tier with basic parsing capabilities.

{
"tier": "fast",
"version": "latest"
}

Here’s a complete example of how to use a tier in an API request:

Terminal window
curl -X 'POST' \
'https://api.cloud.llamaindex.ai/api/v2/parse' \
-H 'Accept: application/json' \
-H 'Content-Type: application/json' \
-H "Authorization: Bearer $LLAMA_CLOUD_API_KEY" \
--data '{
"file_id": "<file_id>",
"tier": "agentic_plus",
"version": "latest"
}'