Capture a screenshot, PDF, HTML, markdown, links, or AI-structured data from a URL using Cloudflare Browser Rendering's stateless REST Quick Actions

Documented steps

1. Note the naming split before you build the URL: the product docs are now at https://developers.cloudflare.com/browser-run/ ('Browser Run, formerly Browser Rendering'), but the REST path segment is still 'browser-rendering'.
2. Base URL shape: https://api.cloudflare.com/client/v4/accounts/{account_id}/browser-rendering/{action}
3. Quick Action endpoints are /content (HTML), /screenshot, /pdf, /markdown, /snapshot (multiple formats at once), /accessibilityTree, /scrape (scrape elements), /json (AI structured extraction), /links, and /crawl, plus GET /crawl/{job_id} and DELETE /crawl/{job_id} to manage async crawl jobs.
4. Auth: an API token with the 'Browser Rendering - Edit' permission, sent as 'Authorization: Bearer {api_token}'.
5. Every request must supply either 'url' or 'html' in the JSON body as the content source.
6. Working example: curl -X POST 'https://api.cloudflare.com/client/v4/accounts/<accountId>/browser-rendering/screenshot' -H 'Authorization: Bearer <apiToken>' -H 'Content-Type: application/json' -d '{"url":"https://example.com"}' --output screenshot.png
7. Common optional body fields across endpoints: viewport (width, height, deviceScaleFactor), gotoOptions (waitUntil, timeout), cookies, authenticate (HTTP basic auth), selector (CSS scope), userAgent, and screenshotOptions (fullPage, quality, type, omitBackground) for /screenshot.
8. Handle 429 responses by reading the Retry-After header and backing off rather than retrying immediately.
9. From inside a Worker, call env.BROWSER.quickAction() with a browser binding instead of making an outbound REST request.
10. Verified reference pages: https://developers.cloudflare.com/browser-run/quick-actions/ and https://developers.cloudflare.com/browser-run/quick-actions/screenshot-endpoint/