Documentation Index
Fetch the complete documentation index at: https://noorle.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Browser is a stateless rendering service. Each request is independent — render a web page to screenshots, structured HTML, or extract data, with no session persistence between calls.
Browser vs Computer: Browser is stateless — each call renders a fresh page with no memory of previous requests. If you need persistent browser sessions (logged-in state, multi-step navigation, cookies preserved across calls), use the Computer capability with its browser subsystem enabled. Key Features
- Screenshot Rendering - Capture web page screenshots
- Structured Data - Extract HTML and page text
- JavaScript Support - Pages with dynamic content fully rendered
- Custom Viewport - Control screen resolution
- Element Interaction - Click, scroll, form fill (advanced)
- Network Isolation - Secure rendering environment
How to Enable
For Agents
- Agents > Select Agent > Settings > Capabilities
- Attach Browser
For MCP Gateways
- Gateways > Select Gateway > Capabilities
- Attach Browser
Usage Examples
Capture Screenshot
Render https://example.com to a screenshot
- PNG image of rendered page
- Page title and URL
- Viewport dimensions
Get the text content from https://news.example.com/article
- Full page text (markdown formatted)
- Headings and structure
- Links and metadata
Capture Dynamic Page
Screenshot the dashboard at https://app.example.com/dashboard
Rendering Options
Screenshot
Captures visual rendering of the page:
{
"url": "https://example.com",
"action": "screenshot",
"viewport": {
"width": 1280,
"height": 720
}
}
{
"url": "https://example.com",
"action": "html"
}
{
"url": "https://example.com",
"action": "text"
}
Configuration
Optional gateway specifications:
{
"browser": {
"timeout_seconds": 30,
"viewport_width": 1280,
"viewport_height": 720,
"javascript_enabled": true,
"timeout_wait_until": "networkidle"
}
}
| Setting | Default | Effect |
|---|
timeout_seconds | 30 | Max render time |
viewport_width | 1280 | Pixel width |
viewport_height | 720 | Pixel height |
javascript_enabled | true | Execute JS |
timeout_wait_until | ”networkidle” | When to capture |
Advanced Features
Wait Conditions
Control when rendering completes:
- load - DOM loaded
- domcontentloaded - Initial HTML parsed
- networkidle - Network quiet (default)
Set request headers:
{
"headers": {
"User-Agent": "Custom Agent",
"Authorization": "Bearer token"
}
}
Cookies
Include cookies in request:
{
"cookies": [
{
"name": "session",
"value": "abc123"
}
]
}
Common Use Cases
Price Monitoring
Screenshot product pages to track price changes
- Render competitor pages
- Extract prices
- Compare with your prices
Content Scraping
Extract article text from news sites
- Get page text
- Parse structure
- Extract key information
Visual Testing
Screenshot app at different breakpoints
- Render at desktop size
- Render at mobile size
- Compare visuals
Get structured data from tables and lists
- Get HTML
- Parse with Code Runner
- Extract data
Resource Limits
| Limit | Value | Notes |
|---|
| Timeout | 30 seconds | Configurable per request |
| Default Viewport | 1280 × 720 | Configurable |
| JavaScript | Enabled | Fully renders dynamic content |
Cost
For current pricing details, see Pricing.
Monitor in Account > Usage dashboard.
Browser vs Computer Browser
| Feature | Browser (this page) | Computer Browser Subsystem |
|---|
| State | Stateless — each call is independent | Stateful — session persists across calls |
| Sessions | No cookies/login between requests | Cookies, login state, tabs preserved |
| Multi-step | Single-page operations only | Navigate across pages, fill multi-step forms |
| Availability | Agents and MCP gateways | Agents only |
| Setup | Attach Browser capability | Attach Computer + enable browser_enabled |
| Use case | Screenshot, scrape, extract data | Automate web apps, logged-in workflows |
Limitations
- Stateless: no session persistence between requests
- Cannot maintain logged-in state (use Computer for that)
- Cannot interact with complex multi-step JS applications
- Some sites may block automated rendering
- Timeouts on very slow pages
Best Practices
Use Screenshots for Visual Content
Screenshots best for:
- Product pages
- Design verification
- Visual inspection
- Chart/graph capture
Text/HTML better for:
- Article content
- Structured data
- Link extraction
- SEO information
Set Appropriate Timeouts
{
"timeout_seconds": 30,
"timeout_wait_until": "networkidle"
}
Handle Errors Gracefully
Some pages may fail to render. Implement retry logic.
Troubleshooting
Screenshot is blank
- Page loading failed
- Wrong viewport size
- Page requires authentication
- Try increasing timeout
Timeout error
- Page too slow
- Waiting for external resources
- Reduce timeout or increase wait condition
- Simplify the URL
Access denied
- Site blocking automated access
- Use different User-Agent header
- Try at different time
Content missing
- Content loaded via JavaScript asynchronously
- Increase timeout
- Use “load” wait condition instead of “networkidle”
Privacy & Security
- Rendering is isolated per request
- No cookies stored between requests
- Headers/auth not retained
- Rendered pages not logged
- Results deleted after delivery
Next Steps
