Skip to main content
Coding agents can read the Unsiloed documentation without rendering the website. Start with the focused documentation index, then open only the raw Markdown pages needed for the task.

​
Start With the Focused Documentation Index

Use llms.txt to discover documentation pages and their raw Markdown URLs. The index is approximately 10 KB, so it provides a lower-context starting point than loading the complete documentation corpus. Use llms-full.txt only when the task requires searching across the entire documentation set. Every documentation page is also available as raw Markdown. For example:

​
Choose the Document Operation

Unsiloed separates document processing into four operations. Choose the operation from the result your application needs: For a first parsing integration, follow the parsing quickstart. It provides Python, JavaScript, and cURL examples for submitting a document, polling the job, and reading the result. The Python and JavaScript examples save both JSON and Markdown output.

​
Use the API Endpoints

Send authenticated requests to https://prod.visionapi.unsiloed.ai with your API key in the api-key header. Use these routes for new integrations: Accepted jobs return a job_id for polling. Parse jobs finish with Succeeded, Failed, or Cancelled. Extraction results are available when the status is completed or review, and extraction can end with failed. Classification and splitting jobs finish with completed or failed. Use POST /parse for standard parsing unless the file needs the large-file upload flow or is an Excel workbook. For the large-file upload, send the file to upload_url with the returned upload_headers; the presigned PUT does not use the api-key header. Poll the resulting job through GET /parse/{job_id}. When extraction has personally identifiable information (PII) detection enabled, it can instead return status: "pii_blocked" with no job. Check the submit response before polling.

​
Treat OpenAPI as Supplementary Reference

Use the human-readable guides and API references linked above as the source of truth for current integrations. The aggregate OpenAPI specification still uses older Parse field names and requires a file upload, so it does not fully describe URL-only Parse requests. Verify generated clients against the relevant endpoint reference before using them:

​
Distinguish Documentation Access From Product Tools

The Unsiloed Document Processing MCP server gives an agent tools for parsing, classification, and structured extraction. It processes documents and does not search the documentation. For documentation research, use llms.txt and raw Markdown pages. For document-processing actions, use the MCP server or REST API.