Quick answer
What has changed at WebReaderAPI?
On 22 October 2026, WebReaderAPI published its website, documentation, prices and policies. The API itself is not open yet; its launch will be the next entry on this page. Prices start at $3.75 for 10,000 pages and fall to $0.07/1K pages on the largest pack.
22 October 2026: site and documentation published
- Website, prices and policies went online: pricing, terms, privacy, acceptable use and refunds.
- Documentation for the
/read,/batch,/crawland/creditsendpoints, with code for Python, Node.js and curl. - Crawler rules published on the bot page: user agent
WebReaderAPI/1.0 (+https://webreaderapi.com/bot/), robots.txt tokenWebReaderAPI, respect forai-input=no. - API status: launch pending. Until the launch entry appears here, no API key can be bought.
What counts as a change worth a dated entry?
Anything a customer or a site owner could rely on:
- a new endpoint, parameter or response field;
- a field renamed or removed (which only happens in a new version of the API, such as
/api/v2/); - a price, a credit rule or a refund rule;
- a change to how the crawler identifies itself or treats robots.txt;
- an incident that affected requests, with its time window.
How are price changes handled?
A new price applies to packs bought after it is published here. Credits you already hold keep their value: they are counted in pages, not in dollars, and Prepaid credits never expire: unused pages stay on your account until you use them.
How stable is version 1 of the API?
Within version 1, we may add fields and parameters, never rename or remove them. Code that reads the fields documented in the response format keeps working. A breaking change would go to a new version, announced here before it goes live.
How do I follow the changes?
Check this page, or read its Markdown version, which llms.txt lists with the other pages of the site. Each entry keeps its date, so you can see what changed since your last visit. Questions go to [email protected].