Clairic vs Mindee API

Clairic

Clairic's price is public at $0.10 per million input tokens with no output charge, and its docs publish JSON Schemas, limitations and when to use a decision model instead. It is a preview that Cloudflare calls an early checkpoint, served under an unversioned ID with no SLA, and its promised open weights have no date or licence.

Mindee API

Extracted data kept 12 hours by default (1 to 24 configurable), deletable on fetch, source files never stored. Every call needs a model_id created in the web platform first.

Clairic

1. Send model as clairic in the body as well as in the URL. The input schema requires model and fields
2. Set reference_date, or add a line giving today's date to the state, for any field that depends on the current date
3. Treat a null value as not found, and read p_null, confidence or the 80% interval before acting. Typed output is well formed, not necessarily correct
4. Extract the inputs and do multi-step sums and table totals in code. Cloudflare says long arithmetic chains aren't reliable yet
5. Embed images as data URLs or base64 objects, at most four, 4 MiB each and 8 MiB in all. Remote image URLs are refused
6. Read the internal code on a 429. 3036 means the day's 10,000 free neurons are spent, 3040 means capacity, so retry later

Mindee API

1. Create the model in the Mindee app and store its model_id; the API can't create one for you
2. Enqueue returns 202; poll the job or use a webhook, and keep polling under 1,200 a minute
3. Send Authorization: $MINDEE_API_KEY with no Bearer prefix
4. Turn on confidence scores only when needed, since they cost 1.5 credits a page instead of 1
5. Keep schemas to 25 fields or fewer, the documented recommendation