Show HN: X402 integrations for an AI-agent data API, checked in a clean room
I run Blockchain IQ. We sell some crypto data to software agents per request over x402 (HTTP 402, USDC on Base, no account or API key). In October we paid for integrations: 22 were submitted and we checked each one by matching its on-chain payment to our purchase log and running it in a clean temporary folder with a throwaway wallet. Twenty passed; the post lists all of them with the exact commits we ran. To try the API: `curl -i https://www.blockchainiq.co/api/x402/v1/brief ` returns the 402 wi
Read original source
Source record
Recorded metrics
points · 1 votes
2026-10-29 08:00:03.165Z
cumulative since publication
Research analysis
What changed
Source account: I run Blockchain IQ. We sell some crypto data to software agents per request over x402 (HTTP 402, USDC on Base, no account or API key). In October we paid for integrations: 22 were submitted and we checked each one by matching its on-chain payment to our purchase log and running it in a clean temporary folder with a throwaway wallet. Twenty passed; the post lists all of them with the exact commits we ran. To try the API: `curl -i https://www.blockchainiq.co/api/x402/v1/brief ` returns the 402 wi
Version & cost evidence
Source votes: 1 votes (Oct 29, 2026 UTC; cumulative since publication); previous same-scope observation: 1 (Oct 29, 2026 UTC). These observations do not establish demand growth. Recent records to compare: “[分享创造] 做了一个 3D AI 办公室，都是真实数据” (V2EX, Nov 9, 2026); “Show HN: Askaboard – A canvas your AI agent can draw on” (Hacker News, Nov 9, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.
Who is affected
Identify the existing workflow this change affects before recommending an upgrade. Launch attention does not establish improvement; an API, pricing or availability change may instead create migration work.
Missing comparison points
Missing checks: old versus new behavior, affected plans and regions, availability date, compatibility, rollback path and cost under the same workload.
Migration check
Save the release or policy notice, run the same task on the old and new option, and compare outputs and the full bill. For retirement notices, verify the deadline before scheduling migration.