x402 conformance status: api.aestheticdata.io
api.aestheticdata.io reads PASS 23/23 on the scheduled run of 2026-10-08T02:33:14.510Z (checker inventory 1.9.0). Checked, never certified: this page states below what the checks do not cover. It is rebuilt after every scheduled run; if no run has happened for 48 hours the image reads STALE rather than repeating an old word.
GET https://api.aestheticdata.io/x402/brands — PASS 23/23 checks
| verdict | check | detail |
|---|---|---|
| PASS | client_fingerprint_parity | all 5 probed User-Agents get the same 402 as the baseline (a User-Agent comparison from one network seat, not a client fingerprint) |
| PASS | discovery_docs_parity | /.well-known/x402, /openapi.json, /llms.txt answer 200 to the default client and to Python-urllib/3.12 and libwww-perl/6.68 alike |
| PASS | body_envelope_complete | v1 body carries x402Version, and resource inside every accepts entry (where v1 puts it) |
| PASS | accepts0_payable | accepts[0] is exact/base — payable by a client that takes the first option |
| PASS | accepts_all_executable | all 1 advertised option(s) are executable |
| PASS | header_body_agree | header (PAYMENT-REQUIRED (base64), eip155:8453) and body (v1, base) name the same option in two dialects — dual-serving, not a disagreement |
| PASS | plaintext_envelope_refused | plaintext redirects 301 to https://api.aestheticdata.io/x402/brands before any terms are served (a GET route carries no body for a 301 to drop) |
| PASS | no_payment | 402 Payment required: send PAYMENT-SIGNATURE (x402 v2) or X-PAYMENT (x402 v1) |
| PASS | header_not_base64_json | 402 invalid_x_payment |
| PASS | garbage_payload | 402 invalid_x_payment |
| PASS | bad_signature | 402 invalid_x_payment |
| PASS | wrong_signer | 402 invalid_x_payment |
| PASS | wrong_amount_underpay | 402 invalid_x_payment |
| PASS | wrong_destination | 402 invalid_x_payment |
| PASS | expired_authorization | 402 invalid_x_payment |
| PASS | not_yet_valid | 402 invalid_x_payment |
| PASS | wrong_chain_domain | 402 invalid_x_payment |
| PASS | payTo_not_zero_address | payTo 0x407ebFbE… |
| PASS | asset_contract_exists | asset has contract code |
| PASS | asset_supports_eip3009 | authorizationState() answers — EIP-3009 present |
| PASS | payTo_not_blacklisted | isBlacklisted(payTo) is false |
| PASS | asset_is_canonical | asset is canonical USDC on base |
| PASS | payTo_account_type | payTo is a contract — it receives ERC-20 fine, but whether funds are sweepable depends on its code (not verifiable read-only) |
What this does not cover
The checker tests spec-normative x402 requirements on the rejection path (the 402, its payment terms, the receiving rail's on-chain liveness, client-fingerprint parity, plaintext exposure) and performs no live paid settlement. A clean verdict is necessary, not sufficient: a door that accepts a payment and then fails to deliver is outside its reach. Nothing here says anything about the endpoint's security, its operator, or the quality of what it sells. Method, scope and selection rules: monitor page; the check inventory is published and versioned.
Embed this badge
Embedding is the operator's choice; the image is free, never for sale, and rebuilt daily. Serve it from here (do not copy the file) so it can go STALE honestly. The image is served with a 30-minute cache at the origin and at the CDN edge (edge rule added 2026-09-11), so a badge can lag the board by 30 minutes and no more. Markdown:
[](https://coppice-ai.com/badge/api.aestheticdata.io.html)HTML:
<a href="https://coppice-ai.com/badge/api.aestheticdata.io.html"><img src="https://coppice-ai.com/badge/api.aestheticdata.io.svg" alt="x402 conformance status for api.aestheticdata.io" height="20"></a>