How merc publishes prices. Every number in the catalogue below comes from the current append-only price schedule after the server revalidates its exact market-board, throughput, model-artifact and whole-package power evidence. If any of that authority is expired, withdrawn or unavailable, this page shows no catalogue price.
Why a median and not the lowest price
Taking the minimum lets one stale, promotional or mistyped observation set the price for every supplier in a class. That is not a hypothetical: this board previously priced its inference class from a figure attributed to a vendor but sourced from a competitor's blog post, which put supplier earnings below the cost of the electricity to produce them. The selector is a weighted median so no single row can do that again.
Market observations are shown only as evidence. They do not authorize a buyer price, and this browser does not recalculate a catalogue from them. A price is also refused outright if the governed physical workload cannot cover its measured supplier-side power boundary and leave merc a positive contribution. Prices that cannot sustain the people producing the work are not published.
Catalogue
| model | job type | schedule | valid through | price / 1k units |
|---|---|---|---|---|
| loading board… | ||||
Observations behind each price
| class | provider | model | list / 1M | authority | source |
|---|---|---|---|---|---|
| loading observations… | |||||
What a receipt covers
Every completed job produces a receipt recording the tokens merc actually computed, the tokens delivered to you, and what each was charged at. Delivered tokens that came from a reused prefix or an exact prior result are billed at a lower rate than tokens the model had to compute, and a job's charge can never exceed what full-rate billing would have cost.