For AI agents: a documentation index is available at the root level at /llms.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
The same chunks indexing produces, without a collection: the Parse API runs a file through the parsing and chunking Captain uses for indexing and returns the chunks without storing them in a collection. Each chunk carries its text, token count, layout type, and page or row location, so the chunks can go into another database and be managed there. See Parse Document.
Documents and spreadsheets: POST /v3/parse/documents takes PDF, DOCX and DOC files, with processing_type set to advanced or basic. POST /v3/parse/spreadsheets takes XLSX, XLSM, XLS, CSV and TSV files, with optional image descriptions and verified facts. See Parse Spreadsheet.
Links or uploads: a parse request takes input, either a direct download link (public or presigned) or a captain:// ID from Upload File. Links without a file extension work too, because Captain reads the file type from the file itself.
Jobs with webhooks: each request starts a job. Get Parse Job returns its status and, once it completes, the chunks in order. Pass wait (up to 50 seconds) to hold the request until the job ends instead of polling on a timer. The parse.completed, parse.failed and parse.cancelled webhook events report when a job ends.
Billing matches indexing: document pages bill at the indexing rates for their processing type. Spreadsheets bill for their sheet text and for each described image. Failed and cancelled jobs are not billed.
