Pricing is calculated at the end of the month based on the number of requests made with your API token. It's calculated from the following tiers:

Total Requests in a MonthMonthly Price (USD)
under 500$0 (free)
under 20,000$9
under 100,000$40
per 1,000,000$360 ($0.00036 per request)
per 10,000,000$3,240 ($0.000324 per request)
a request is defined as any HTTP request made to the API endpoint: - but the official middlewares strive to only make requests for HTML pages (thus you can predict your approximate usage based on number of monthly sessions on your website)
* EU customers: Prices inclusive of VAT, where applicable


  • Example 1: 19,999 requests would cost $9
  • Example 2: 20,001 requests would cost $40
  • Example 3: 100,001 requests would cost $36 (making over 100,000 requests qualifies for the variable rate plan)
  • Example 4: 1,500,000 requests would cost $540

Billing is automatic at the end of the cycle

  • The cycle is 30 days long and starts when you add your credit/debit card
  • If the credit/debit card on record fails/rejects the payment, we'll try 2 more times (and send you an email indicating failed payment) over the next few days. After the 3rd failure, your service will be converted into the "free tier" which means it will be rate limited to 500 requests total per month.
  • We send a receipt with a summary of your requests via email after a successful payment. After this, corresponding a PDF invoice (marked "paid") is available for download when you sign-in to

Reduce costs

  • cache API responses locally (easy with our Node.js lib or nginx config)
  • use a "botsOnly" config so only googlebot, twitterbot etc. user-agents are proxied through

Rate limiting

  • API requests without an API token are rate-limited: 15 requests per hour and/or 500 per month
  • API requests with an API token but no or invalid billing will be rate-limited 500 per month (but not per hour)
  • API requests with an API token and valid billing information are not rate-limited

Burst requests and capacity

  • can tolerate unexpected bursts of up to 100 req/sec. If that burst is sustained for more than 3 minutes, the system autoscales to meet the load. This autoscaling process takes approximately ~3 minutes.
  • If there's a sudden burst of traffic exceeds 100 req/sec, the requests beyond 100/sec will be queued. It will take approximately 6 minutes total to address that queue. Historically there's only ever been queuing when a new large customer joins without reaching out beforehand.
  • To tolerate any potential capacity issues may have, set your request timeout to 6 minutes.
  • Email us if you have any capacity concerns. If you have complicated burst or seasonal requirements, we can program the autoscaler to provision capacity on a schedule.
Hosted on