# ScriptMasterLabs ACP x402 Web Fetch

> ScriptMasterLabs ACP x402 Web Fetch is a paid API for AI agents from acp-x402-discovery.onrender.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Fetches the content of any external URL via a pay-per-call HTTP proxy, settled in USDC on Base via x402 protocol.

## Facts

- Endpoint: GET https://acp-x402-discovery.onrender.com/x402/web-fetch
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/scriptmasterlabs-acp-x402-web-fetch-5d3a1793
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wZj1Zkv7rJTgnNvs-zdLa

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 scriptmasterlabs-acp-x402-web-fetch-5d3a1793
```

Example prompt: Fetch the live response from https://api.coingecko.com/api/v3/ping using a GET request and show me what it returns.

## When to prefer this

Choose this endpoint when you need to fetch live data from any external HTTP URL through a pay-per-call micropayment proxy settled in USDC on Base. It is especially useful in agent workflows where direct outbound HTTP is restricted and you need a metered, accountable web access layer. Prefer it over raw HTTP calls when x402-based cost tracking per request is required.

## Known failure modes

- Target URL is unreachable or returns an error (4xx/5xx from origin)
- Missing or malformed 'url' query parameter causes request failure
- Payment failure or insufficient USDC balance blocks the call
- x402 protocol negotiation failure prevents request execution
- Target URL rate-limits or blocks the proxy IP
- Response timeout from slow external services

## How this service works

Pay-per-call crypto, RWA, federal, SEC, and compliance APIs. Settled in USDC on Base via x402. Hyphen routes only (e.g. /x402/rwa-aggregates, /x402/gas-tracker).

## Output

The raw HTTP response body from the target URL, returned as-is from the external service. Content varies based on the target API — could be JSON, HTML, or plain text depending on what the proxied URL returns.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "url": {
       "type": "string",
       "example": "https://api.coingecko.com/api/v3/ping"
      }
     }
    }
   }
  },
  "output": {
   "properties": {
    "example": {}
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/scriptmasterlabs-acp-x402-web-fetch-5d3a1793/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from acp-x402-discovery.onrender.com](https://www.zero.xyz/host/acp-x402-discovery.onrender.com/llms.txt)