Conformance report
agentres.dev

Checked: 2026-09-28T00:14:23.174Z

Resource: GET /api/discover/restaurants?fields=slim&limit=5&neighborhood=west+village

Result: 11/11 passed

Fingerprint: sha256:34ffe8f5192e6116eb19d1427ef3ed28e126a993e11835f9ee8656f2cae3ec17

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?	401	passed	Refused with HTTP 401.
`wrong_recipient` Is a payment to a different recipient refused?	401	passed	Refused with HTTP 401.
`wrong_asset` Is a token other than the one demanded refused?	401	passed	Refused with HTTP 401.
`underpayment` Is an amount below the price refused?	401	passed	Refused with HTTP 401.
`wrong_network` Is a payment on the wrong chain refused?	401	passed	Refused with HTTP 401.
`expired` Is an expired authorization refused?	401	passed	Refused with HTTP 401.
`replayed_nonce` Is a reused nonce refused?	401	passed	Refused with HTTP 401.
`not_yet_valid` Is a not-yet-valid authorization refused?	401	passed	Refused with HTTP 401.
`domain_version` Is a contract version supplied by the request ignored?	401	passed	Refused with HTTP 401.
`domain_chain_id` Is a chain id supplied by the request ignored?	401	passed	Refused with HTTP 401.

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-28T00:14:23.174Z · sha256:34ffe8f5192e6116eb19d1427ef3ed28e126a993e11835f9ee8656f2cae3ec17

Conformance reportagentres.dev

Individual checks

Method and limits

Report history

Conformance report
agentres.dev