For data publishersx402 + managed subscription1 feeds minted

Mint a contradiction-verified, signed feed of your own data.

We run a managed verification layer over a data owner's feed. Every record carries a verification status, an as-of date, source links, and a tamper-evident signed receipt. Records that go stale (past your freshness SLA) or get contradicted by current public records are flagged automatically on each daily re-verification. Buyers of your feed get receipts they can show their own auditors.

Honest read. The urgency here is thin: most data publishers aren't on fire about "signed, verified" today — it's an upsell/differentiator on an existing licensing P&L, not a must-buy. It lands where a record's wrongness has a cost (compliance/KYB/financial feeds). Treat this as a premium tier for publishers who already license data, not a cold-start product.

Each record carries

· Status — VERIFIED / CONTRADICTED / EXCLUSION_HIT / UNVERIFIABLE.

· As-of date + a freshness SLA; records past SLA flag stale.

· Source links — live contradiction-engine (SEC 10-K vs USAspending) + exclude-feed (OFAC/LEIE).

· Signed receipt — SHA-256 hash-chain anchor; recompute to prove the verification is unaltered since its as-of date.

Pricing (managed service)

TierFeedsPrice
Sample1$0
Managed Feed3$1,000/mo
Licensed Publisher20$3,000/mo
Enterprise200$5,000/mo

Per-record verification via x402: $0.20 USDC on Base mainnet, keyless.

API, MCP & x402 →

Live demo — verified on our own gov feed

The govcon-demo feed is minted from our real contradiction-engine gov data and re-verified live. See real CONTRADICTED + VERIFIED records, each with an as-of date and signed receipt.

View the live demo feed →
DropWatch HQ · verified.dropwatchhq.com · Docs & pricing · Live demo feed · MCP · x402
Verification statuses are DATED evidence statements ("as of T, source X shows Y"), not guarantees. Public-source data can change; the freshness SLA + re-verification keep records current.