Skip to main content
POST /v1/quote checks the credit price for a scrape without fetching the page or charging credits. Send the same body you would send to /v1/scrape. The endpoint requires an API key with the scrape scope.
The response’s data contains credits, free, and reason. A supported scrape currently quotes one credit with free: false and reason: "fresh_fetch". A quote does not reserve credits or guarantee that the source page will succeed.

​
Current credit rules

A source page’s 404 is a billable answer. Credits are reserved before a request and released when its outcome is unbilled. Browser rendering and currently available extra formats have no surcharge. Every scrape fetches fresh content; there is no free cached-repeat tier. All organization keys spend from the shared organization balance. The dashboard shows the current balance and usage; Activity shows charges and released reservations for individual requests.

​
Plans and credit purchases

See Billing and plans for monthly allowances, prepaid credits, subscriptions, and automatic recharge. Billing changes require an organization owner or admin. Use an Idempotency-Key on scrape and map requests you may retry. See retries and idempotency to avoid duplicate work and charges. A successful quote does not create a reservation or a price lock. Another key can spend the balance before your scrape runs. An insufficient available balance returns 402; inspect Billing before retrying.