Skip to main content
Credits are the currency you use to pay for email verifications in OrbiSearch. You purchase credits in advance and they are deducted as you verify addresses. Understanding how credits are counted — and how caching and deduplication reduce consumption — helps you get the most out of your balance.

​
Cost per verification

Each email verification costs 0.2 credits. There are no separate charges for API calls, substatus lookups, or failed requests.

​
Caching

OrbiSearch caches verification results for 24 hours. If you verify the same email address more than once within that window, the cached result is returned and no additional credits are deducted.
Caching applies per email address. Verifying [email protected] ten times in one hour costs 0.2 credits total — not 2.0.

​
Deduplication in bulk jobs

When you submit a bulk verification job, OrbiSearch automatically deduplicates the list before processing. You are only charged for each unique email address, regardless of how many times it appears in the input file.
You do not need to deduplicate your lists before uploading them. OrbiSearch handles this automatically and you will never be charged twice for the same address in a single job.

​
Checking your credit balance

You can check your remaining credits at any time via the API or in the dashboard.

​
API

Send a GET request to /v1/credits with your API key: 
curl "https://api.orbisearch.com/v1/credits" \
  -H "X-API-Key: YOUR_API_KEY"
The response includes your current balance and your user ID: 
{
  "credits": 4250.0,
  "user_id": "usr_abc123"
}

​
Dashboard

Your credit balance is displayed in the top navigation bar of the dashboard and on the Billing page, where you can also view your usage history and purchase additional credits.

​
Tips for managing credit usage

Verify once, reuse the result. Store verification results in your own database so you can reference them without re-verifying. Credits are only consumed on the first call within the 24-hour cache window.
Filter obvious invalids before verifying. Use client-side syntax validation to catch malformed addresses (missing @, invalid TLD) before submitting them to the API. This prevents spending 0.2 credits on addresses that would return invalid_syntax.
Batch with bulk jobs. Bulk verification jobs are the most efficient way to process large lists. Deduplication is automatic and you avoid the overhead of making individual API calls per address.