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

1 · price changes between the two latest snapshots

45 listings repriced19 sellers28 raised17 lowered5 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.

foundry-api-production-95ae.up.railway.app · payTo 0xaCe6B7bbA8C9C1A429E58ffE407d1305734f107E · 8 listings (3 raised, 5 lowered)

x402-data-api.sigrunner.workers.dev · payTo 0x5765ae06a52dc7A0BB71c36A11db512c7ea9ed10 · 7 listings (7 raised, 0 lowered)

agents.daedalusdevelopmentgroup.com · payTo 0x8AfBD522F8a16BEa184b41c593B8925a66830Bc6 · 5 listings (5 raised, 0 lowered)

api.hivemindos.app · payTo 0xbD62F8DCB52E21CA5BDf20ba173488Da101eBCf0 · 4 listings (2 raised, 2 lowered)

api.marketintelligenceapi.com · payTo 0x48d5A78d480B4C32dE319C2aEF69e682Dc304615 · 3 listings (3 raised, 0 lowered)

oracle.cyberwarex.com · payTo 0x058D0Cc5CC97e61e8A9f38D6d6365bce525921B2 · 2 listings (0 raised, 2 lowered)

api.hyperextend.xyz · payTo 0x548fC289526ab2F0391D562a723cdA64Bbf1abc4 · 2 listings (1 raised, 1 lowered)

filings-specs-api.onrender.com · payTo 0x6BfFcc85172372aD4e9c1Ffafe97980A2C778FC7 · 2 listings (2 raised, 0 lowered)

market-calendar-api.onrender.com · payTo 0xC577c27d10767ABfc10D867b443577fE296E7d23 · 2 listings (2 raised, 0 lowered)

kino402.com · payTo 0x2A266c87F7b0D1F8A471D2d5234F5CF4FB62b206 · 1 listing (1 raised, 0 lowered)

sift.srv1996466.hstgr.cloud · payTo 0x33d25C0A915e1114B341d09a7Cf7CEcaB60AFa0d · 1 listing (1 raised, 0 lowered)

www.taifoon.io · payTo 0x3574999dd4c96eB73Bd6e11D4177010C83E14f5b · 1 listing (0 raised, 1 lowered)

makememoneynomistakes.ai · payTo 0x751fd2618DEf5623b3766673160DD9a4dcDb6618 · 1 listing (0 raised, 1 lowered)

twin.unykorn.org · payTo 0x7d9a65d06dcc435a52D5880C6310Bd6E96c156DB · 1 listing (0 raised, 1 lowered)

tenjin.sh · payTo 0x8b62AD897f108c39Fd9CF309b46f2b54455a5699 · 1 listing (0 raised, 1 lowered)

api.gondola-ai.com · payTo 0x98886846918c7deBe86E1D74E249DCDd64a9D367 · 1 listing (0 raised, 1 lowered)

agent-evidence-api.thx93.workers.dev · payTo 0x9c0e2B44180439294Fa30Ae2B2a94f8655455FD0 · 1 listing (1 raised, 0 lowered)

aizamon.com · payTo 0xB88544cF8E9E97EEb2F313e0D3528FC1e50C2887 · 1 listing (0 raised, 1 lowered)

flow-kg4x.vercel.app · payTo 0xcF8A8350cb42a6680005ca7FF9E485Bb55fa74FA · 1 listing (0 raised, 1 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

1927 repricing events1810 listings1389 raised538 lowered

981 events with a 7-day readingpayers_30d fell after 25 of them (3%)rose after 577unchanged after 379946 too recent to read

2026-09-22 → 2026-10-21. 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.