Execution response
| Field | Meaning |
|---|---|
| ok | Whether the provider response was successful. |
| status | The upstream HTTP status. |
| body | Returned content as a string. |
| contentType | Media type reported for the returned body. |
| format | Requested output format. |
| credits | Reported provider charge, or null when not reported. |
| elapsedMs | Elapsed execution time in milliseconds. |
| bytes | UTF-8 size of the returned body. |
| truncated | True when the upstream body exceeded the response bound. |
| requestId | Identifier for this execution. |
Check both status layers
The service can return a valid JSON envelope even when the upstream result has ok: false. Check the envelope’s status and ok; a successful HTTP transport alone does not prove the target returned usable content.
Handle the body by format
HTML is page markup, extended JSON contains provider page data, Markdown contains transformed text, and AI extraction returns provider-generated structured content. Validate the actual body before feeding it into an application.
Treat truncation explicitly
The service reads at most 2,000,000 upstream body bytes. If truncated is true, the body may be incomplete, including invalid JSON. Do not treat it as a complete document.
Dashboard preview
The dashboard HTML preview is static and sandboxed. Active scripts, navigation and external resources are removed or blocked. Use the code view or download the raw response when inspecting actual returned text.