Can I See a Breakdown of My Credit Usage?

Yes. You can view your API logs and credit usage directly from your Enrich Layer dashboard. This lets you see exactly how your credits are being used — broken down by request.

How to access your usage breakdown

1. Log in to your Enrich Layer dashboard
2. Navigate to the API Logs section
3. You'll see a log of your API requests, including:
   • Endpoint called — which API endpoint was used (e.g., Person Profile, Company Profile, Person Search)
   • Credits used — total credits consumed by the request
   • Credit Breakdown — a detailed breakdown showing exactly how much each parameter contributed to the final credit cost (e.g., base cost, Data Freshness, enrichment add-ons)
   • Timestamp — when each request was made
   • Response status — whether the request was successful or returned an error

Looking up a specific request

Every API response includes a request ID in the response headers. You can use this ID to find the exact request in your API Logs and see its full credit breakdown.

This is especially useful when you want to verify how much a specific call cost or understand why it used more credits than expected.

What the credit breakdown shows

The Credit Breakdown column shows exactly which parameters added to the cost of each request. For example:

• Base cost — the standard credit charge for the endpoint
• Data Freshness — if enabled, this adds an extra credit per request
• Enrichment parameters — optional fields like funding_data or exit_data that increase the cost
• Result volume — for search endpoints, credits scale with the number of results returned (3 credits per result)

Tips for monitoring your usage

• Check your credit balance regularly — your remaining balance is visible on the dashboard
• Review logs after large queries — confirm usage matches your expectations
• Set a smaller page_size when testing — keeps per-call costs low while you iterate on filters

If you're unsure what a specific charge means, contact support at [email protected] and share the request ID from your response headers — we can look into it together.