# Web Content Verification & Claim Checker

> Web Content Verification & Claim Checker is a paid API for AI agents from eymqg-159-89-4-32.run.pinggy-free.link, paid per call via x402, $0.25/call, status down (last checked 2026-09-19).

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

## Facts

- Endpoint: POST https://eymqg-159-89-4-32.run.pinggy-free.link/verify
- Price: $0.25/call
- Payment: x402
- Status: down
- Last checked: 2026-09-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/web-content-verification-claim-checker-9338a261
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5o9edzp2VipcchKmdChcu

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-claim-checker-9338a261 -d '<json body>'
```

Example prompt: Can you verify whether this URL actually supports the claim that 'the Eiffel Tower is 330 meters tall'? The page is https://en.wikipedia.org/wiki/Eiffel_Tower — I want to know if it's supported, and any cross-references the page has.

## When to prefer this

Choose this endpoint when you need to verify whether a specific web page actually supports a stated claim, or when you need cross-references extracted from a page to fact-check information. Prefer it over generic web scraping when the goal is claim validation with a structured supported/not-supported verdict rather than raw content extraction.

## Known failure modes

- URL is unreachable or returns a non-200 status — verification cannot proceed
- Page content is behind a login wall or paywall — content inaccessible for analysis
- Claim is ambiguous or too vague to match against page content — 'supported' may be inconclusive
- URL returns dynamic JavaScript-rendered content that cannot be parsed — incomplete analysis
- Invalid URL format in input — request rejected

## How this service works

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

## Output

Returns the verified URL, a payment receipt object, a 'supported' string indicating whether the page content supports the optional claim, and an array of cross-reference objects found on or related to the page.

## 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-claim-checker-9338a261/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from eymqg-159-89-4-32.run.pinggy-free.link](https://www.zero.xyz/host/eymqg-159-89-4-32.run.pinggy-free.link/llms.txt)