Usage & Registry
The Usage & Registry page replaces the legacy credits view with a comprehensive cost breakdown. It shows per-feature cost (extraction, OCR, batch, matching), a daily cost chart, and a full call log with model, tokens, and cost per request. The Master view (admin only) shows per-customer breakdowns and platform-wide statistics. Navigate to Usage from the sidebar to access all views.
Understanding your usage patterns helps optimize costs. For example, if extraction dominates your spend, consider using batch mode for non-urgent documents to cut that cost in half. If OCR is a significant portion, check whether you are processing image-heavy documents that could benefit from better source quality. The daily cost chart makes it easy to spot usage spikes and correlate them with specific ingestion events or batch completions.
Behind the scenes, every LLM and OCR call is logged with full detail — the model used, input and output token counts, latency, and computed cost. This data powers both the per-feature breakdown and the individual call log. The system tracks costs across extraction, OCR, batch inference, matching AI resolution, and quality passes so you always know where your spend is going.
Most teams review the daily cost chart weekly to establish a usage baseline. Unexpected spikes usually correlate with large document uploads or batch completions. For organizations managing multiple workspaces, the Master view provides a single pane of glass showing per-customer breakdowns and platform-wide aggregates — accessible only to platform administrators.
Usage views
| Parameter | Type | Description |
|---|---|---|
| Per-feature costs | breakdown | Extraction, OCR, batch inference, matching, and other features listed with total cost. |
| Daily cost chart | visualization | Bar chart showing daily spend over the past 30 days. |
| Call log | audit | Every API call with model, token count, latency, and cost. |
| Master view | admin | Per-customer breakdown and platform-wide aggregates. Accessible only in master (all-tenant) mode. |
Cost Optimization Tips
- Use batch mode for non-urgent documents — extraction runs at 50% cost with a 48-hour delivery window.
- Build your field registry — as more fields reach Tier 1 and Tier 2, extraction costs drop because values are resolved via lookup instead of AI calls.
- Review the per-feature breakdown weekly to identify which operations dominate your spend.
- Leverage routing rules to automatically assign schemas, reducing the number of manual job runs and re-extractions.
Tracking Usage via API
Usage data is fully accessible through the REST API, enabling you to build custom cost monitoring dashboards or integrate usage tracking into your financial systems. The credits endpoint provides credit balance, transaction history, daily breakdowns, and per-request usage logs. This is particularly useful for organizations that need to allocate extraction costs across departments or client projects based on actual usage.
curl https://api.talonic.com/v1/credits \
-H "Authorization: Bearer $TALONIC_API_KEY"{
"balance": 12450,
"total_used": 37550,
"usage_by_feature": {
"extraction": 22100,
"ocr": 8900,
"batch": 4200,
"matching": 2350
},
"period": "current_month"
}For automated cost monitoring, query the daily breakdown endpoint to track spend trends over time. Set up alerts in your monitoring system when daily spend exceeds a threshold — this catches unexpected usage spikes caused by large document uploads or misconfigured routing rules before they accumulate into significant costs. Teams that monitor usage proactively typically identify optimization opportunities that reduce their monthly extraction costs by 20-30%.
curl https://api.talonic.com/v1/credits/daily \
-H "Authorization: Bearer $TALONIC_API_KEY"{
"data": [
{ "date": "2026-05-07", "cost": 12.50, "documents_processed": 45 },
{ "date": "2026-05-06", "cost": 8.30, "documents_processed": 31 },
{ "date": "2026-05-05", "cost": 15.80, "documents_processed": 62 }
]
}The per-request usage log is particularly valuable for cost allocation. Each entry includes the document ID, job ID, model used, token counts, and computed cost. This granular data lets you attribute costs to specific documents, document types, or processing jobs. For organizations that charge back extraction costs to departments or clients, this data provides the foundation for accurate, auditable billing. Export the usage log via the API and feed it into your accounting or BI system for automated cost reporting.