Credits and usage - pline

pline bills in credits. Credits are consumed per API request based on the action performed and whether it uses a residential (premium) proxy.

Credit system — cost per action

Action	Credits	Notes
Basic scrape (standard proxy)	1 credit	Default scrape via unblocker/datacenter proxy
JS rendering	2 credits
Enhanced proxy	3 credits	Premium residential proxy for hard/anti-bot sites
Premium proxy	4 credits	Premium residential proxy for hard/anti-bot sites
Map (extract site links)	1 credit	Flat, regardless of site size (fair-use applies)
Crawl — basic (per page)	1 credit / page	Standard proxy
Crawl — residential (per page)	3 credits / page	Residential proxy
Search	2 credits / page	1 page = 10 results; runs on browser + managed proxy

Costs for the same request can combine — for example, a JS-rendered scrape on a residential proxy costs more than a basic static scrape. See your plan’s included credits for how far these go each month.

What does not cost extra

Failed requests that return no content
Session lock waits or 429 responses (no successful scrape)
Health check endpoints (/health/*)
Session playbook CRUD (/session, /strategy)

Dashboard

Dashboard → Usage shows:

Current credit balance and renewal date
Daily usage chart
Top tags by spend
Export to CSV

Response fields for reconciliation

Every scrape response includes fields you can log for billing alignment:

{
  "request_id": "req_01HZ1234ABCD5678EFGH",
  "site_tier": "standard",
  "proxy_tier": "enhanced",
  "status": 200
}

Log request_id, site_tier, and proxy_tier with your job ID for support and invoice disputes. The tag you send on a request isn’t echoed back in the response body, but it is attached to the request for spend attribution — look it up by request_id in Request history.

Subscription