Stream a response the browser fetches
Send an HTTP request from the browser itself, like fetch, and stream the response body back as it arrives, of any size and with bounded memory at every hop; a slow reader slows the upstream read. The upstream status is in BCTRL-Fetch-Status and its headers (JSON) in BCTRL-Fetch-Headers. A failure before the first byte is an error response; a failure after it aborts the stream, and the Run’s completion Event records unknown. Human control blocks it.
Authentication
Use Bearer <api-key>.
Path parameters
Headers
Optional retry key for this billable operation. Reusing the same key with the same request replays its stable outcome; credential-bearing results may be freshly issued for the same principal. Reusing it with a different request returns 409.
Query parameters
Request
Response headers
The upstream response headers as a JSON object (at most 16 KiB; larger header sets are cut to the headers that fit).
The upstream Content-Type.
Evaluated policy limit; zero when no finite policy was evaluated.
Remaining policy budget; zero when no finite policy was evaluated.
Seconds until reset; zero when no finite policy was evaluated.

