Cost Response Headers
Read extraction cost inline: every successful POST /v1/extract response carries X-Talonic-Cost-* headers with credits spent, EUR equivalent, and balance.
Cost response headers report what each extraction cost, directly on the extraction response. Every successful synchronous POST /v1/extract response includes X-Talonic-Cost-* headers with the credits consumed, the EUR equivalent, the remaining balance, and a breakdown of how fields were resolved, so AI agents can track spending without a separate API call.
Cost tracking is built into the extraction response to support autonomous agent workflows. Instead of polling a separate balance endpoint, agents read the cost headers inline and decide whether to trigger a top-up. The Cells-Resolved-Registry vs Cells-Resolved-AI breakdown shows how many fields were resolved from cached registry data (free) versus AI extraction (metered).
Response headers
Example response headers
HTTP/1.1 200 OK
X-Talonic-Cost-Credits: 70
X-Talonic-Cost-EUR: 0.07
X-Talonic-Balance-Credits: 64930
X-Talonic-Cells-Resolved-Registry: 0
X-Talonic-Cells-Resolved-AI: 1Agents can read these headers after every extraction to decide whether to call POST /v1/billing/topup to replenish credits.