Credit Costs

Every billable operation in the eCore API is priced in credits drawn from your wallet. This page is the single source of truth for what each operation costs and when the charge is applied.

Pricing Table

Operation	Cost	Charged When
Search Records	Free	—
Unlock Email	1 credit	Per record, on unlock
Unlock Phone	5 credits	Per record with phone data
Unlock Phone — no data	1 credit	Per record with no phone data on file
Email Enrichment	1 credit	Only when email is found (status: success)
Phone Enrichment	5 credits	Only when phone is found (status: success)
Account/Contact Enrichment (Standard)	Dynamic — per-row, based on requested fields	Upfront on submit; reconciled at end of job
Account/Contact Enrichment (Pro)	Dynamic — higher per-row rate	Upfront on submit; reconciled at end of job
Email Validation	1 credit per email (default)	Upfront on upload; refunded for any non-Valid result
Already-owned records (any unlock)	0 credits	Skipped automatically

Charging Behavior

Charge-on-success (Enrichment endpoints)

Email and Phone Enrichment use a charge-on-success model:

• A successful lookup (status: success) deducts the per-call rate.
• A not_found result returns 200 OK but no credit is charged.
• Validation errors (400) and auth errors (401) never charge.

This makes enrichment safe to retry with different identifier combinations — only paid hits cost you credits.

Upfront-with-refund (Email Validation, Account Enrichment)

Bulk operations use an upfront-with-refund model:

• The full estimated cost is deducted before the async worker starts processing.
• At the end of the job, credits for any record that did not produce a billable outcome (e.g., non-Valid emails, contacts that fail name-match) are refunded in a single combined wallet transaction.
• If the job crashes, all upfront credits are refunded by the failure handler.

The job's total_credits_charged field shows the final net charge after refunds.

Pre-check before charging

For every endpoint that charges credits, the wallet balance is checked before the operation begins:

• Sufficient balance → request proceeds and credits are deducted.
• Insufficient balance → 402 Payment Required is returned and no credits are deducted.

Pricing Configuration

The per-operation rates above are the platform defaults. Actual rates are read from a dynamic pricing configuration that can be adjusted by administrators. Your remaining_credits (or wallet_balance) field on each response shows the canonical balance after the call.

If you're unsure of the current rate for a high-volume operation (e.g., before a large Account Enrichment submission), make a small test request and compare remaining_credits before and after — that gives you the live per-row cost.

Wallet Top-up

To add credits, sign in to the eCore dashboard at app.ecoreservice.com and navigate to Billing → Add Credits.