Read-only source evidence for DAOs, digital treasuries, SaaS billing controllers and software-to-software purchasing systems. Compare actual onchain transaction receipts, recipient, sender, amount, block age and confirmation depth without holding or moving money.
Supply a real Base mainnet USDC transaction hash and expected payee. The preview reports the matching public transfer facts. No wallet, credentials or payment required.
Free checks are rate limited. A transfer may be unrelated to a claimed invoice; this service cannot independently validate contractual obligations.
Independent checks before a buyer-approved payment settles. Detect missing receipts, duplicate transaction hashes in a bundle, misdirected recipients, shortfalls and insufficient confirmations. Produce a structured SHA-256 fingerprint of the observed results.
Paid contract & machine example →
Buyer must enable payment and provide funds through x402 USDC or an existing buyer-funded prepaid account. We do not acquire or sign wallet permissions, transfer assets, or initiate a charge on behalf of sellers.
Independent read-only confirmation of public USDC transfers used by autonomous treasury systems.
Spot whether an observed transaction covers the amount and recipient a billing system expects.
Compare declared transfer evidence before releasing downstream tasks or producing an internal acceptance record.
POST /v1/treasury-court
Payment-Signature: <authorized buyer x402 payment>
Content-Type: application/json
{
"network":"eip155:8453",
"receipts":[{
"tx_hash":"0x...real-64-hex",
"expected_pay_to":"0x...real-40-hex",
"min_amount_usdc":"100.00",
"invoice_ref":"invoice-001"
}],
"policy":{"min_confirmations":12,"max_age_hours":168}
}
Existing customer-funded prepaid credit alternative: POST /v1/prepaid/treasury-court with a buyer-held API key, a unique idempotency key and an explicit spending ceiling. The website does not enroll other entities automatically. Machine discovery: well-known JSON descriptor.
The chain proves a token transfer, not contractual acceptance, invoice ownership, refunds, beneficial ownership, legal discharge, cross-chain settlement or permanent finality. The SHA-256 fingerprint is not a digital signature or third-party attestation. Buyer systems must check their own invoice and authorization records.