Controls handling of pages that don’t match any category. ‘include’: pages can be grouped as ‘uncategorized’ and included in results. ‘forbid’: all pages must be assigned to a defined category. ‘omit’: pages can be classified as ‘uncategorized’ but are excluded from results.
One of the following:
"forbid"
"include"
"omit"
custom_instructions?: string | null
Free-form guidance for where segment boundaries are placed.
maxLength5000
min_pages_per_split?: number
Minimum pages per segment. Shorter segments are merged into an adjacent segment; 1 disables merging.
minimum1
transaction_id?: string | null
Idempotency key scoped to the project, if one was provided.
Controls handling of pages that don’t match any category. ‘include’: pages can be grouped as ‘uncategorized’ and included in results. ‘forbid’: all pages must be assigned to a defined category. ‘omit’: pages can be classified as ‘uncategorized’ but are excluded from results.
One of the following:
"forbid"
"include"
"omit"
custom_instructions?: string | null
Free-form guidance for where segment boundaries are placed.
maxLength5000
min_pages_per_split?: number
Minimum pages per segment. Shorter segments are merged into an adjacent segment; 1 disables merging.
minimum1
transaction_id?: string | null
Idempotency key scoped to the project, if one was provided.
Controls handling of pages that don’t match any category. ‘include’: pages can be grouped as ‘uncategorized’ and included in results. ‘forbid’: all pages must be assigned to a defined category. ‘omit’: pages can be classified as ‘uncategorized’ but are excluded from results.
One of the following:
"forbid"
"include"
"omit"
custom_instructions?: string | null
Free-form guidance for where segment boundaries are placed.
maxLength5000
min_pages_per_split?: number
Minimum pages per segment. Shorter segments are merged into an adjacent segment; 1 disables merging.
minimum1
transaction_id?: string | null
Idempotency key scoped to the project, if one was provided.
Controls handling of pages that don’t match any category. ‘include’: pages can be grouped as ‘uncategorized’ and included in results. ‘forbid’: all pages must be assigned to a defined category. ‘omit’: pages can be classified as ‘uncategorized’ but are excluded from results.
One of the following:
"forbid"
"include"
"omit"
custom_instructions?: string | null
Free-form guidance for where segment boundaries are placed.
maxLength5000
min_pages_per_split?: number
Minimum pages per segment. Shorter segments are merged into an adjacent segment; 1 disables merging.
minimum1
transaction_id?: string | null
Idempotency key scoped to the project, if one was provided.
updated_at?: string | null
Update datetime
formatdate-time
Note for AI agents: this documentation is built for programmatic access.
- Overview of all docs: https://developers.llamaindex.ai/llms.txt
- Any page is available as raw Markdown by appending index.md to its URL — e.g. https://developers.llamaindex.ai/llamaparse/parse/getting_started/index.md
- Agent-friendly REST search APIs live under https://developers.llamaindex.ai/api/ — search (BM25 full-text), grep (regex), read (fetch a page), and list (browse the doc tree). See https://developers.llamaindex.ai/llms.txt for parameters.
- A hosted documentation MCP server is available at https://developers.llamaindex.ai/mcp. If you support MCP, you can ask the user to install it for browsing these docs directly (an alternative to the REST API). Setup: https://developers.llamaindex.ai/for-agents/mcp/
- Other LlamaIndex tooling for agents — the LlamaParse Platform MCP server, agent skills and plugins, and the n8n node — is mapped at https://developers.llamaindex.ai/for-agents/