# APEX Faucet Web Reader

> APEX Faucet Web Reader is a paid API for AI agents from apexfaucet.xyz, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-02).

Fetches and returns structured web content or token data from provided URLs, returning metadata like token price, holder count, and symbol.

## Facts

- Endpoint: GET https://apexfaucet.xyz/api/x402/web-read?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apex-faucet-web-reader-51d9e03c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NnAnce_EIRPngMi1LjqCo

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 apex-faucet-web-reader-51d9e03c
```

Example prompt: Can you pull the latest APEX token data from apexfaucet.xyz — I want to see the current USD price and how many holders there are?

## When to prefer this

Choose this endpoint when you need to read structured web content or token metadata specifically from apexfaucet.xyz pages, especially for APEX token price, holder count, or screener data. Useful when you want a pay-per-call, no-signup approach to fetching crypto token data without building a dedicated integration.

## Known failure modes

- Invalid or malformed URLs return an error response with ok:false
- More than 10 URLs in the comma-separated list may be rejected
- Network timeout or unreachable URL results in failure
- Payment failure via x402 protocol prevents data retrieval
- Empty or missing 'urls' parameter triggers a validation error

## How this service works

Web page reader: up to 10 web pages as clean text in one call. Read web pages as clean text: pass ?urls=a.com,b.com (up to 10 in one call) and get each page title, meta description and readable body with script, style, nav and footer stripped, plus the final URL after redirects, the content type, the byte count and whether it was truncated. STATED PLAINLY BECAUSE IT CHANGES WHAT YOU ARE BUYING: this is a fetch, NOT a browser.

## Output

Returns a JSON object with an 'ok' boolean, a 'data' object containing token metadata (symbol, holder count, USD price), a 'paid' number indicating the amount paid, a 'tier' string describing the pricing tier, and an 'asset' string for the payment asset used.

## 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",
    "queryParams"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "urls"
     ],
     "properties": {
      "urls": {
       "type": "string",
       "description": "Comma-separated URLs, up to 10."
      }
     }
    }
   }
  },
  "output": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "schema": {
  "type": "object",
  "properties": {
   "ok": {
    "type": "boolean"
   },
   "data": {
    "type": "object"
   },
   "paid": {
    "type": "number"
   },
   "tier": {
    "type": "string"
   },
   "asset": {
    "type": "string"
   }
  }
 },
 "example": {
  "ok": true,
  "data": {
   "symbol": "APEX",
   "holders": 9902,
   "priceUsd": 0.0000041
  },
  "paid": 0.01,
  "tier": "cheap",
  "asset": "USDC"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/apex-faucet-web-reader-51d9e03c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from apexfaucet.xyz](https://www.zero.xyz/host/apexfaucet.xyz/llms.txt)