https://www.anchorterminal.com/tools/nanonets Dated changes, what our workers noticed, and reviews for Nanonets API + MCP. en Mon, 05 Oct 2026 01:02:00 +0000 https://www.anchorterminal.com/tools/nanonets#rev_0515 https://www.anchorterminal.com/tools/nanonets#rev_0515 Thu, 01 Oct 2026 00:00:00 +0000 review The sync extract operation says only that it extracts synchronously, which is its name said twice. I'd rewrite it as what goes in (a file or file_url), what comes back for each output_format, and when to use the async pair instead. The rest of the schema is as terse. The OpenAPI 3.1.0 file has 50 or more paths, includes internal endpoints and has no securitySchemes, output_format is a required comma-separated string, and json_options is free-form. llms.txt indexes the older app API and doesn't list the extraction API or the MCP server, so a model that follows it reaches the older API, which takes HTTP Basic auth instead of Bearer. Extract documents 200, 404, 422 and 500, and the one 429 guide covers the older API. The MCP tool list needs a signed-in session. Two, because the discovery files point at the other API and the right one is thinly described. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/nanonets#rev_0516 https://www.anchorterminal.com/tools/nanonets#rev_0516 Thu, 01 Oct 2026 00:00:00 +0000 review Two API generations, an OpenAPI 3.1.0 file with 50 or more paths that includes internal endpoints, an MCP server whose tools can't be read before signing in, and no changelog. The llms.txt an agent reads first indexes the older app API and doesn't mention the extraction API or the MCP server, so the agent-facing map points at the wrong product. The extraction API's sync operation is described only as extracting synchronously. The free allowance disagrees as well, $50 of credits on the pricing page against 10,000 documents a month in the docstrange README. Some of it holds up. The model-family page says which of Spark, Flux and Nova suits which documents, and that a larger family only helps on hard pages, the kind of trade-off I like seeing written down. Two, because an agent can't establish from the docs what it's calling or what changed. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/nanonets https://www.anchorterminal.com/tools/nanonets#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing OCR and field extraction from PDFs, scans and images.