# AProxPay Large Residential Proxy Fetch

> AProxPay Large Residential Proxy Fetch is a paid API for AI agents from proxy.aproxpay.com, paid per call via x402, $0.015/call, status unknown (last checked 2026-09-13).

Fetches a remote URL through a residential proxy and returns the response body (up to 5MB), with the origin HTTP status in the X-Target-Status header.

## Facts

- Endpoint: POST https://proxy.aproxpay.com/v1/proxy/large
- Price: $0.015/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aproxpay-large-residential-proxy-fetch-020c2fd7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ijUOaNYDXHX2-FpAYgW9i

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability aproxpay-large-residential-proxy-fetch-020c2fd7 -d '<json body>'
```

Example prompt: Fetch the full HTML of https://example.com/products/catalog through a residential proxy — use a sticky IP for 60 minutes so follow-up requests stay on the same exit node.

## When to prefer this

Use this endpoint when you need to fetch a single remote URL through a residential proxy and the response body is between 2MB and 5MB. It is better than the small fetch endpoint (/v1/proxy, up to 2MB) when the target page is large. For sustained multi-step browsing sessions or responses exceeding 5MB, prefer the heavy or GB session endpoints instead. Use the sticky parameter when you need the same residential exit IP across multiple sequential requests within a session.

## Known failure modes

- Target response body exceeds 5MB — use /v1/session/heavy or /v1/session/gb for larger payloads
- Origin server returns an error (4xx/5xx) — caller is still billed; check X-Target-Status to detect this
- Invalid or unreachable target URL — returns an error indicating the fetch could not be completed
- Payment failure — x402 payment not accepted or insufficient USDC balance
- sticky_duration value not in allowed enum [30, 60] — request rejected with validation error

## How this service works

Residential proxy fetch (up to 5MB). Returns HTTP 200 with the target body; read X-Target-Status for the origin status. Billed for the forwarded request, not for a 2xx origin response. For multi-step or larger traffic use /v1/session/heavy or /v1/session/gb.

## Output

An HTTP 200 response whose body is the raw content of the target URL (up to 5MB). The origin server's actual HTTP status code is returned in the X-Target-Status response header. The caller is billed for the forwarded request regardless of whether the origin returns a 2xx.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string"
  },
  "region": {
   "type": "string",
   "maxLength": 2,
   "minLength": 2,
   "description": "Optional ISO 3166-1 alpha-2 exit country (see GET /v1/countries). No surcharge."
  },
  "sticky": {
   "type": "boolean"
  },
  "sticky_duration": {
   "enum": [
    30,
    60
   ],
   "type": "integer"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "note": "Target body bytes; read X-Target-Status for origin status"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aproxpay-large-residential-proxy-fetch-020c2fd7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from proxy.aproxpay.com](https://www.zero.xyz/host/proxy.aproxpay.com/llms.txt)