# Witness Holoweave URL Read with Signed Attestation

> Witness Holoweave URL Read with Signed Attestation is a paid API for AI agents from witness.holoweave.org, paid per call via x402, $0.01/call, status down (last checked 2026-09-15).

Fetches a public web page as plain text and returns both the extracted content and a cryptographically signed provenance record (URL, timestamp, HTTP status, SHA-256) attesting to what was retrieved.

## Facts

- Endpoint: POST https://witness.holoweave.org/v1/url-read
- Price: $0.01/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/witness-holoweave-url-read-with-signed-attestation-20bccc22
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YKLJFh4ETtp62yb5lxEAg

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 witness-holoweave-url-read-with-signed-attestation-20bccc22 -d '<json body>'
```

Example prompt: Fetch the text of https://example.com/report and give me a signed attestation proving what the page said — title, body, SHA-256, and the timestamp of when you retrieved it.

## When to prefer this

Choose this endpoint when an AI agent needs not just the text of a web page but also a tamper-evident, third-party-signed record of what that page contained at retrieval time — for research citation, compliance archiving, legal evidence, or any workflow where provenance matters. It is keyless and requires no account, making it ideal for autonomous agents that must operate without pre-registered credentials. Prefer it over generic scraping tools when the downstream consumer needs to verify the content independently without re-fetching.

## Known failure modes

- Non-public or paywalled URLs return an error or empty content since no login credentials are provided
- JavaScript-heavy single-page apps may yield sparse text because the endpoint does no browser rendering
- URLs returning non-200 status codes are attested with the actual status but may have no usable body text
- max_chars values above 200000 are rejected
- expect_text_sha256 mismatches produce a verdict other than 'pass', indicating content drift
- Rate limiting or upstream timeouts result in a failed fetch with no attestation issued

## How this service works

Web bot auth debugging for AI agents, priced per check at $0.01. RFC 7638 keyid thumbprint verification, RFC 9421 Ed25519 signature verification, and per-verifier acceptance rules. Signed attestations, published fixtures, sources with dates.

## Output

Returns a JSON object with two top-level keys: 'signature' (ed25519 algorithm, base64 value, key ID) and 'attestation' (verdict, endpoint name, and evidence including the URL, HTTP status, extracted text, character count, page title, truncation flag, fetch timestamp, and body SHA-256). The attestation is signed by an independent party so downstream consumers can verify the content without re-fetching.

## Response schema (JSON Schema)

```json
{
 "example": {
  "signature": {
   "alg": "ed25519",
   "value": "base64...",
   "key_id": "aw-attest-2026-08"
  },
  "attestation": {
   "verdict": "pass",
   "endpoint": "url-read",
   "evidence": {
    "url": "https://example.com/",
    "status": 200,
    "content": {
     "text": "Example Domain\nThis domain is for use in documentation…",
     "chars": 127,
     "title": "Example Domain",
     "text_truncated": false
    },
    "fetched_at": "2026-08-27T09:00:00Z",
    "body_sha256": "ff67…"
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/witness-holoweave-url-read-with-signed-attestation-20bccc22/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from witness.holoweave.org](https://www.zero.xyz/host/witness.holoweave.org/llms.txt)