Skip to main content
Credits are the currency you use to pay for email verification, email finder searches and company enrichment in OrbiSearch. You purchase credits in advance and they are deducted as you use the API. Understanding how credits are counted, and how deduplication reduces consumption, helps you get the most out of your balance. Credits are the pay-as-you-go billing model. The email finder is also available on flat-rate unlimited plans, where no credits move; email validation and company enrichment are credits-only on every plan.

​
Cost per operation

There are no separate charges for API calls. A request we can’t complete on our side is refunded (see Refunds).

​
Repeat requests

Every returned response is charged, including repeats of the same input: each email finder search costs 1 credit and each verification costs 0.2 credits every time. Within a single bulk job, duplicates are removed before billing (see below), but separate requests and separate jobs are each charged in full.

​
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. Bulk company enrichment works the same way: each unique input is charged once, however many times it appears. A LinkedIn URL and a domain for the same company are two different inputs, so each is charged. The bulk email finder charges each unique person once (matched on name and domain, or on the LinkedIn profile URL). A row that isn’t a LinkedIn profile URL at all comes back as invalid_linkedin_url and costs nothing.
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.

​
Refunds

Credits are refunded only when OrbiSearch infrastructure can’t complete a request: a single request that returns 502, or a bulk submission we can’t accept or process, whose upfront charge is reversed. Every other returned response or result row is charged, whatever its outcome. The one exception is a bulk email finder row that isn’t a LinkedIn profile URL, which costs nothing (see above).

​
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:
The response includes your current balance and your user ID:

​
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.
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.