x402 conformance status: api.printmoneylab.com
api.printmoneylab.com reads FAIL 17/18 on the scheduled run of 2026-10-27T02:33:32.169Z (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 26 hours (the daily run plus two hours of grace; 48 hours until 2026-10-10, which let one whole missed run pass unseen) the image reads STALE rather than repeating an old word.
Operate this endpoint? The fix for every adverse row above is on the board's detail column and in the check's own detail text, free. If you would rather fix it before the next run reads it, there is a private operator audit, $99: the same battery run privately, a fix list in the order the money leaks, re-tests until it passes for 30 days, and nothing published without your word. The fee buys the work, never the verdict; a paid audit never changes this badge.
GET https://api.printmoneylab.com/api/v1/kimchi-premium?symbol=BTC — FAIL 17/18 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 |
| FAIL | plaintext_envelope_refused | GET http://api.printmoneylab.com/api/v1/kimchi-premium answers 402 with a full payment envelope in the clear — and its own resource.url claims https://api.printmoneylab.com/api/v1/kimchi-premium?symbol=BTC, a security property the channel it arrived on does not have. payTo is rewritable in transit by anything on the path. |
| PASS | body_envelope_complete | body carries x402Version + resource beside `accepts` |
| PASS | accepts0_payable | accepts[0] is exact/eip155:8453 — payable by a client that takes the first option |
| PASS | accepts_all_executable | all 3 advertised option(s) are executable |
| PASS | header_body_agree | header and body advertise the same payment options |
| PASS | no_payment | 402 Payment required |
| PASS | garbage_transaction | 402 Payment required |
| PASS | header_not_base64_json | 402 Payment required |
| PASS | unsigned_transaction | 402 Payment required |
| PASS | forged_signature | 402 Payment required |
| PASS | wrong_asset | 402 Payment required |
| PASS | wrong_amount_underpay | 402 Payment required |
| PASS | wrong_destination | 402 Payment required |
| PASS | extra_instruction | 402 Payment required |
| PASS | fee_payer_ata_as_source | 402 Payment required |
| PASS | receive_rail_exists | destination token account 8SSUtadv… exists |
Verdict changes on record
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.printmoneylab.com.html)HTML:
<a href="https://coppice-ai.com/badge/api.printmoneylab.com.html"><img src="https://coppice-ai.com/badge/api.printmoneylab.com.svg" alt="x402 conformance status for api.printmoneylab.com" height="20"></a>