browser-render is useful when a page only shows its content after JavaScript runs. That includes pricing pages, status pages, dashboards, and client-side product listings.

For a repeat check, keep the prior response in your own workflow and call the same URL again. Compare final_url, title, bytes, and the returned html. Those fields make a redirect, page-title change, or rendered-DOM change visible without treating a raw HTTP fetch as the page state. 

{
  "url": "https://example.com/status",
  "wait_ms": 1500
}

Use wait_ms only when the page has late client-side content. It accepts up to 10 seconds. Set screenshot to true when your workflow needs a PNG instead of HTML.

The endpoint accepts public HTTP(S) URLs and rejects private-network targets. A dependency problem returns a structured 424 response with dependency: "browser-runtime", so a caller can retry later or keep its previous page state.