RAG Web Browser alternative: subimpact RAG Web Browser Lite
Both actors search Google, fetch the top results and return clean Markdown for an LLM, plus page metadata and the search result each page came from. apify/rag-web-browser lists $2.28 per 1,000 pages on the Free plan and $1.33 per 1,000 on Gold. Ours lists $1.00 per 1,000 pages, and Apify bills platform usage on top of that. Theirs runs a full browser, so pages that need scripts still load; ours fetches over raw HTTP. Both run on the Apify Store.
Prices checked 20 Nov 2026. Both actors run on Apify, so the numbers come from the same Store listing pages.
Key facts side by side
| Fact | RAG Web Browser | This API (RAG Web Browser Lite — Cheap Markdown for AI Agents) |
|---|---|---|
| Price per 1,000 pages (Free plan) | $2.28 | $1.00 |
| Higher plans (Gold) | $1.33 | $1.00 |
| Start fee per run | $0.000225 | None |
| Platform usage | Included | Paid separately |
| Users on the Apify Store | 213,874 | 1 |
| Rating | 4.7 (35 reviews) | No reviews yet |
| Last build | 16 Nov 2026 | 18 Nov 2026 |
| Pricing model | Pay per event | Pay per event |
Apify Store list prices, checked 20 Nov 2026. Platform usage 'Paid separately' means Apify bills compute on top of the event price.
Head-to-head test
one Google query, top 3 result pages as Markdown
| Measure | RAG Web Browser | This API |
|---|---|---|
| Status | SUCCEEDED | SUCCEEDED |
| Items returned | 3 | 3 |
| Run time (seconds) | 22.4 | 35.2 |
| Average filled fields per item | 3.7 | 4.0 |
| Distinct fields | 6 | 5 |
| List price of the job | $0.007065 | $0.003 |
| Measured platform usage | $0.00528 of compute, included in the price | $0.00049 of compute, paid separately |
One run each on 20 Nov 2026, same input, default memory. Small samples; your results will vary with input.
Which one to choose
When to choose RAG Web Browser
- Your targets need JavaScript, since a full browser renders those pages.
- You want the reference actor that most RAG tutorials are written against.
- You value their very large run history when picking a dependency.
- You prefer one listing that covers both search and browser fetch.
When to choose this API
- You want a lower event price per page in a RAG pipeline.
- The pages you read are mostly server rendered articles and documentation.
- You want small platform usage because no browser container starts.
- You want a standby endpoint that answers one GET without polling.
Switching from RAG Web Browser
| Their input field | Our input field | Note |
|---|---|---|
query | query | Same key and same meaning: keywords or a single URL. |
maxResults | maxResults | Same key; it is ignored when the query is a URL. |
outputFormats | outputFormats | Same key; markdown is the default on both actors. |
gl | gl | Same two letter country code for Google Search. |
hl | hl | Same two letter language code for Google Search. |
proxyConfiguration | proxyConfiguration | Same key for the proxy used to fetch the target pages. |
removeElementsCssSelector | removeElementsCssSelector | Same key for stripping navigation and cookie banners before conversion. |
Example input
{
"query": "web browser for RAG pipelines -site:reddit.com",
"proxyConfiguration": {
"useApifyProxy": true
},
"removeElementsCssSelector": "nav, footer, script, style, noscript, svg, img[src^='data:'],\n[role=\"alert\"],\n[role=\"banner\"],\n[role=\"dialog\"],\n[role=\"alertdialog\"],\n[role=\"region\"][aria-label*=\"skip\" i],\n[aria-modal=\"true\"]"
}Actor id: subimpact/rag-web-browser-lite. Paste the input above into the Apify Console and press Start.
Where each one is stronger
Where RAG Web Browser is stronger
- Much larger user base and the reference actor in this lane
- Full browser rendering, so pages that need scripts still load
- Output shape that other RAG pipelines are already written against
Where this API is stronger
- Raw HTTP with no browser, so the platform usage on your account stays small
- Same output shape as theirs, so existing pipelines need no reshaping
- Light container per page, which keeps run overhead down
Questions people ask
How do the prices compare per 1,000 pages?
apify lists $2.28 per 1,000 fetched pages on the Free plan and $1.33 per 1,000 on Gold, plus a separate search event and a small start fee. Ours lists $1.00 per 1,000 pages, and Apify bills platform usage for our actor on top of that, so the all in figure depends on the compute your run uses.
Does the output shape carry over to my pipeline?
Yes. Rows carry crawl, searchResult, metadata, markdown and, when those formats are selected, text or html, which is the shape most RAG code already reads. markdown is the default format on both actors, so a pipeline built against apify/rag-web-browser can point at this actor without reshaping records.
What happens on script heavy pages?
Pages are fetched over raw HTTP and converted with cheerio and turndown, so sites that render entirely in the browser, Reddit among them, can return thin content. Those pages are caught by the content gate instead of being billed, and crawl.requestStatus reports the failure with the HTTP status alongside.
How do I switch over?
Pass the same query, maxResults and outputFormats values to our actor and change the actor id in your API call. If you call it from an agent runtime, the standby endpoint takes a single GET with the same keys, so no run polling code is needed.
How many results can one query return?
maxResults defaults to 3 and takes up to 100, and each top organic result becomes its own row with its own markdown. When the query is a URL instead of a search term, maxResults is ignored and only that page is fetched.
Which limits should I plan around?
Only the top organic Google results are fetched, with no deep paging, and pages under 250 characters of real content are treated as empty and not charged. Country and language come from gl and hl, and the search fetch is billed as platform usage rather than as a page event.
Need a data source that is not here?
We build and run scrapers for sites that have no public API. Tell us the site, the fields and how often you need them.