Loading
Knocking on the endpoint…
We ask it what it charges, read its catalogue entry, apply the policy, and then ask it again to see whether the price held. That is two round trips to somebody else’s server, so a few seconds is normal and a slow answer is a fact about them rather than about this page.
Walks a whole purchase in the order a buyer asks the questions, stopping at the first that objects. Nothing is signed and nothing is spent. The payment check asks the narrower question, about a payment you have already decided on.
Every question a buyer asks before paying was answered, and none of them objected. That is not a promise about what arrives: only paying and reading the answer establishes that.
Answering since 2026-11-04. 10 of 10 knocks have been answered, the most recent on 2026-11-11.
One mark is one knock, not a span of time. We knock a working endpoint about once a day and back off on one that has been down a long time, so a gap here is where we did not look.
Asked just now. We knock at most once a minute per endpoint, shared by everybody, because our own user agent promises not to be a load.
The half that settles those is a real payment from your own wallet, which is not built yet. When it is, the money goes to the seller and never through us.