Skip to main content
Pipecorn meters usage with two separate mechanisms that are easy to confuse, partly because the GET /credits response uses the word “credits” for both. This page tells them apart so you know which one a request draws on, which one an error is about, and what actually unblocks you.
One-line version. A credit is a paid unit you spend on enrichment (emails, phones, company and people data). A limit is a quota bundled with your plan that caps how many profiles or companies you can extract per day or month. Buying credits never raises a limit, and a limit resetting never adds credits.

Side by side

Preview endpoints (/leads/advanced_search/preview, /accounts/search/preview, /intents/accounts/stack/preview) draw on neither. They are free and never return either error.

Enrichment credits

Credits are the paid resource. Every endpoint that returns enriched data checks your balance before doing any work and charges only for what it actually returns: When the balance is too low the request is rejected up front with 402 and nothing is spent, enqueued, or imported. Top up and replay the same request. Credits belong to the workspace, so every member and every API key spends from the same pool.

Plan limits

Limits are quotas, not a balance. They come with your plan, reset on a fixed schedule, and cannot be bought one at a time. There are two of them: When a quota is used up the endpoint answers 422 with "Can't proceed with the request. Plan limit reached.". Wait for the reset or move to a plan with a higher allowance. Buying credits does nothing here.
In GET /credits the remaining quotas live under the credits key, next to credits.enrichment, and the field descriptions call them “credits”. Read them as remaining quota for the current period, not as a spendable balance. Only credits.enrichment is money you can top up. The limits object gives each quota’s ceiling so you can compute how much of the period you have used.
In this example the workspace has 3,000 enrichment credits to spend, and can still extract 1,500 of its 2,500 daily profiles.

Two other “limits” that are not plan limits

Workspace weekly credit limit

A workspace admin can cap how many enrichment credits each member may spend per week. This is a spending ceiling on credits, not a quota on extraction. Hitting it returns 403 Forbidden with code: "workspace_limit_exceeded" and no top_up_url: the balance may be fine, so buying credits does not help. An admin raises the member’s weekly allowance, or the limit resets at the end of the week.

Rate limits

Requests per second or per minute, tracked per API key and per endpoint. Exceeding one returns 429 Too Many Requests. Rate limits are about request pacing and have nothing to do with credits or quotas; back off and retry.

Which one am I hitting?

Branch on the status code and, for 403, on the code field. For the exact response bodies and the list of endpoints that return each code, see Credit and limit errors.
History. Until August 2026, enrich account and enrich people drew on the company import and profile scraping quotas and failed with 422 when they ran out. They are now priced in credits and answer 402 and 403 instead. See the changelog.