> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to LlamaParse

The LlamaParse connector lets your AI agent act in each user's LlamaParse account. Each user connects their own LlamaParse access token once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 22 tools.

**Authentication:** Bearer Token
**Categories:** AI, Files & Documents
**Tools:** 22: 12 read, 7 write, 3 destructive
**Users sign in with:** Access token
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=LLAMAPARSE)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the LlamaParse connection

   In **AgentKit > Connections**, create a LlamaParse connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'llamaparse'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize LlamaParse:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'llamaparse_classify_jobs_list',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "llamaparse"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize LlamaParse:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="llamaparse_classify_jobs_list",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their LlamaParse credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'llamaparse_classify_job_get',
  toolInput: {
    job_id: '<job_id>',
  },
  connector: 'llamaparse',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="llamaparse_classify_job_get",
    tool_input={
        "job_id": "<job_id>",
    },
    connection_name="llamaparse",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `llamaparse_classify_job_get`

Get Classify Job · Read-only

Get a classify job's status and, when finished, the chosen document type with its confidence and reasoning.
Returns id, status, error_message and the classification result.
Use this to poll a classification and read the result.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `job_id` (`string`, required): Classify job ID returned by llamaparse_classify_job_create or listed by llamaparse_classify_jobs_list. Example: clj-5b8e2f9c3a1d
- `expand` (`array`, optional): Extra fields to include: usage. Example: ["usage"]

Example input: `{"job_id":"<job_id>"}`

### `llamaparse_classify_jobs_list`

List Classify Jobs · Read-only

List classify jobs in the project, optionally filtered by status and creation time.
Returns items (each with id, status and created_at) and next_page_token.
Use this to find earlier classifications. Use llamaparse_classify_job_get for a result.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `created_at_on_or_after` (`string`, optional): Only jobs created at or after this time (ISO 8601). Example: 2026-11-01T00:00:00Z
- `created_at_on_or_before` (`string`, optional): Only jobs created at or before this time (ISO 8601). Example: 2026-11-15T23:59:59Z
- `page_size` (`integer`, optional): Jobs per page, 1 to 100. Example: 20
- `page_token` (`string`, optional): Token from next_page_token of the previous response, to get the next page. Example: eyJvZmZzZXQiOjIwfQ
- `status` (`string`, optional): Only return classify jobs in this status: PENDING, RUNNING, COMPLETED, FAILED, CANCELLED. Example: COMPLETED. One of: `PENDING`, `RUNNING`, `COMPLETED`, `FAILED`, `CANCELLED`.

Example input: `{}`

### `llamaparse_extract_job_get`

Get Extract Job · Read-only

Get an extract job's status and, when finished, the extracted data.
Returns id, status, error_message and extract_result (data matching the schema), plus any expanded fields.
Use this to poll an extraction and read the result.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `job_id` (`string`, required): Extract job ID returned by llamaparse_extract_job_create or listed by llamaparse_extract_jobs_list. Example: exj-7f2c9d1a4b6e
- `expand` (`array`, optional): Extra fields to include: configuration, extract_metadata (citations and confidence scores), usage. Example: ["extract_metadata"]

Example input: `{"job_id":"<job_id>"}`

### `llamaparse_extract_jobs_list`

List Extract Jobs · Read-only

List extract jobs in the project, optionally filtered by status, source document or creation time.
Returns items (each with id, status, file_input and created_at) and next_page_token.
Use this to find earlier extractions. Use llamaparse_extract_job_get for a job's result.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `created_at_on_or_after` (`string`, optional): Only jobs created at or after this time (ISO 8601). Example: 2026-11-01T00:00:00Z
- `created_at_on_or_before` (`string`, optional): Only jobs created at or before this time (ISO 8601). Example: 2026-11-15T23:59:59Z
- `file_input` (`string`, optional): Only jobs run on this parse job ID or file ID. Example: pjb-3k9x2m7q1v8c
- `page_size` (`integer`, optional): Jobs per page, 1 to 1000. Example: 20
- `page_token` (`string`, optional): Token from next_page_token of the previous response, to get the next page. Example: eyJvZmZzZXQiOjIwfQ
- `status` (`string`, optional): Only return extract jobs in this status: PENDING, THROTTLED, RUNNING, COMPLETED, FAILED, CANCELLED. Example: COMPLETED. One of: `PENDING`, `THROTTLED`, `RUNNING`, `COMPLETED`, `FAILED`, `CANCELLED`.

Example input: `{}`

### `llamaparse_extract_schema_validate`

Validate Extraction Schema · Read-only

Check whether a JSON Schema can be used for extraction.
Returns the validated (normalized) schema, or a 422 error describing what is wrong.
Use this before llamaparse_extract_job_create.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `data_schema` (`object`, required): JSON Schema to check for use with extract jobs. Example: {"type": "object", "properties": {"total": {"type": "number"}}}

Example input: `{"data_schema":{}}`

### `llamaparse_organizations_list`

List Organizations · Read-only

List the LlamaCloud organizations the API key's user belongs to.
Returns items with id, name and created_at, plus next_page_token.
Use this with llamaparse_projects_list to see account structure.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `name` (`string`, optional): Only organizations with this name. Example: Acme Corp
- `page_size` (`integer`, optional): Organizations per page. Example: 20
- `page_token` (`string`, optional): Token from next_page_token of the previous response. Example: eyJvZmZzZXQiOjIwfQ

Example input: `{}`

### `llamaparse_parse_job_get`

Get Parse Job · Read-only

Get a parse job's status and, with expand, its parsed output as markdown, text, structured items or metadata.
Returns job (id, status, error_message) plus the requested outputs, for example markdown.pages[].markdown.
Use this to poll a job and read the result. Use llamaparse_parse_jobs_list to find job IDs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `job_id` (`string`, required): Parse job ID returned by llamaparse_parse_job_create or listed by llamaparse_parse_jobs_list. Example: pjb-3k9x2m7q1v8c
- `expand` (`array`, optional): Output to include with the job: text, markdown, items, metadata, forms, job_metadata, usage, or one of the *_content_metadata fields (which carry presigned download URLs, for example images_content_metadata or xlsx_content_metadata). Without expand only the job status is returned. Example: ["markdown", "usage"]
- `image_filenames` (`string`, optional): Comma-separated image filenames to include when expanding images_content_metadata. Example: image_0.png,image_1.jpg

Example input: `{"job_id":"<job_id>"}`

### `llamaparse_parse_jobs_list`

List Parse Jobs · Read-only

List parse jobs in the project, newest first, optionally filtered by status and creation time.
Returns items (each with id, status, tier, created_at and the source) and next_page_token.
Use this to find an earlier job. Use llamaparse_parse_job_get for a job's output.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `created_at_on_or_after` (`string`, optional): Only jobs created at or after this time (ISO 8601). Example: 2026-11-01T00:00:00Z
- `created_at_on_or_before` (`string`, optional): Only jobs created at or before this time (ISO 8601). Example: 2026-11-15T23:59:59Z
- `page_size` (`integer`, optional): Jobs per page, 1 to 1000. Example: 20
- `page_token` (`string`, optional): Token from next_page_token of the previous response, to get the next page. Example: eyJvZmZzZXQiOjIwfQ
- `status` (`string`, optional): Only return parse jobs in this status: PENDING, RUNNING, COMPLETED, FAILED, CANCELLED. Example: COMPLETED. One of: `PENDING`, `RUNNING`, `COMPLETED`, `FAILED`, `CANCELLED`.

Example input: `{}`

### `llamaparse_parse_versions_list`

List Parse Versions · Read-only

List the available versions for each parse tier.
Returns each tier with its dated versions and which one latest points to.
Use this to pin a version in llamaparse_parse_job_create.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `llamaparse_project_get`

Get Project · Read-only

Get one LlamaCloud project.
Returns id, name, organization_id and timestamps.
Use llamaparse_projects_list to find the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`string`, required): Project ID (UUID) from llamaparse_projects_list. Example: 7a8b9c0d-1e2f-4a3b-8c4d-5e6f7a8b9c0d

Example input: `{"project_id":"<project_id>"}`

### `llamaparse_projects_list`

List Projects · Read-only

List the LlamaCloud projects the API key can access.
Returns items with id, name, organization_id and created_at, plus next_page_token.
Use this to see where jobs run. API keys are scoped to a project, so this usually returns one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `name` (`string`, optional): Only projects with this name. Example: Default
- `organization_id` (`string`, optional): Only projects in this organization. Example: 1d2c3b4a-5e6f-4a7b-8c9d-0e1f2a3b4c5d
- `page_size` (`integer`, optional): Projects per page. Example: 20
- `page_token` (`string`, optional): Token from next_page_token of the previous response. Example: eyJvZmZzZXQiOjIwfQ

Example input: `{}`

### `llamaparse_supported_extensions_list`

List Supported File Types · Read-only

List the file extensions LlamaParse can parse.
Returns an array of supported extensions with their content types.
Use this to check a document type before llamaparse_parse_job_create.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `llamaparse_classify_job_cancel`

Cancel Classify Job · Write

Cancel a pending or running classify job.
Returns the job with its updated status.
Use this to stop a classification you no longer need.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `job_id` (`string`, required): Classify job ID returned by llamaparse_classify_job_create or listed by llamaparse_classify_jobs_list. Example: clj-5b8e2f9c3a1d

Example input: `{"job_id":"<job_id>"}`

### `llamaparse_classify_job_create`

Classify Document · Write

Start a LlamaClassify job that labels a parsed document or file with one of the document types you describe, spending credits.
Returns the job with id and status. Poll llamaparse_classify_job_get until COMPLETED to read the chosen type and reasoning.
Use this to route documents by type. Use llamaparse_extract_job_create to pull fields out of them.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `file_input` (`string`, required): Parse job ID (from llamaparse_parse_job_create) or LlamaCloud file ID of the document to classify. To work from a URL, parse it first and pass the parse job ID. Example: pjb-3k9x2m7q1v8c
- `configuration_id` (`string`, optional): ID of a saved classify configuration to use instead of rules. Example: cfg-6d3a8b2e9f
- `rules` (`array`, optional): Document types to choose from, each with a type label (up to 50 characters) and a description (up to 2000) of what that type looks like. Required unless configuration_id is set. Example: [{"type": "invoice", "description": "A bill with line items, amounts and a total due"}, {"type": "contract", "description": "A legal agreement with parties, terms and signatures"}]
- `transaction_id` (`string`, optional): Idempotency key, up to 255 characters, unique in the project. Reusing it returns the original job. Example: classify-inbox-2026-11-15-001

Example input: `{"file_input":"<file_input>"}`

### `llamaparse_extract_job_cancel`

Cancel Extract Job · Write

Cancel a pending or running extract job.
Returns the job with its updated status.
Use this to stop an extraction you no longer need.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `job_id` (`string`, required): Extract job ID returned by llamaparse_extract_job_create or listed by llamaparse_extract_jobs_list. Example: exj-7f2c9d1a4b6e

Example input: `{"job_id":"<job_id>"}`

### `llamaparse_extract_job_create`

Extract Structured Data · Write

Start a LlamaExtract job that pulls structured data matching a JSON Schema out of a parsed document or file, spending credits.
Returns the job with id and status. Poll llamaparse_extract_job_get until COMPLETED to read extract_result.
Use this after llamaparse_parse_job_create to get fields such as totals, dates or names. Use llamaparse_classify_job_create to label the document type instead.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `file_input` (`string`, required): Parse job ID (from llamaparse_parse_job_create) or LlamaCloud file ID of the document to extract from. To work from a URL, parse it first and pass the parse job ID. Example: pjb-3k9x2m7q1v8c
- `cite_sources` (`boolean`, optional): If true, return citations for each value under extract_metadata. Example: true
- `confidence_scores` (`boolean`, optional): If true, return confidence scores under extract_metadata. Example: true
- `configuration_id` (`string`, optional): ID of a saved extract configuration to use instead of data_schema and the other settings. Example: cfg-8c1e4f7a2b
- `data_schema` (`object`, optional): JSON Schema of the fields to extract. Required unless configuration_id is set. Check it with llamaparse_extract_schema_validate or draft one with llamaparse_extract_schema_generate. Example: {"type": "object", "properties": {"invoice_number": {"type": "string"}, "total": {"type": "number"}}}
- `max_pages` (`integer`, optional): Maximum number of pages to process, starting from page 1. target_pages wins if both are set. Example: 10
- `system_prompt` (`string`, optional): Extra instructions that guide the extraction. Example: Amounts are in EUR; use the grand total including VAT.
- `target_pages` (`string`, optional): Pages to process, 1-based, as a comma-separated list of pages and ranges. Omit for all pages. Example: 1,3,5-8
- `tier` (`string`, optional): Extract tier: cost_effective (5 credits/page), agentic (15), agentic_plus (50) or turbo (35). Example: cost_effective. One of: `cost_effective`, `agentic`, `agentic_plus`, `turbo`.

Example input: `{"file_input":"<file_input>"}`

### `llamaparse_extract_schema_generate`

Generate Extraction Schema · Write

Draft an extraction JSON Schema from a plain-language description, a sample file or an existing schema.
Returns the generated configuration with its data_schema.
Use this before llamaparse_extract_job_create when you do not have a schema yet. Use llamaparse_extract_schema_validate to check a schema you wrote.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `data_schema` (`object`, optional): Existing schema to refine or extend. Example: {"type": "object", "properties": {"invoice_number": {"type": "string"}}}
- `file_id` (`string`, optional): LlamaCloud file ID of a sample document to base the schema on. Example: 4f6b2c1e-9a7d-4e3b-8c5f-1a2b3c4d5e6f
- `name` (`string`, optional): Name for the generated configuration, up to 255 characters. Auto-generated if empty. Example: Invoice fields
- `prompt` (`string`, optional): Plain-language description of the data to extract. Example: Invoice number, issue date, vendor name, line items with description and amount, and the total

Example input: `{}`

### `llamaparse_parse_job_cancel`

Cancel Parse Job · Write

Cancel a pending or running parse job.
Returns the job with its updated status.
Use this to stop a job you no longer need. Use llamaparse_parse_job_delete to remove a finished job.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `job_id` (`string`, required): Parse job ID returned by llamaparse_parse_job_create or listed by llamaparse_parse_jobs_list. Example: pjb-3k9x2m7q1v8c

Example input: `{"job_id":"<job_id>"}`

### `llamaparse_parse_job_create`

Parse Document from URL · Write

Start a LlamaParse job that downloads a document from a public URL and parses it into markdown, text and structured items, spending credits.
Returns the job with id and status. Parsing runs asynchronously; poll llamaparse_parse_job_get until status is COMPLETED and request the output with expand.
Use this first for any document. Use llamaparse_extract_job_create or llamaparse_classify_job_create on the resulting job ID for structured data or document types.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `source_url` (`string`, required): Public URL of the document to parse (PDF, Word, PowerPoint, spreadsheet, image, HTML and more; see llamaparse_supported_extensions_list). LlamaParse downloads it, so it must be reachable without login. Example: https://example.com/reports/annual-report-2025.pdf
- `tier` (`string`, required): Parsing tier: fast (rule-based, cheapest, text only), cost_effective (balanced), agentic (AI-powered, supports custom_prompt) or agentic_plus (highest accuracy). Pass configured with configuration_id to use the saved configuration's tier. Example: cost_effective. One of: `fast`, `cost_effective`, `agentic`, `agentic_plus`, `configured`.
- `configuration_id` (`string`, optional): ID of a saved parse configuration. Its settings apply, and tier and version default to the saved values (pass configured for both). Example: cfg-2a7d9e4b1c
- `custom_prompt` (`string`, optional): Instructions for the AI tiers (cost_effective, agentic, agentic_plus) on how to parse, for example how to transcribe tables or what to ignore. Not used by the fast tier. Example: Output every table as markdown and skip page headers and footers.
- `disable_cache` (`boolean`, optional): If true, ignore cached results and parse again. Use when the document at the URL changed. Example: false
- `max_pages` (`integer`, optional): Maximum number of pages to process, starting from page 1. target_pages wins if both are set. Example: 10
- `output_options` (`object`, optional): Output settings, for example markdown table handling, spatial text layout, or images to save. Example: {"markdown": {"tables": {"output_tables_as_markdown": true}, "annotate_links": true}}
- `processing_options` (`object`, optional): Processing settings, for example OCR languages or text to ignore. Example: {"ocr_parameters": {"languages": ["en", "de"]}, "ignore": {"ignore_hidden_text": true}}
- `target_pages` (`string`, optional): Pages to process, 1-based, as a comma-separated list of pages and ranges. Omit for all pages. Example: 1,3,5-8
- `version` (`string`, optional): Tier version: latest, or a dated version from llamaparse_parse_versions_list (for example 2026-11-09). Pass configured with configuration_id. Default: latest. Example: latest. Default: `latest`.

Example input: `{"source_url":"<source_url>","tier":"fast"}`

### `llamaparse_classify_job_delete`

Delete Classify Job · Destructive

Delete a classify job and its result.
Returns a confirmation.
Use this to remove classification data.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `job_id` (`string`, required): Classify job ID returned by llamaparse_classify_job_create or listed by llamaparse_classify_jobs_list. Example: clj-5b8e2f9c3a1d

Example input: `{"job_id":"<job_id>"}`

### `llamaparse_extract_job_delete`

Delete Extract Job · Destructive

Delete an extract job and its results.
Returns a confirmation.
Use this to remove extracted data.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `job_id` (`string`, required): Extract job ID returned by llamaparse_extract_job_create or listed by llamaparse_extract_jobs_list. Example: exj-7f2c9d1a4b6e
- `force` (`boolean`, optional): If true, delete even if the job is still running. Default: false. Example: false

Example input: `{"job_id":"<job_id>"}`

### `llamaparse_parse_job_delete`

Delete Parse Job · Destructive

Delete a parse job and its stored results.
Returns a confirmation; 409 if the job is still running.
Use this to remove parsed data. Use llamaparse_parse_job_cancel to stop a running job first.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `job_id` (`string`, required): Parse job ID returned by llamaparse_parse_job_create or listed by llamaparse_parse_jobs_list. Example: pjb-3k9x2m7q1v8c

Example input: `{"job_id":"<job_id>"}`

## Related

Other AI connectors ([all 216](/agentkit/connectors/?category=ai)):

- [Chorus](/agentkit/connectors/chorus/): Scalekit connector, Username and password, 9 tools
- [Gong](/agentkit/connectors/gong/): Scalekit connector, OAuth, 69 tools
- [Jiminny](/agentkit/connectors/jiminny/): Scalekit connector, Access token, 27 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
