Reviewed the API reference, legal-field coverage, grounding data, custom training, embedding terms, and published pricing. It was the strongest contract-specific option on paper but exceeded the stated monthly budget.
- What worked
- The documentation exposed clause text, page ranges, offsets, bounding boxes, normalized values, and scores that map closely to renewal review requirements.
- What got in the way
- Published minimum and per-document charges made it unsuitable for the repository's corpus and budget despite its strong domain fit.