Conformance report
app.suedeai.ai
Checked: 2026-10-17T00:44:21.444Z
Resource: POST /create-music
Result: 11/11 passed
Fingerprint: sha256:249af8418f898b27e4810d793b716ac0e16566fe65fe88823b2d52f90e8e86c0
Individual checks
| Check | HTTP | Grade | Reason |
|---|---|---|---|
challenge_presentDoes an unpaid request answer with a valid 402 challenge? | 402 | passed | Valid HTTP 402 challenge. |
malformed_signatureIs an unreadable payment header refused rather than answered with a 5xx? | 402 | passed | Refused with HTTP 402. |
wrong_recipientIs a payment to a different recipient refused? | 402 | passed | Refused with HTTP 402. |
wrong_assetIs a token other than the one demanded refused? | 402 | passed | Refused with HTTP 402. |
underpaymentIs an amount below the price refused? | 402 | passed | Refused with HTTP 402. |
wrong_networkIs a payment on the wrong chain refused? | 402 | passed | Refused with HTTP 402. |
expiredIs an expired authorization refused? | 402 | passed | Refused with HTTP 402. |
replayed_nonceIs a reused nonce refused? | 402 | passed | Refused with HTTP 402. |
not_yet_validIs a not-yet-valid authorization refused? | 402 | passed | Refused with HTTP 402. |
domain_versionIs a contract version supplied by the request ignored? | 402 | passed | Refused with HTTP 402. |
domain_chain_idIs a chain id supplied by the request ignored? | 402 | passed | Refused with HTTP 402. |
Method and limits
An unpaid challenge is requested first. The remaining requests carry unreadable or altered payment headers with fabricated signatures. No valid payment is ever sent and no money moves. The responses demonstrate HTTP refusals, not isolated cryptographic field or replay security. At most 11 requests per origin including the challenge, one per second.
Report history
- 2026-10-17T00:44:21.444Z ·
sha256:249af8418f898b27e4810d793b716ac0e16566fe65fe88823b2d52f90e8e86c0 - 2026-09-25T01:00:45.034Z ·
sha256:8a37af91346f1e4c09ee702fec6ec1e20a587e1036a72682d84d696c99bacabe