repricing — what changed price in the x402 Bazaar and what happened afterwards

1 · price changes between the two latest snapshots

57 listings repriced20 sellers17 raised40 lowered1 earlier changes with a 7-day reading

Prices in USDC per call. A sub-table under a listing is section 2: that listing's earlier price changes and what the demand readings did around them. The last column is the exact request body for the paid seller report on that listing.

amanchain-relay.gitajhd.workers.dev · payTo 0xfB5625d44be488414606773244F0De35410b2f39 · 37 listings (0 raised, 37 lowered)

animica.dev · payTo 0x5D17c40FD6b119dc6006C4Ab3C20a917FCaB2aCD · 2 listings (2 raised, 0 lowered)

www.amnt.io · payTo 0x02fe8aebddb34d3ca6e35faaba13efa00f6b71e6 · 1 listing (1 raised, 0 lowered)

mcpfax-utility.bowling-anthony.workers.dev · payTo 0x1831f336585a6C67B6A954d28f3E07F44C4EEBbd · 1 listing (1 raised, 0 lowered)

www.amnt.io · payTo 0x25d9849169346ccc8d5f63ba0246139e644c4e92 · 1 listing (1 raised, 0 lowered)

nordland.halowerk.com · payTo 0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E · 1 listing (1 raised, 0 lowered)

www.amnt.io · payTo 0x3fe7e9c0b63fb45050b13d1c71533907f3600f18 · 1 listing (1 raised, 0 lowered)

www.amnt.io · payTo 0x40dedb69d66b93ac661d21ffe47fd5c5b87b2755 · 1 listing (1 raised, 0 lowered)

x402-lookup-seller.fly.dev · payTo 0x4396C5a0648fBF2e514C50b6A2E6186276284c70 · 1 listing (0 raised, 1 lowered)

www.amnt.io · payTo 0x46647e671e1d6d647db046fc36c04a46d1ab2032 · 1 listing (1 raised, 0 lowered)

api.x402card.org · payTo 0x4d5D3dF7F6e3d568D49bF063aE65773fD1fa02E9 · 1 listing (0 raised, 1 lowered)

www.amnt.io · payTo 0x568da6ff9854bafe17467ddd299f9b280ab69dc9 · 1 listing (1 raised, 0 lowered)

coil.trade · payTo 0x7B53524d5c5D29EfB8C1d128C56F62FE38Cd9476 · 1 listing (0 raised, 1 lowered)

www.amnt.io · payTo 0x7bb7be1c319771bd68ee3521361dafbd04ee1ed9 · 1 listing (1 raised, 0 lowered)

www.amnt.io · payTo 0xa2bae3ddebf4e8fade407539304cee6cbb4ed92b · 1 listing (1 raised, 0 lowered)

www.amnt.io · payTo 0xa89feef50d6d8de6a03157ddb6508aa55f4a34ae · 1 listing (1 raised, 0 lowered)

www.amnt.io · payTo 0xbe5a1facd5a3a810d094042ceb799f6f4e2804eb · 1 listing (1 raised, 0 lowered)

www.amnt.io · payTo 0xc93bd911d1ec7a6c9e488640ed5f5cea46f8b02d · 1 listing (1 raised, 0 lowered)

www.amnt.io · payTo 0xe18d541ec8bf15a0f9c0d5d5c66951ea0b3fc0c4 · 1 listing (1 raised, 0 lowered)

www.amnt.io · payTo 0xf4dd40650c5bc29aebc0c9c5e1fbcf4ab96bd109 · 1 listing (1 raised, 0 lowered)

2 · earlier changes, read

For each listing above, every earlier price change with at least 7 days of history on both sides is shown under it: payers and calls (trailing 30 days) on the last day at the old price and exactly 7 days after the change, and the revenue the calls observed at the new price would have produced at the abandoned price. These are the same readings the paid report returns, from the same code.

3 · rolling 30 days

754 repricing events617 listings402 raised352 lowered

520 events with a 7-day readingpayers_30d fell after 39 of them (8%)rose after 203unchanged after 278234 too recent to read

2026-08-09 → 2026-09-07. an event has a 7-day reading when the listing was still priced 7 days after the change; payers_30d there is compared with the previous snapshot's.

4 · how these numbers are derived

Every day the observatory takes one snapshot of the x402 Bazaar catalog: for each listing, the price its 402 terms publish (amount_atomic, USDC with six decimals) and the trailing 30-day call and payer counts the catalog reports for it. Nothing here is a seller self-report to us; it is what the listing itself publishes.

A repricing is a snapshot day on which a listing's recorded price differs from the previous snapshot's. One observation per day means a price that changed and changed back within a day is not seen, so counts here are conservative.

For an earlier price change, "day before" is the last snapshot at the old price and "7 days after" is the snapshot exactly seven days after the first snapshot at the new price. Both are trailing 30-day counts, so a 7-day reading carries 23 days of pre-change history in it; the direction of the move is the signal, not its size.

The counterfactual takes the calls observed at the new price (the last snapshot at which that price still held) and asks what the abandoned price would have earned on that same volume. regret_usdc positive means the abandoned price would have earned more; negative means the reprice earned more. No elasticity is inferred beyond the observed snapshots.

These readings use the same functions as the paid seller report, so a number on this page and the number in a paid call for the same listing never disagree.

your own listing

Free worked example (a real listing that repriced several times, with the input and response schemas): https://api.oblique.markets/api/v1/reprice-regret/example

Paid seller report, $0.01 per call, x402 (USDC on Base or Solana) or MPP (pathUSD on Tempo): POST https://api.oblique.markets/api/v1/paid/reprice-regret

{"resource_url":"https://<host>/<path exactly as listed>","window_days":30}
{"seller_payto":"<the payTo address the listing publishes>","window_days":30}
# exactly one of resource_url or seller_payto; window_days 7–90 (default 30); optional network, cursor

Call it without payment first: the HTTP 402 answer carries the exact amount, asset and payTo; pay and retry with the payment header. No account, no key.