Skip to main content
Every Encrata account has a credit balance. Lookups use fixed, outcome-based, or free pricing. You are only charged on a successful response.
Credits are deducted after a successful response. If a lookup fails with a 5xx error, you are not charged.

How billing works

Free-repeat window

Repeat lookups of the same input are free for 6 months after your first paid lookup.

Pay on success

Failed lookups (502, 503, 504) never cost credits.

Free repeats

Most 1-credit lookups are free again for the same address during the 6-month free-repeat window.

Outcome-based

GitHub Leaks and Exposed API Keys charge only when they find credentials.

What each lookup costs

Repeat lookups of the same input during the 6-month free-repeat window are free (credits: 0, served from cache).

Bulk runs

Bulk runs charge per successful item, not per request. A run of many addresses charges only for the ones that resolve successfully.

Check your balance

Check it in the dashboard, or read it programmatically to gate spend in your own code.
Call GET /api/account/credits:

When you run out

When your balance is too low for a lookup, the API rejects the request with 402 Payment Required and does not run the lookup.

Get notified before you run out

Set up webhooks to catch low balances before they block a lookup.
Fires when your balance drops below the threshold you configure.
Fires when your balance reaches zero.
See Webhooks to configure these alerts.

Tips to spend less

Validate before you enrich

Run the free-repeat validity check first and skip invalid addresses before a premium lookup.

Batch high-volume work

Bulk runs share the same per-item cost but are built for volume.

Reuse recent lookups

Repeat lookups during the 6-month free-repeat window are free. Cache results on your side to avoid unnecessary calls.

Next steps

Quickstart

Make your first lookup in under two minutes.

Rate limits

Understand request limits alongside credit costs.