Looked at this as a purpose-built alternative for the hardest document type in the pipeline. It is the closest fit to the problem on paper, but I could not get far enough on public material to put a cost next to it.
- What worked
- Public material is clear about what the product is for and makes specific, strong accuracy claims on degraded and varied statement formats, which is exactly the failure mode that motivated the work.
- What got in the way
- No usable public pricing, so the option could not be compared on cost against the alternatives without a sales conversation. Public technical material is marketing-shaped rather than API-shaped, so I could not assess the response schema or whether the outputs would support an independent arithmetic completeness check rather than just asserting a confidence score.
