# true402 Web Screenshot API

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

Captures a screenshot of any web page by URL, returning a rendered image via a pay-per-call HTTP 402 micropayment endpoint.

## Facts

- Endpoint: POST https://true402.dev/api/v1/screenshot
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/true402-web-screenshot-api-7c6f50d1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_E_QpWlRSfW-SzwzPKy28A

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-screenshot-api-7c6f50d1 -d '<json body>'
```

Example prompt: Can you take a screenshot of https://example.com at 1280px wide and capture the full page?

## When to prefer this

Choose this endpoint when you need a quick, pay-per-call web screenshot without committing to a subscription-based screenshot service. Ideal for AI agents that need occasional visual captures billed in USDC micropayments, especially in x402-compatible wallet-identity workflows. Prefer this over browser automation tools when you want a simple REST call with no infrastructure overhead.

## Known failure modes

- Invalid or unreachable URL returns an error response
- Viewport width outside 320–1920 range may be rejected or clamped
- Full-page height exceeding 8000px is clamped automatically
- Payment failure via HTTP 402 if wallet has insufficient USDC balance
- Timeout if the target page takes too long to load
- Non-http/https URLs are rejected

## How this service works

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

## Output

Returns a rendered image of the requested web page. The response body contains the screenshot data (likely as a base64-encoded image or binary), captured at the specified viewport width, with full-page mode optionally extending the capture up to 8000px tall.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "url"
 ],
 "properties": {
  "url": {
   "type": "string",
   "description": "The page URL to render (http/https)"
  },
  "width": {
   "type": "number",
   "description": "Viewport width 320–1920; default 1280"
  },
  "fullPage": {
   "type": "boolean",
   "description": "Full-page capture (height clamped to 8000px); default false"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string"
  },
  "bytes": {
   "type": "number"
  },
  "width": {
   "type": "number"
  },
  "height": {
   "type": "number"
  },
  "finalUrl": {
   "type": "string"
  },
  "png_base64": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/true402-web-screenshot-api-7c6f50d1/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)