RAG Web Browser
Pricing
Pay per usage
RAG Web Browser
Web browser for OpenAI Assistants, RAG pipelines, or AI agents, similar to a web browser in ChatGPT. It queries Google Search, scrapes the top N pages, and returns their content as Markdown for further processing by an LLM. It can also scrape individual URLs. Supports Model Context Protocol (MCP).
4.4 (11)
Pricing
Pay per usage
86
Total users
2.6k
Monthly users
947
Runs succeeded
>99%
Issue response
4.7 days
Last modified
15 days ago
Actor uses Standby mode
BetaThe Standby mode is a new, lightweight method for using Actors. Instead of starting an Actor for each input and waiting for results, the Actor remains ready in the background to handle arbitrary HTTP requests, just like any web or API server.
Read moreActor URL
Send a HTTP request to the this URL, and wait for the response. To call the Actor, you need to have an Apify account. Replace <YOUR_API_TOKEN> with your API token, which you can find under Settings > Integrations in Apify Console.Learn more.
To view the specific endpoint of this Actor, go to README.
https://rag-web-browser.apify.actor?token=<YOUR_API_TOKEN>Max requests per run
maxRequestsPerActorRunnumber
The maximum number of concurrent HTTP requests a single standby Actor run can accept. If this limit is exceeded, the system starts a new Actor run to handle the request, which will take a few seconds.
Default value of this property is 14
Desired requests per run
desiredRequestsPerActorRunnumber
The desired number of concurrent HTTP requests a single standby Actor run can handle. If this limit is exceeded, the system preemptively starts a new Actor run to handle additional requests.
Default value of this property is 10
Memory (MB)
memoryMbytesnumber
The amount of memory (RAM) allocated for the Actor standby run, in megabytes. With more memory, the Actor can typically handle more requests in parallel, but the number of compute units consumed and the cost also grow.
Default value of this property is 8192
Idle timeout (seconds)
idleTimeoutSecsnumber
If a standby Actor run doesn’t receive any HTTP requests in this amount of time, the system will finish the run. When a new request comes, the system might need to start a new standby Actor run to handle it, which will take a few seconds. Higher idle timeout increases the responsiveness but increases the costs as the Actor needs to keep running longer.
Default value of this property is 300
