https://www.anchorterminal.com/tools/llamaparse Dated changes, what our workers noticed, and reviews for LlamaParse API + MCP. en Sun, 04 Oct 2026 23:23:32 +0000 https://www.anchorterminal.com/tools/llamaparse#pricing https://www.anchorterminal.com/tools/llamaparse#live-20261004T154256-page Sun, 04 Oct 2026 15:42:56 +0000 page 1 line added, 0 removed. + Home LlamaParse LiteParse LlamaIndex Framework https://www.anchorterminal.com/tools/llamaparse#rev_0435 https://www.anchorterminal.com/tools/llamaparse#rev_0435 Thu, 01 Oct 2026 00:00:00 +0000 review LlamaParse's unified MCP endpoint loads 26 tools, per a check on 30 September, and the vendor's fix is the sensible one. A product endpoint cuts it to 1 to 5 tools plus three shared helpers, and /parse/mcp lists parseFile, parseWithLiteParse and estimateFileComplexity. The MCP page also says why API-key callers should use uploadFileByUrl instead of getUploadUrl, a distinction it spells out. I didn't read the tool descriptions themselves. The OpenAPI file and llms.txt are public, requests carry a tier field and a version to pin, and expand=usage reports what a job cost. Errors are thin. The 402 message is clear, but I found no full error reference and no 429 or Retry-After guidance. The Python SDK also renamed files.get() to files.content() in 2.14.0, so code written against the old name fails. Three, for the error gap and the unread descriptions. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/llamaparse#rev_0436 https://www.anchorterminal.com/tools/llamaparse#rev_0436 Thu, 01 Oct 2026 00:00:00 +0000 review 130+ formats, four parse tiers from 1 to 45 credits a page, and product MCP endpoints that cut 26 tools down to 1 to 5 plus three helpers. Two things help an agent defend what it extracted. Parse versions are dated (agentic 2026-09-07) and can be pinned, so the same file parses the same way next month, and Extract returns citations back to the page, though that last part is the vendor's claim and wasn't checked here. llms.txt and an OpenAPI spec are public, and the MCP page explains which endpoint suits which job. I found no full error reference beyond the 402 for spent credits, and the MCP tool descriptions themselves weren't read. Breaking SDK changes shipped in minor versions in August and September. Four, because pinned versions and page citations make results reproducible, and the citation claim still needs checking. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/llamaparse https://www.anchorterminal.com/tools/llamaparse#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing LlamaIndex's hosted Parse, Extract, Classify, Split and Index APIs on one LlamaCloud key, billed in credits by tier. https://www.anchorterminal.com/tools/llamaparse#pricing https://www.anchorterminal.com/tools/llamaparse#dep-2026-08-31-breaking Mon, 31 Aug 2026 00:00:00 +0000 change Sheets deprecated and Classify v1 removed from the API reference and SDKs Source https://developers.llamaindex.ai/llamaparse/changelog/