Plans and credits

One requested or submitted business costs one lead credit on active paid plans. Search and enrichment creation reserve credits before work enters the queue.

Plan	Period allowance	Current per-search maximum
Free	100	100, one free search
Starter	10,000	700
Growth	50,000	700
Scale	200,000	700

Always treat GET /account as the runtime source of truth. Subscription state can reduce max_results_per_search to zero, and credits_remaining changes as dashboard and API jobs are created.

Validation order

Before creating a paid search, choose a requested count no higher than:

min(max_results_per_search, credits_remaining)

Every search must request at least 100 businesses. Requests below 100 return 422 before Mapsdata creates a job or reserves credits. Examples:

Account state	Request	Result
Free, unused	100	Accepted; the free search is consumed.
Free, unused	700	`403` — the free search is limited to 100 leads.
Paid, 700 credits remain	700	Accepted when the subscription is active.
Paid, 700 credits remain	1,000	`402` — the response says 1,000 are needed but 700 remain.
Paid, 10,000 credits remain	1,000	`403` — a single search is limited to 700.

A free search requests and reserves 100 credits. Paid searches reserve exactly the requested count. Rejected requests create no job and spend no credits.

Successful jobs retain the reserved charge. Failed jobs follow Mapsdata’s refund path, including restoration of free-search eligibility where applicable. Reading account data, status, search lists, locations, categories, and results consumes no lead credits. A two-stage workflow is charged separately: a discovery-only search reserves its requested result count, then standalone enrichment reserves one additional credit for every selected business. The free plan contains one 100-credit job, so it cannot run a free discovery job and then a second free enrichment job.

Getting started

Endpoints

Reference

Validation order

​Validation order

Validation order