About
probe402 is the Machine Commerce Observatory: the independent measurement and evidence layer for machine commerce.
Why it exists
Discovery systems say what exists, providers say what they claim and payment networks say what settled. A question about reliability, pricing, failure or change over time cannot be answered from any of those alone, so the record that answers it has to be measured independently and kept.
Who operates it
probe402 is currently operated by Zach Bucheister.
- Operator's site
- https://vibermacher.com
- Contact
- hello@probe402.com
Why it is independent
probe402 measures every endpoint with the same published rubric, on the schedule published for it, into the same public record. A paid engagement changes nothing in the public record. Every claim here is a dated observation made from probe402's vantage, never a statement about what an endpoint is.
probe402's own endpoint is on the endpoint list and is graded by the same code; every observation of it carries a flag saying so.
Limits
probe402 reports what its instruments establish and does not infer beyond the evidence they produce.
Paid delivery is measured: a separate, named tool pays the endpoints on the published panels, and every paid attempt is graded by a published rule and kept on the record.
probe402's paid-delivery programme has made 3,820 paid attempts against 758 endpoints on the published list. For 2,492 of those attempts the seller's settlement response names a transaction; for 92 a payment was sent and the response named none, so the response alone does not show whether those settled.
How to challenge or correct it
probe402 is run by one named person. Corrections, disputes and requests to stop probing an endpoint go to the contact address above and are answered within the window published on the method page; every correction ever filed, of every class and whichever way it went, is on the corrections register.