The agent sends an HTTP request to the Browserless PDF endpoint with either a URL or raw HTML content. You can configure page format, margins, headers, footers, and print background settings. The API renders the page in headless Chrome, executes all JavaScript, and returns the PDF binary. Generation typically completes within two seconds.

Yes. The Take Screenshot endpoint supports full-page capture that scrolls the entire page height. You can also define clip coordinates for partial captures targeting specific page regions. Output supports PNG or JPEG with configurable quality. Screenshots of standard pages complete in roughly one second.

Tars requires your Browserless API token, which you generate from your Browserless account dashboard. This single token authenticates all REST API calls including PDF generation, screenshots, scraping, content retrieval, custom functions, file downloads, and unblock operations. No OAuth flow is needed.

No. Tars retrieves PDFs, screenshots, and scraped data from Browserless in real-time but does not persist these outputs on its servers. The Browserless API returns content directly in HTTP responses. You can configure your agent to forward files to your preferred cloud storage or messaging platform.

The Unblock endpoint uses stealth browser sessions with advanced fingerprint masking to bypass CAPTCHA challenges and bot detection services like Datadome. It can return rendered HTML content, session cookies, and page screenshots. For heavily protected sites, configure wait conditions and appropriate timeout values for best results.

Yes. The Execute Custom Function endpoint accepts ESM module code with a default export function. Pass dynamic data through context objects. Your scripts run on managed Chrome infrastructure without local browser dependencies. This enables complex workflows like form submissions, multi-step navigation, and data transformation beyond what standard endpoints offer.

Local Chrome requires server provisioning, memory management, dependency updates, and crash recovery. Browserless provides a managed pool of headless browsers with built-in scaling, load balancing, and session isolation. Tars adds a conversational layer so non-technical users can trigger browser operations without writing code or maintaining infrastructure.

Yes. Both the Fetch HTML Content and Scrape Content endpoints wait for JavaScript execution before extracting data. Configure waitForSelector to target specific DOM elements, waitForTimeout for time-based delays, or waitForEvent to listen for page load signals. The API returns fully rendered content from React, Angular, or Vue applications.