Conformance report
agentservices.to

Checked: 2026-09-27T01:00:22.822Z

Resource: GET /v1/indicators/eth

Result: 11/11 passed

Fingerprint: sha256:3e4edd89877b63b0ddd447f3f090163d573518c2e64e55d630a586d39d34b55c

Individual checks

Check	HTTP	Grade	Reason
`challenge_present` Does an unpaid request answer with a valid 402 challenge?	402	passed	Valid HTTP 402 challenge.
`malformed_signature` Is an unreadable payment header refused rather than answered with a 5xx?	402	passed	Refused with HTTP 402.
`wrong_recipient` Is a payment to a different recipient refused?	402	passed	Refused with HTTP 402.
`wrong_asset` Is a token other than the one demanded refused?	402	passed	Refused with HTTP 402.
`underpayment` Is an amount below the price refused?	402	passed	Refused with HTTP 402.
`wrong_network` Is a payment on the wrong chain refused?	402	passed	Refused with HTTP 402.
`expired` Is an expired authorization refused?	402	passed	Refused with HTTP 402.
`replayed_nonce` Is a reused nonce refused?	402	passed	Refused with HTTP 402.
`not_yet_valid` Is a not-yet-valid authorization refused?	402	passed	Refused with HTTP 402.
`domain_version` Is a contract version supplied by the request ignored?	402	passed	Refused with HTTP 402.
`domain_chain_id` Is 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.

Original data (JSON)

Report history

2026-09-27T01:00:22.822Z · sha256:3e4edd89877b63b0ddd447f3f090163d573518c2e64e55d630a586d39d34b55c

Conformance reportagentservices.to

Individual checks

Method and limits

Report history

Conformance report
agentservices.to