POST /v1/vision

Run a perception pass (unit-billed, per image)

Robot vision route (route_type: vision; task #37). Perception turn: image file(s) in, mask/annotation JSON or binary out — negotiated by the response_format form field (json, the default | binary; anything else is 400 invalid_param/response_format). Multipart/form-data ONLY; the body crosses to the card VERBATIM (the dial is POST <lane-base>/vision). Accepted form fields — model (required), one or more file FILE parts (the single-kind slot, the OCR twin), response_format. SAM point/box prompts are NOT accepted day one (automatic-mask / full-image is the day-one shape; a point or box field is 400 unknown_param — the additive later param set if a lane ever needs them). The 25 MiB multipart family cap applies (413). Metering: unit_type='images' (the existing per-image unit) — the model-reported images count on a JSON answer when it is a whole count in [1, 1e9], else the request's file-part count (files — a reported zero/negative, fractional, or absurd value on a 200 falls to the files basis). usage on a JSON answer is OUR {images, cost} at 6dp; a BINARY answer (response_format=binary) is the provider's Content-Type + bytes VERBATIM — no rewrite is possible, billing is input-side (the files basis). An unparseable 2xx JSON body relays verbatim (the row already billed by count). Lane saturation at the provider relays as CLIENT 429 rate_limited (never a 502) with the card's Retry-After forwarded when present, non-rotating, the turn unbilled. Idempotency-Key: accepted and logged, NO replay semantics (the §8 multipart family). The robot models ship UNLISTED at launch (task #37).

curl -X POST https://api.ironstratum.com/v1/vision \
  -H "Authorization: Bearer $IRONSTRATUM_API_KEY" \
  -F model=<model>
  -F file=@<file>