Credits

Every Encrata account has a credit balance. Each API call either costs a fixed number of credits or is free, and 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

Pay on success

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

Free repeats

Most 1-credit lookups are free again for the same address within the billing window.

Outcome-based

Some scans only charge when they find something, such as GitHub Leaks.

What each lookup costs

Standard (1 credit)
Premium
Outcome-based
Free

Endpoint	What it does
`/api/lookup/email/validity`	Email deliverability check
`/api/lookup/email/gender`	Predict gender and country
`/api/lookup/email/compliance`	Resolve cold-email jurisdiction and rule
`/api/lookup/email/breaches`	Breach history for an email
`/api/lookup/email/password/breaches`	Check if a password has leaked

Repeat lookups of the same input within the billing window are free (credits: 0, served from cache).

Endpoint	What it does	Cost
`/api/lookup/email/identity`	Resolve the person behind an email: name, role, company, socials	1,000 credits

Repeat Email Identity lookups of the same address are served from cache as free repeats within the billing window.

Endpoint	What it does	Cost
`/api/lookup/breaches/github`	Scan a public repo for leaked secrets	1 credit per leak found

A clean scan, a refused scan, and a repeat of a repository state you already paid for are all free.

Endpoint	What it does
`GET /api/lists`	List contact lists
`GET/POST /api/webhooks`	Webhook management
`GET /api/health`	Health check

Bulk runs

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

Operation	Cost
Bulk lookup (up to 1,000,000 emails)	1 credit per successful enrichment

Check your balance

Check it in the dashboard, or read it programmatically to gate spend in your own code.

API
Dashboard

Call GET /api/account/credits:

curl https://developer.encrata.com/api/account/credits \
  -H "Authorization: Bearer YOUR_API_KEY"

{
  "credits_remaining": 4794,
  "credits_used": 206,
  "total_lookups": 206,
  "stats_degraded": false
}

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.

{
  "error": "Insufficient credits"
}

Get notified before you run out

Set up webhooks to catch low balances before they block a lookup.

credits.low

Fires when your balance drops below the threshold you configure.

credits.exhausted

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.

Request only what you need

Use the fields parameter to trim the response. Same credit cost, smaller and faster payloads.

Batch high-volume work

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

Reuse recent lookups

Repeat lookups within the billing window are free - cache results on your side to avoid unnecessary calls.

Overview

Configuration

Best practices

How billing works

Pay on success

Free repeats

Outcome-based

What each lookup costs

Bulk runs

Check your balance

When you run out

Get notified before you run out

Tips to spend less

Validate before you enrich

Request only what you need

Batch high-volume work

Reuse recent lookups

Next steps

Quickstart

Rate limits

​How billing works

Pay on success

Free repeats

Outcome-based

​What each lookup costs

​Bulk runs

​Check your balance

​When you run out

​Get notified before you run out

​Tips to spend less

Validate before you enrich

Request only what you need

Batch high-volume work

Reuse recent lookups

​Next steps

Quickstart

Rate limits

How billing works

What each lookup costs

Bulk runs

Check your balance

When you run out

Get notified before you run out

Tips to spend less

Next steps