# Web Content Verification API

> Web Content Verification API is a paid API for AI agents from idask-37-255-229-96.run.pinggy-free.link, paid per call via x402, $0.25/call, status unknown (last checked 2026-10-21).

Verifies a URL's content and optionally tests a specific claim against the page, returning support status and cross-references

## Facts

- Endpoint: POST https://idask-37-255-229-96.run.pinggy-free.link/verify?utm_source=zero.xyz
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/web-content-verification-api-5be79a28
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-iBLr6Grk4GuKY8DfhR88

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 web-content-verification-api-5be79a28 -d '<json body>'
```

Example prompt: Can you verify whether the page at https://example.com/article actually supports the claim that 'electric vehicles reduce CO2 emissions by 50%'?

## When to prefer this

Choose this endpoint when you need to verify whether a specific web page actually supports a given claim or statement, especially for fact-checking, citation validation, or content auditing workflows. Prefer this over general web scraping when the goal is binary claim validation with a structured receipt and cross-reference output rather than raw content extraction.

## Known failure modes

- URL is unreachable or returns an error (404, 500) — verification cannot proceed
- Claim provided does not match any content on the page — 'supported' returns negative or unsupported
- URL points to non-textual content (PDF, image, video) that cannot be parsed for claim verification
- Network timeout when fetching the target URL
- Malformed URL input causes validation error before request is made

## How this service works

Website hosted for free through pinggy.io&gt;
    &lt;meta name=

## Output

Returns the original URL, a receipt object confirming the verification transaction, a 'supported' string indicating whether the claim is backed by the page content, and an array of cross-reference objects with supporting evidence or related links.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "url"
 ],
 "properties": {
  "url": {
   "type": "string"
  },
  "claim": {
   "type": "string",
   "description": "optional claim to test against page content"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "url"
 ],
 "properties": {
  "url": {
   "type": "string"
  },
  "receipt": {
   "type": "object"
  },
  "supported": {
   "type": "string"
  },
  "crossReferences": {
   "type": "array",
   "items": {
    "type": "object"
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/web-content-verification-api-5be79a28/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from idask-37-255-229-96.run.pinggy-free.link](https://www.zero.xyz/host/idask-37-255-229-96.run.pinggy-free.link/llms.txt)