Skip to content

MaintenanceThe former company search endpoint goes into maintenance on November 9Migration guide

Reverse ContactDocs
Reverse ContactDocs
API pricing Changelog What's changing

Introduction

Integration guides

Migrations & changes

Code examples

AI agents & CLI

Get API keyLog in
Supportreversecontact.com

Integration guides

Credits

Updated

Last verified

How the API charges credits, what is always free, how async jobs are refunded, and how to spend less.

Most requests cost between 0 and 3 credits depending on the endpoint. Find Email costs 3 credits when a professional email is found and 5 when a personal one is found (8 when a lookup finds both), Find Phone costs 20 credits when a number is found, the people search endpoints cost 1 credit per profile delivered and Company search 1 credit per company delivered, plus 1 credit per page for Agentic Search and Agentic Company Search. Most errors and status checks are always free. The API pricing page lists every endpoint, and Rate limits covers how many requests you can send.

You're never charged for

  • Errors all 4xx and 5xx responses cost 0 credits, except 404 which depends on the endpoint (see API pricing).
  • Check and Usage endpoints always 0 credits, designed for testing and decision-making before spending.

You can test the API freely before committing credits.

Per-endpoint pricing

The API pricing page lists every endpoint with what it costs when it finds a result and when it does not, whether an async lookup that finds nothing is refunded, and where its data comes from. Its figures are the ones the API bills, and the same table is in your dashboard under Billing > API pricing.

Async endpoints follow their own billing model: credits are charged when the request creates the job, then refunded automatically based on the outcome. A job that ends in error without data (fetch-data-error, invalid-data, result-unavailable, invalid-request) is refunded, and so is a Find Email or Find Phone lookup that finds nothing. A live fetch that finds no profile is billed. Refunds are auditable in the Webhook Events dashboard.

Plans and credits

Credits work on every endpoint. On a Go, Plus or Max plan, the calls your plan covers cost 0 credits, up to the daily profile cap described in Rate limits, and every other call costs credits. What each plan covers is on the pricing page.

Agent, MCP, and dashboard usage

Not every credit-consuming action shows up as the same kind of usage event:

  • Agent LLM turns consume credits, but they do not call the API endpoints.
  • Agent tool calls use the same endpoints as the REST API and consume the same endpoint credits.
  • MCP calls use the same credits as the REST API.
  • Polling and status-only endpoints such as GET /v2/usage and GET /v2/webhooks/:webhookId stay free.

In the dashboard, the Usage channels section is the best view to understand where credits are going across Agent, MCP, and API usage. The request analytics tabs remain HTTP-request-centric on purpose. How each of these counts toward your per-minute limit is in Rate limits.

Save credits

Check before you fetch. Call the free Check endpoint first to see if a profile exists and when it was last updated. Then decide: cached fetch (1 credit) or live scrape (2 credits). See Data freshness for the full strategy.

Use Search for bulk discovery. People search returns full profiles and costs 1 credit per profile delivered, so size your query first with the free count endpoint. Company search works the same way for companies: full company profiles at 1 credit per company delivered, sized for free with its own count endpoint. On both, lower perPage to cap what a single request can spend.

FAQ

Am I charged for errors or 404 responses?

Reverse Contact API responses with a 4xx or 5xx status cost 0 credits, except 404, whose cost depends on the endpoint. The Reverse Contact API pricing page gives the cost of a 404 for every endpoint, in its Not found column.

Where can I see what each Reverse Contact endpoint costs?

The Reverse Contact API pricing page, at docs.reversecontact.com/pricing, lists every endpoint with its cost when it finds a result, its cost when it does not, whether an async lookup that finds nothing is refunded, and where its data comes from. The same table is in the dashboard under Billing > API pricing.

Can I still call the API when my credits run out?

When a Reverse Contact workspace has fewer than 2 credits left, even the free Check endpoints (POST /v2/fetch/persons/check and /v2/fetch/companies/check) return 402 NO_CREDITS. GET /v2/usage, GET /v2/flags, the Search available-fields endpoints and webhook polling (GET /v2/webhooks/:webhookId) keep working, so you can still read your balance and retrieve already-paid results.

Are credits refunded when an async request finds nothing?

It depends on the endpoint. Reverse Contact async requests are charged at creation. Find Email and Find Phone refund the credits automatically when no email or phone number is found, and a job that ends in error without data (fetch-data-error, invalid-data, result-unavailable, invalid-request) is refunded. A live fetch that finds no profile is billed. Webhook delivery failures are not refunded, because the data was successfully fetched, and refunds can be audited in the Webhook Events dashboard.