# Web Content Verification via Pinggy

> Web Content Verification via Pinggy is a paid API for AI agents from ejjvg-64-118-156-55.free.pinggy.net, paid per call via x402, $0.25/call, status unknown (last checked 2026-10-10).

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

## Facts

- Endpoint: POST https://ejjvg-64-118-156-55.free.pinggy.net/verify?utm_source=zero.xyz
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/web-content-verification-via-pinggy-964c10e9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XJJC5Q4s4_6TEgIOUttob

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-via-pinggy-964c10e9 -d '<json body>'
```

Example prompt: Can you verify whether this URL actually supports the claim that 'electric vehicles reduce emissions by 50%'? Here's the page: https://example.com/ev-study

## When to prefer this

Use this endpoint when you need to programmatically verify whether a web page supports a specific claim or fact, especially in fact-checking, research validation, or content audit workflows. It is suitable for single-URL verification with an optional claim string. Prefer alternatives if you need bulk URL verification, deep crawling, or structured data extraction rather than claim validation.

## Known failure modes

- URL is unreachable or returns a non-200 HTTP status — verification fails with no content to analyze
- Claim is too vague or ambiguous for the verifier to match against page content — may return low-confidence or unsupported result
- Pinggy tunnel endpoint may be ephemeral/offline since it is a free hosted tunnel, causing connection failures
- Page content is behind authentication or a paywall — verifier cannot read the content
- Malformed URL input causes a validation error before verification begins

## How this service works

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

## Output

Returns the verified URL, a receipt object confirming the verification transaction, a 'supported' string indicating whether the page content supports the provided claim, and an array of cross-reference objects linking related sources or evidence found during verification.

## 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-via-pinggy-964c10e9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ejjvg-64-118-156-55.free.pinggy.net](https://www.zero.xyz/host/ejjvg-64-118-156-55.free.pinggy.net/llms.txt)