# true402 Web Extract

> true402 Web Extract is a paid API for AI agents from true402.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-13).

Extracts content from a web page by URL, payable per call via HTTP 402 with USDC.

## Facts

- Endpoint: POST https://true402.dev/api/v1/web-extract
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/true402-web-extract-c4e8f863
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ntr9VDS0ChVYIENWKQ9rP

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 true402-web-extract-c4e8f863 -d '<json body>'
```

Example prompt: Can you extract the content from https://example.com/article — I want to read what's on that page.

## When to prefer this

Use this endpoint when you need to extract readable content from a public web page and want to pay per call with USDC via the x402 protocol, without a subscription. Particularly useful for AI agents operating in machine-native payment environments where wallet-based micropayments are preferred over API key billing.

## Known failure modes

- URL is unreachable or returns a non-200 HTTP status — extraction fails
- URL points to a JavaScript-heavy SPA that requires browser rendering — content may be incomplete or empty
- Invalid or malformed URL provided — validation error returned
- Payment fails or wallet has insufficient USDC — HTTP 402 not resolved, call not executed
- Rate limiting or bot protection on target site blocks extraction

## How this service works

The machine-native marketplace. Wallet = identity. Pay per call with HTTP 402.

## Output

Returns an object containing the extracted content from the target webpage, including parsed text and possibly structured data from the page.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "url"
 ],
 "properties": {
  "url": {
   "type": "string",
   "description": "The page URL to extract (http/https)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ok": {
   "type": "boolean"
  },
  "url": {
   "type": "string"
  },
  "text": {
   "type": "string",
   "description": "Clean readable text"
  },
  "links": {
   "type": "array",
   "description": "{ href, text } in document order"
  },
  "title": {
   "type": "string"
  },
  "markdown": {
   "type": "string",
   "description": "Light markdown rendering"
  },
  "wordCount": {
   "type": "number"
  },
  "description": {
   "type": "string"
  },
  "hiddenContent": {
   "type": "object",
   "description": "Content the page declared invisible, stripped from text/markdown before you receive them. { count, samples[], note }. A non-zero count is a strong signal about the page. Does NOT cover colour-contrast hiding (white-on-white), which needs rendering to judge."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/true402-web-extract-c4e8f863/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from true402.dev](https://www.zero.xyz/host/true402.dev/llms.txt)