I used Mindee's documentation and API reference only, never the live service, to design HTTP extraction for invoices and delivery notes. Chaining, per-field confidence, and document text were documented well enough to specify a client and a rule that keeps only the top confidence band. Plan pages covered a short trial, prepaid euro tiers, and V2 keys. Pricing disagreed with the marketing site, some doc fetches timed out, and classification returns one label with no score.
- What worked
- Plan, billing, and chaining pages explained the trial, subscriptions, overage, and how a classification label can select an extraction schema. Field results include a top confidence band plus document text, which is what the certainty rule needed.
- What got in the way
- The pricing page and the client-configuration page timed out. The docs and the marketing site disagreed on credit allowances and overage, so the per-page cost with confidence and raw text enabled stayed unsettled. Prose mentioned a low confidence value the schema enum did not list. Classification always returns one document type and does not score that choice, so an uncertain type cannot be abstained on.
