Estimate Batch Cost (pre-flight, dry-run)
Pre-flight estimate of the credits a DRAFT batch will consume on submit, plus how many of its objects were already extracted — so a force/replace re-run that re-pays GPU extraction surfaces its cost BEFORE submitting. Does not consume credits or change the batch’s contents/status; it DOES refresh a DRAFT batch’s activity timestamp so the draft-TTL reaper grants a fresh grace window while you confirm the cost.
Authorizations
Mixpeek API key, sent as Authorization: Bearer mxp_sk_.... Create one in Studio under Settings → API Keys, or with an admin key via POST /v1/organizations/users/{user_email}/api-keys. A missing header returns 403; an invalid or revoked key returns 401.
Namespace id (ns_...), not the namespace name. This scopes the request rather than authenticating it, and it is required on every operation marked x-mixpeek-namespace-scoped.
Path Parameters
The unique identifier of the bucket.
The unique identifier of the batch.
Response
Successful Response
Dry-run estimate of what submitting a DRAFT batch will cost + re-pay.
skip | replace | force — controls re-extraction
Objects this batch will process
Objects in this batch already extracted before (re-paid under force/replace)
Credits submitting this batch will consume (same calc as submit)
Dollar cost of this batch under live v2 pricing (file type × amount × search-by features). Credits are milli-dollars of this value.
~credits re-paying already-extracted objects (force/replace only; linear approx)
What this batch searches by (dimension 3 of pricing): feature keys billed per file type; custom plugins as 'custom:'.
Internal implementation of features — prefer rendering features; extractor names are the deeper disclosure layer.
Dimensions 1+2 of pricing: file types and how much of each (counts, video minutes, pages, tokens…)

