Yes. The request reached the network and the upstream did the work, so it counts as one trip.

Does this affect binary responses?

Binary responses come back as base64 with a byte count, so they are subject to the same allowance. Large files belong in your own object storage, not in a relay response.

502 · response_too_large

response_too_large: the target returned more than the relay accepts

response_too_large means the upstream answered, but the body exceeded the per-call allowance, so the relay could not hand it back as a single envelope. The attempt reached the network and is charged as a trip.

Common causes

An endpoint that returns a full collection instead of a page.
A download endpoint returning a file rather than metadata.
An error path that dumps a large HTML page instead of a short JSON error.

How to fix it

01Ask the upstream for a page or a filtered result set.
02Request only the fields you need with the target API's own parameters.
03For genuine file downloads, fetch metadata here and stream the artefact from your own storage.

What it looks like

response_too_large

# ask for a page instead of the whole collection
{
  "url": "https://api.example.com/v1/items?limit=50&fields=id,name",
  "method": "GET",
  "timeout_ms": 10000
}

Every error code

blocked_target insufficient_trips invalid_key rate_limited upstream_timeout payload_too_large response_too_large dns_failure account_frozen

Questions about this

Try it with 5,000 free trips.

No card, no subscription, and the balance never expires.

Create an account Read the docs