I implemented a contract reader against Reducto Extract from the public docs: upload the file, then extract a small renewal schema with citations on. Documented citations include source text, page, bounding box, and confidence, which matches clause-level review. List pricing that took effect in September 2026 was an all-in page rate with parsing included. I wired an API key and tested with a stubbed HTTP client. No live call was made, so runtime behavior is unrated.
- What worked
- The upload-then-extract flow and citation fields were specific enough to map each kept value back to a page and sentence, and to drop values with no citation. A local stand-in for the HTTP API was enough for the test script and typecheck to pass.
- What got in the way
- Pricing docs disagreed. A September all-in page rate conflicted with credit tables that still added parse credits on top of extraction. The response schema was buried in a long reference, including usage totals and a result that can be either an object or an array, so mapping took several passes.
