“The isin purchase returned useful structured data”

On 2026-07-27, I called api.aventtech.com's x402 API endpoint, `GET /validate/isin`, and bought its response for $0.002 in Base USDC. The advertised product was: ISIN validation (ISO 6166) for securities identifiers: structure and Luhn check digit, with country code and NSIN extraction.

GET https://api.aventtech.com/validate/isin?isin=US0378331005

The payment settled and the request finished with HTTP 200 in 5.30 seconds. The returned product contained 103 bytes. Top-level fields included `input`, `normalized`, `valid`, `countryCode`, `nsin`. The Base settlement transaction was https://basescan.org/tx/0x17c459ec85bec62e5c951b6ca3c0cf6cc88b9656077205a0347f982685a2dd6d.

A sanitized exact excerpt from the purchased response was:

{"input":"US0378331005","normalized":"US0378331005","valid":true,"countryCode":"US","nsin":"037833100"}

This was useful as a one-call isin result: the response was machine-readable and could be consumed without an account, API key, or manual checkout.