polyscrape API · Account Balance

Account Balance

Check the remaining prepaid balance on the account behind the API key, in credits and dollars.

Returns the caller's remaining balance as both `free_balance_credits` (raw integer credits) and `free_balance_display` (a dollar string). The account is identified entirely by the API key, so this endpoint takes no request body. Free. Use it to check funds before a pricier call, or to surface a live balance in your own dashboard.

POST /api/v1/account/balance Free

Use your polyscrape API key instantly, or inspect the sample response first.

curl
curl -X POST https://polyscrape.com/api/v1/account/balance \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $POLYSCRAPE_API_KEY" \
  -d '{}'

Sample response

{
  "currency": "USD",
  "free_balance_credits": 500,
  "free_balance_display": "$0.50"
}

API Playground

Run a real /api/v1/account/balance request. No key? We show the real sample result so you can still inspect the shape.

Endpoint

POST /api/v1/account/balance

sample mode
Auth header X-API-Key
Cost Free

Leave empty to inspect the response shape without spending API balance.

Sample mode: explore the real response shape for free. Add a key to run a live request.

Response

POST /api/v1/account/balance

sample
{
  "currency": "USD",
  "free_balance_credits": 500,
  "free_balance_display": "$0.50"
}

Request and response

The full contract for /api/v1/account/balance: what to send and what comes back.

Request body

This endpoint takes no request body. The account is identified by your API key. Send an empty POST.

Response fields

Field Type Description
free_balance_credits integer Remaining balance in raw credits (1 credit = $0.001).
free_balance_display string The same balance as a dollar string, e.g. "$0.50".
currency string Always "USD".

Code examples

Copy, paste, swap in your API key.

curl -X POST https://polyscrape.com/api/v1/account/balance \
  -H "Content-Type: application/json" \
  -H "X-API-Key: " \
  -d '{}'

What developers build with it

Common ways Account Balance ends up in production.

Checking remaining funds before a batch of scrape or search calls.

Surfacing a live API balance in your own dashboard.

Alerting a workflow when the prepaid balance runs low.

Status codes

The same predictable contract on every endpoint.

200 Success. The lookup completed and was charged, even if the response is empty (a no-match search, or a thin page).
400 The request was rejected before any fetch (for search: an unsupported country code). Never charged.
401 Missing or unknown API key. Never charged.
402 Not enough balance on the account. Never charged. The detail is a JSON object with error, message, credits_required, and api_credits.
422 Invalid request body (wrong shape or types). The detail is a list of per-field errors. Never charged.
429 Rate limit exceeded: max 10 requests per second per API key (5/second for parse, which is CPU-heavier). Never charged.
502 Upstream fetch failed — the target page or search could not be fetched (site down, unreachable, timed out, or blocked). Never charged.
Body Every error response is JSON shaped as {"detail": ...}. detail is a message string, except 402 (a JSON object) and 422 (a list of field errors).

Other endpoints

Explore the rest of the polyscrape API.

View all endpoints

Pay once. Spend when needed.

New accounts start with a free API balance. Paid balance never expires, so it can sit until your workflows need it.

Free

$0.50 to start

$0.50 free balance to start. Get an API key in seconds with no credit card.

  • Scrape, Search, and Parse
  • No credit card required
  • Perfect for a first integration
Starter

$10 one-time

Adds $10 to your API balance for steady production traffic and early automated jobs.

  • Balance never expires
  • From $0.001 per call
  • Useful for small pipelines
Pro Most popular

$100 one-time

$130 spendable balance, including a $30 bonus. The sweet spot for production workloads.

  • $100 + $30 free balance
  • Best value per workload
  • Built for automated pipelines
FAQ

Questions before you connect?

Pricing & Balance

Usage-based, charged against your prepaid balance. Scrape and parse cost $0.001 per 1,000 words of Markdown returned (minimum $0.001, capped at $0.10). Search costs $0.001 for the search plus $0.002 per result returned. Same prices across REST and MCP — no quota math, no tiers.
The whole scraping stack, handled for you: a residential proxy, a real Chrome browser fingerprint, HTML-to-Markdown conversion, built-in document parsing (PDF, Word, PowerPoint, Excel, Outlook, EPUB, CSV, XML), and caching. You send a URL, a search, or a document and get back clean, LLM-ready Markdown.
No. Your API balance never expires, so you can use it whenever your workflows need it. In the unlikely event polyscrape is ever discontinued, unused paid balance is refunded.
Paid API requests stop with a 402 until you add more balance. This keeps spend predictable and prevents unexpected charges.

API & Integration

Create and manage API keys from your account, then send your key in the X-API-Key header from your app, scripts, or internal tools.
Yes. Your dashboard shows every request, its cost, and your remaining balance, so you can track spend while building and running automated workflows.
Yes, a completed request is billable even when the answer is empty (for example a page with no readable content). Errors like 402 or 429 are never charged.
We enforce a rate limit of 10 requests per second per API key. If you exceed it, the API returns HTTP 429. Build exponential backoff (briefly pausing before retrying) into your application code.
Our support team responds to email inquiries within 1 business day. We can help with account, billing, and API integration questions.

Give your product and agents clean Markdown.

Start with a free key and $0.50 free balance, on REST, MCP, or both.