# AProxPay Residential Proxy Fetch (Standard, up to 2MB)

> AProxPay Residential Proxy Fetch (Standard, up to 2MB) is a paid API for AI agents from proxy.aproxpay.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-14).

Fetches a target URL through a residential proxy and returns the response body (up to 2MB), billed per request regardless of origin status code.

## Facts

- Endpoint: POST https://proxy.aproxpay.com/v1/proxy
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aproxpay-residential-proxy-fetch-standard-up-to-2mb-d6e34faf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xI4YoWz0mAVFDqLXA_7sG

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-residential-proxy-fetch-standard-up-to-2mb-d6e34faf -d '<json body>'
```

Example prompt: Fetch the page at https://example.com/products through a residential proxy and give me the response body — use a sticky session for 30 seconds so follow-up requests stay on the same IP.

## When to prefer this

Use this endpoint when you need to fetch a single URL (up to 2MB response) through a residential IP, especially when the target site blocks datacenter traffic. Prefer this over session pass endpoints for low-volume fetches (fewer than 17 requests per session). If the response body exceeds 2MB, use the /v1/proxy/large sibling endpoint. If you need sustained high-volume fetching, a session pass is more cost-effective.

## Known failure modes

- Response body exceeds 2MB limit — use /v1/proxy/large instead
- Origin server returns an error (check X-Target-Status header for the real status)
- Target URL is unreachable or times out via residential network
- Payment/billing failure if USDC balance is insufficient
- Invalid sticky_duration value — must be 30 or 60
- Malformed or missing URL field in request body

## How this service works

Residential proxy fetch (up to 2MB). 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 larger responses use /v1/proxy/large; at >17 requests a session pass is cheaper.

## Output

Returns HTTP 200 with the target page body (up to 2MB). The actual origin HTTP status code is in the X-Target-Status response header. The caller is billed $0.003 USDC per request made, regardless of whether the origin returned a 2xx response.

## 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-residential-proxy-fetch-standard-up-to-2mb-d6e34faf/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)