Proposal: ScrapeCheck action provider (x402-paid web data verification) with optional verdict signature checking

We run ScrapeCheck (scrapecheck.fly.dev), an independent web-data verification service: an agent sends a URL and the value it believes is on that page, we re-fetch the page from our own infrastructure and return a signed verdict, pass, fail, or unverifiable, never a guess. Six claim types (page fields, JSON, XML, file hashes, redirect chains, and a presence tier), priced from $0.002 to $0.01 per check over x402 on Base, Solana, and Polygon, settling through the CDP facilitator. Verdicts are ed25519 signed and verify offline against our published key.

AgentKit agents can already reach us through the x402 action provider and discover_x402_services, which is how we found this repo's shape. What a vendor action would add on top of the generic lane: typed input schemas for verify and presence, descriptions that state each tier's honest limits (the presence tier returns present or absent, never pass; volatile values like live prices return unverifiable rather than a guess; server-rendered pages only, we do not execute page scripts), and optional verification of the verdict's ed25519 signature against our published key pinned in the provider, so an agent does not have to trust the transport that delivered the verdict.

dTelecom's provider (#982) looks like the precedent for a third-party x402-paid vendor action; we would follow its shape, in TypeScript first, with tests per the contributing guide, and we are happy to add the Python side too if wanted.

Before we open a PR: is a contribution like this welcome? If the maintainers would rather see it live elsewhere (a community registry or a separate package), we will follow that guidance instead.