Use ScrapeCheck from your agent

Four ways to wire independent verification into an agent or pipeline, each ending in something you can paste. Every snippet on this page was run against production before it was published here. First 100 checks per client are free; no account, no API key.

1. MCP clients (Claude, ChatGPT, Cursor, anything that speaks MCP)

One line gives your agent a verification tool in its own toolbox. From then on it can check a value mid-task, on its own judgment, before it acts on it.

claude mcp add --transport http scrapecheck https://scrapecheck-mcp.fly.dev/mcp

Any other MCP client: add a streamable-HTTP server at https://scrapecheck-mcp.fly.dev/mcp. The tools are verify_web_field ($0.01), verify_presence ($0.002), and get_verifier_info (free). The free allowance is served before payment is ever required; past it, payment is x402 in-band from the agent's own wallet.

2. x402-native agents and catalogs

Anything built on the x402 client stack can discover us in the CDP Bazaar catalog, read the machine metadata, pay per call in USDC on Base, and verify, with no human in the loop. Six resources are listed: /verify, /verify-presence, /verify-json, /verify-hash, /verify-xml, /verify-redirect. A bare POST returns the standard 402 challenge your payment stack consumes; the challenge itself carries the input schema, an example body, and the documented errors:

curl -i -X POST https://scrapecheck.fly.dev/verify-json \
  -H "content-type: application/json" \
  -d '{"url":"https://scrapecheck.fly.dev/healthz","claim":{"service":"scrapecheck"}}'
# HTTP/1.1 402 Payment Required
# payment-required: <base64 challenge: schema, example, prices, errors>

Your x402 client handles the rest. Nothing to register with us; being listed with agent-ready metadata is the integration.

3. Apify workflows (no crypto anywhere)

The Scrape QA actor chains after any scraper actor on Apify: add it as an integration on the scraper, and when a run succeeds, verification runs on the output dataset automatically and a trust report lands. Apify bills; no wallet exists anywhere in this lane. To verify an existing dataset directly:

apify call fieldmodellc/scrape-qa --input '{"datasetId":"YOUR_RUN_DATASET_ID"}'

4. Plain HTTP for custom agent loops (LangChain, CrewAI, hand-rolled)

Hit the API directly. The free-allowance header works with no payment plumbing at all:

curl -X POST https://scrapecheck.fly.dev/verify-json \
  -H "content-type: application/json" \
  -H "X-Use-Free-Allowance: yes" \
  -d '{"url":"https://scrapecheck.fly.dev/healthz","claim":{"service":"scrapecheck"}}'
# returns a signed verdict: pass | fail | unverifiable

Building a tool for a framework? Point it at /openapi.json and the tool definition generates itself from our own spec. The plain-language version lives at /llms.txt.

Every verdict, in every lane, is the same artifact

An ed25519-signed envelope that verifies offline against our published key, with a one-file, zero-dependency verifier anyone can run. Don't trust us. Verify us.