A rank describes the field

1,000 USDT on Tron to Bitcoin, one fan-out, Stereoswap asked alongside it:

Seventeenth of eighteen. One place off the bottom, in a field where the same board had it on top.

Nothing here says the other board was wrong. It compares a different set of providers, and among those Stereoswap was the best that morning. Among these it is near the worst. A rank is a sentence about the other seventeen, and the provider in the middle of it is the one thing that did not change.

The amount differed too: their 100 against this 1,000. Small transfers price differently because fixed costs weigh more on them, so the two rankings were not even of the same question. Two variables moved at once, and either alone could account for sixteen places.

The error was ours and it was in writing: a number read off somebody else’s page, treated as a property of the provider. Quoting another site’s rank imports their field along with it. This site exists so that nobody has to do that, which makes it a particularly bad mistake to make here.

The other thing the episode corrected is older. Stereoswap had been recorded as blocked on them for thirteen days, because their API rejected our key the same way it rejected a garbage one. Probed again, it rejects everything that way — no header, an empty key, a wrong key, all one byte-identical 401. A response that cannot tell those apart could never have shown the fault was theirs. It was not: the key on this machine had been copied from a dashboard that masks the tail, thirty-six characters with six asterisks in them, where the real one is sixty-four.

It stays queued, at the bottom. The adapter is a morning’s work and buys a row that would have sat sixteen places down. If it is added, it will be ranked the way every other provider here is: by thousands of same-second fan-outs, not by one board read once.