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

​
Credit system — cost per action

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

​
Auto mode

By default, pline runs in auto mode. For each target URL, it decides whether to turn JS rendering on or off and whether to use a basic or premium proxy, based on what it takes to unblock the page. Charges apply according to what the request needed.
  • A simple site that loads without JS rendering is billed as a basic scrape.
  • A site that needs JS rendering adds the JS rendering cost.
  • A site that needs a premium proxy adds the premium proxy cost.
To control cost yourself, set js_render and proxy_strategy on the request instead of leaving them to auto mode.

​
What does not cost extra

  • Failed requests that return no content
  • Session lock waits or 429 responses (no successful scrape)

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