Home / Web scraping APIs / String
String pricing
100,000 JavaScript-rendered pages a month cost $170.00 on String's Starter plan.
Checked Oct 24, 2026 on String's own pricing page
- Starter
- Growth
Your workloadType any volume or pick one on the scale, change the success rate or copy a link to this jobEdit
The volumes on the scale were priced in advance from published vendor rules, and any other volume you type is worked out in your browser by the same rules. Nothing is sent anywhere and no account is needed.
Every String plan
| Plan | Covers | Billed monthly | Billed yearly, per month | Included | Past the allowance | Throughput |
|---|---|---|---|---|---|---|
| Starter fits your volume | 10K to 100K pages | $20.00 | not offered | none: the fee buys no usage | every request, at this plan's rates, on top of the fee | up to 60 requests a second |
| Growth | 250K to 1M pages | $100.00 | not offered | none: the fee buys no usage | every request, at this plan's rates, on top of the fee | up to 60 requests a second |
Your job
What String bills you for
What you pay
About this price and its sources
String's Web Access API bills a $20 or $100 monthly fee plus every successful request at $0.20 to $6.00 per 1,000, set by the fetch path and proxy String picks for each site.
Cite this price
100,000 JavaScript-rendered pages a month cost $170.00 on String's Starter plan. Price read from https://usestring.ai/pricing on Oct 24, 2026. Scraping API Prices, https://scrapingapiprices.com/string-pricing
How the bill builds up
- Base rate$0.0003per request
- → JavaScript rendering$0.0015per request; replaces the base rate
- × Premium proxyNot requiredNot part of this workload
- ÷ Success rate1Failed requests are not billed
- = Billed units per page you keep1 requestFrom this bill’s calculation
- = per 1,000 pages kept$1.70Starter, billed monthly
Credits and multipliers
JavaScript rendering
Billed failures
Success rate
Concurrency
Free tier
Renews monthly The bill at your volume
100,000 pages per month · $170.00
Read the chart as a table
| Volume | Bill | Offer |
|---|---|---|
| 10,000 | $35.00 | Starter |
| 25,000 | $57.50 | Starter |
| 50,000 | $95.00 | Starter |
| 100,000 | $170.00 | Starter |
| 250,000 | $350.00 | Growth |
| 500,000 | $600.00 | Growth |
| 1,000,000 | $1,100.00 | Growth |
Follow each billed unit
-
Successes you want
100,000 pages
Your stated workload. Every vendor on this site is priced against this same number.
- × 1
Attempts you are billed for
100,000 requests
String does not bill failed fetches, so failures cost nothing here.
- × 1
What the meter counts
100,000 requests
One attempt is one billed unit for this workload.
- =
Cash per month
$170.00 /mo
Starter: the cheapest way to buy this volume, not just the first plan big enough.
Bars share one linear scale across the 3 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
100,000 pages divided by 95% success → 100,000 requests → Starter $170.00/mo = $1.70 per 1,000 pages kept
What makes it cost more
One page is not always one billed unit. These are String's published charges for each kind of work; failed requests are not billed. Where a rate depends on the plan, the row names the plans that pay it.
| Work | Costs | Per | Source |
|---|---|---|---|
| A standard page | $0.0003 on Starter$0.0002 on Growth | request | source |
| JavaScript rendering | $0.0015 on Starter$0.001 on Growth | request | source |
| Premium proxies | $0.003 on Starter$0.002 on Growth | request | source |
| JavaScript rendering with premium proxies | $0.006 on Starter$0.004 on Growth | request | source |
Limits and terms
What String publishes beyond the price: the limits a job runs into and the terms that change what a plan is worth. Each line links the page it comes from and the day it was read.
Speed, concurrency and sessions
- No concurrency cap on any plan; throughput is 60 requests a second with a burst allowance of 3,600 requests, the same on Starter and Growth. source, read Oct 22, 2026
Credits, renewal and billing
- The pricing page says "Credits roll over" and "Unused credits roll over", and its FAQ "You don't buy credits up front", while the billing docs describe a flat fee with usage billed on top, paid from a "prepaid balance"; none says how that balance is filled. source, read Oct 23, 2026
Cheaper for this job
Same 100,000 JavaScript-rendered pages a month at a 95% success rate, ranked by what you would actually be billed. APIs without a full public price aren't ranked. Showing 6 of 20; see the rest.
What String does not publish
- Which fetch path and proxy class String picks for a given target: the bill for a page moves between $0.30 and $6.00 per 1,000 on Starter by that choice.
- Whether the 5,000 free requests renew each month.
- The AI extraction fee per request.
- How the prepaid balance the docs mention is filled, when the FAQ says no credits are bought up front.
What String is
String sells a Web Access API for developers and AI agents: fetch any URL as clean Markdown or structured data, search the web, run a remote browser over a WebSocket, and map a site, with an MCP server for Claude, Cursor and other clients (String pricing and billing docs, checked Oct 22, 2026).
How billing works
Each plan has a flat monthly fee, $20 for Starter or $100 for Growth, “with usage billed per request on top”: the fee buys no requests. A request is billed by the path String uses to get the page and the proxy it needs. On Starter a plain fetch through the standard proxy costs $0.30 per 1,000, a fetch through the premium (residential) proxy $3.00, a page rendered in a real browser $1.50, and a browser page through the premium proxy $6.00; Growth cuts each rate by a third, to $0.20, $2.00, $1.00 and $4.00. Search is $1.50 per 1,000 on Starter and $1.00 on Growth. A remote browser session is billed instead on time, $0.12 an hour, and bandwidth, $10.00 per GB through the premium proxy or $5.00 through the standard one (String pricing and billing docs, checked Oct 22, 2026).
Failed requests are not billed, with two exceptions the docs name: a 502 that carries an x-billed-request-type header, and a request with custom headers that the site blocks. A page the site answers with a 404 still comes back to you, so it is billed (billing docs, checked Oct 22, 2026).
Before you buy
String, not you, picks the fetch path and the proxy for each site, so the same page can cost $0.30 or $6.00 per 1,000 on Starter. At 100,000 pages a month that choice alone moves the bill from $50, if every page is a plain fetch on Starter, to $500, if every page goes through the browser and the premium proxy, on Growth (Starter would be $620) (String pricing, checked Oct 23, 2026). The bill here prices a JavaScript page at the browser rate; test a sample of your own sites and read the requestType each response reports before you budget a month. Growth pays for itself once usage at Starter’s rates passes $240 a month, which is 160,000 browser pages. AI extraction to a JSON schema adds a fee per request that grows with the page and the schema, and no rate is published. The free 5,000 standard requests come with no stated renewal. The pricing page says unused credits roll over, and its FAQ says you don’t buy credits up front; the docs describe the fee as flat with usage on top and speak of a prepaid balance that requests are paid from, without saying how it is filled.
Who it suits
String suits teams that would rather not choose a proxy or a renderer per site and want blocked requests to cost nothing, from one key that also covers search and a remote browser. At high volume on plain pages its per-request rates are low, but the fee is paid on top, so at a few thousand pages a month the fee is most of the bill; the calculator sets String’s bill for your job against every other scraping API.