Per-call credit consumption trail
Usage history includes this as part of the Lead Intelligence surface on /products/usage.
Axix OWL
Trace with Usage history
Usage history records Lead Intelligence calls that consume credits: returned leads, returned emails, and successful company lookups. Finance and ops use it to attribute spend to teams or jobs; engineers use it to debug 402 insufficient credits and 429 rate limits. History lives next to the dashboard and API key controls.
See which calls spent credits — Search, emails, and company lookups.
Without usage history, credit burn is a ghost story
Usage history records which Search, Email Finder, and Company lookup calls spent credits so RevOps can attribute cost to jobs, keys, and teams.
Usage history capabilities
Filter by endpoint and time range
Usage history includes this as part of the Lead Intelligence surface on /products/usage.
Attribute spend to keys or jobs
Usage history includes this as part of the Lead Intelligence surface on /products/usage.
Spot 402 and 429 patterns early
Usage history includes this as part of the Lead Intelligence surface on /products/usage.
Export-friendly views for finance
Usage history includes this as part of the Lead Intelligence surface on /products/usage.
Multi-tenant isolation
Usage history includes this as part of the Lead Intelligence surface on /products/usage.
Usage history checklist
What operators verify before trusting production traffic.
- Filter by endpoint and time
- Attribute spend to API keys
- Reconcile with CRM load counts
- Investigate 402 insufficient credits
- Watch 429 clusters before raising plan
- Export-friendly views for finance
Close the loop after a job
Run
Execute Search, Bulk Search, or Email Finder.
Record
Usage history captures credit spend.
Attribute
Map spend to key, team, or campaign.
Decide
Top up, upgrade, or throttle the next job.
Spend that finance can explain
Every returned lead, email, and successful company lookup leaves a trail — the opposite of opaque seat contracts.
- Per-call credit trail
- Key-level attribution
- 402 / 429 forensics
- Multi-tenant isolation
The audit trail for a credit-based API
When 402 hits, usage history explains why — not a vague “you used the product a lot.”
Axix OWL
See Usage history beside a live credit balance
Open Usage history next to remaining credits so every returned lead, email, or successful company lookup is visible before it lands in CRM or outreach.
