---
title: "The Week's Ledger — 2026-W36"
description: "What this store's weekly round observed in 2026-W36: doors reached, doors payable, what moved, and what the instrument could not see."
canonical: "https://scvd.store/ledger/2026-W36"
url: "https://scvd.store/ledger/2026-W36"
data: "https://scvd.store/ledger/2026-W36.json"
---

# The Week's Ledger — 2026-W36

What this store's weekly round observed in 2026-W36: doors reached, doors payable, what moved, and what the instrument could not see.

## What this is

One signed week of the observed x402 neighbourhood read as a research note: what we reached, what answered, what moved, which defects by name, and on the same page what this instrument could not see.

## Proposition

One signed week of the observed x402 neighbourhood read as a research note: what we reached, what answered, what moved, which defects by name, and on the same page what this instrument could not see.

## Price

Nothing here costs money: every figure is a count over a signed snapshot that is already free to fetch, and the paid instruments are priced on the shelf where they are sold rather than gated behind this reading.

## Free first

Every week the chain holds is free to read as a page or as JSON, and each one names the signed snapshot it counted so you can rebuild the whole reading yourself.

## Opened

2026-09-04

## How to call

### The index

GET https://scvd.store/ledger for every week the chain holds, HTML or JSON by Accept.

### One week

GET https://scvd.store/ledger/2026-W36 for the page, or https://scvd.store/ledger/2026-W36.json for the same reading as JSON.

### The findings

Every entry in `findings` names the fields it was computed from in `derived_from`; fetch the snapshot it cites and recount.

### Subscribe

The signed source is https://scvd.store/corpus/latest.json, which carries ETag and Last-Modified for a conditional GET.

## Errors

### Unknown week

A week the chain does not hold answers 404 with `known_weeks` naming the weeks it does. This store does not invent a baseline for a week it did not seal.

### Malformed week

Anything that is not a YYYY-Wnn week answers 404 rather than being guessed at.

### No weeks yet

With an empty chain the index answers 200 with an empty `weeks_held`. That is our age, not an error.

## Security

### What this does in your name

Nothing. A GET here reads signed snapshots already published; no door is probed and nothing is fetched from anyone on your behalf.

### What it stores about you

Nothing about you. The porch counts a visit by surface, never by caller.

### What we never do

No account, cookie, caller identifier or IP-based budget. Budgets bound our cost, not caller rank. Requests are never sold, shared or published. The weekly census reads public discovery feeds, never these requests.

### Standards

Disclosure is private-first and symmetric: notify the operator before publication, including our own defects. Corrections are dated and public. Signed artifacts verify offline against our published key.

### Reporting

https://scvd.store/.well-known/security.txt for a vulnerability, https://scvd.store/corrections for something we got wrong.

## Artifact

week_ledger

## Name

The Week's Ledger

## Week

2026-W36

## Taken at

2026-09-01T13:27:08.998Z

## Sequence

5

## Digest

a69a2144fb5b0feee0da1003d6356dca331ccf58917e6f136ff369706d9f3722

## Brief

### Artifact

weekly_brief

### Name

The Week's Doors

### Week

2026-W36

### Taken at

2026-09-01T13:27:08.998Z

### Sequence

5

### Digest

a69a2144fb5b0feee0da1003d6356dca331ccf58917e6f136ff369706d9f3722

### Battery

preflight-v2

### Doors

- **Listed** — 6000
- **Probed** — 1088
- **Payable** — 634
- **Not payable** — 450
- **Unreachable** — 4
- **Offers seen** — 762

### Networks

- **Eip155:8453** — 733
- **Solana:5eykt4usfv8p8njdtrepy1vzqkqzkvdp** — 255
- **Eip155:137** — 110
- **Eip155:42161** — 102
- **Hyperliquid:mainnet** — 1
- **Base** — 14
- **Solana** — 2
- **Eip155:84532** — 15
- **Eip155:480** — 58
- **Algorand:wghe2pwdvd7s12bl5faop20egyesn73ktic1qzkkit8=** — 4
- **Eip155:10** — 2
- **Eip155:1329** — 1
- **Eip155:143** — 58
- **Eip155:42220** — 1
- **Eip155:43114** — 2
- **Eip155:4663** — 22
- **Stellar:pubnet** — 2
- **Algorand:wghe2pwdvd7s12bl5faop20egyesn73k** — 56
- **Eip155:196** — 60
- **Eip155:56** — 58
- **Eip155:999** — 55
- **Xrpl:0** — 57
- **Eip155:50** — 1
- **Eip155:1440000** — 1
- **Eip155:1** — 2
- **Eip155:1187947933** — 1
- **Solana:etwtrabzayq6imfeykouru166vu2xqa1** — 2
- **Animica:1** — 1
- **Eip155:3338** — 1
- **Eip155:4326** — 1

### Schemes

- **Batch-settlement** — 3
- **Exact** — 761
- **Upto** — 4
- **Onchain** — 1
- **Aggr deferred** — 1

### Defects

| ID | Title | Count |
| --- | --- | --- |
| status-402 | status-402 | 320 |
| payto-payable | payto-payable | 63 |
| amount-atomic | amount-atomic | 56 |
| solana-rail-receivable | solana-rail-receivable | 19 |
| payment-required-header | payment-required-header | 16 |
| network-mainnet | network-mainnet | 15 |
| signed-offers | signed-offers | 12 |
| transfer-method-signable | transfer-method-signable | 2 |
| accepts | accepts | 1 |
| bazaar-extension | bazaar-extension | 1 |

### Our gaps

- **Not probed** — 1
- **Observer degraded** — 0
- **Coverage suspect** — true

### Previous

- **Week** — 2026-W35
- **Payable** — 676
- **Not payable** — 293
- **Probed** — 969

### Not a ranking

Counts, with their denominators, for one signed week. No host is ranked or named on this page; the doors themselves are listed alphabetically at /doors, each with its own dated observation. Every figure here carries the two numbers it came from, which is the house sentence: never a ranking, and never a verdict without its derivation and denominator beside it.

### How to rederive

Every number here is a count over https://scvd.store/corpus/5.json, the signed snapshot for 2026-W36 (digest a69a2144fb5b0feee0da1003d6356dca331ccf58917e6f136ff369706d9f3722); recount it with your own tools and compare against the chain at https://scvd.store/corpus.json.

### Every door

<https://scvd.store/doors>

## Changes

### Artifact

corpus_changes

### Week

2026-W36

### Sequence

5

### Digest

a69a2144fb5b0feee0da1003d6356dca331ccf58917e6f136ff369706d9f3722

### Taken at

2026-09-01T13:27:08.998Z

### What this is not

Never a ranking, and never a verdict without its derivation and denominator beside it. A change here is two dated observations a week apart, one instrument, one vantage; nothing is claimed about the days between, and a host absent from a round was unlisted, beyond the round's caps, or dropped by our own coverage — the rounds say which. A changed pay-to is a changed set of address digests between the two rounds, compared only where both captured one; it is not a finding of compromise, and the verbatim addresses are not published here.

### Cite

scvd.store, corpus changes, week 2026-W36 (snapshot 5), observed 2026-09-01T13:27:08.998Z; ed25519-signed, key at https://scvd.store/.well-known/scvd-signing-key; bytes at https://scvd.store/corpus/changes/2026-W36.json; verify at https://scvd.store/corpus/5.json.

### Cite format

One line to quote verbatim: the issuer, what and which, when it was observed, how it is signed and where the key is, and the URL whose bytes are the thing cited. A citation names an observation, never a judgment.

### Previous

- **Week** — 2026-W35
- **Sequence** — 4
- **Digest** — a77a01a8fff60c897972b7c4dbcb2696be361c03513a20245823a8e8b98a58a1

### Additions

- agentworld.me
- patentpulse.theaslangroupllc.com
- ephemeris.561.group
- mail.cusethejuice.com
- api-onchain.optimai.network
- copperhead.lonestaroracle.xyz
- cottonmouth.lonestaroracle.xyz
- rattler.lonestaroracle.xyz
- the-stall.intuitek.ai
- signal.keelbase.io
- x402.blackswan.wtf
- curatoria.dev
- api.gmfarcaster.com
- x402.sniperx.fun
- 402signal.com
- stationfx.com
- x402.outpimp.com
- node-starter--maxujon18.replit.app
- www.celerapi.com
- agent.massive.com
- lion-x402.lionmaster-operations.workers.dev
- openrelay.hggfffdfy687.workers.dev
- agent-api-production.tim1712.workers.dev
- agent-api-testnet.tim1712.workers.dev
- grov.fun
- oracle.cyberwarex.com
- web.cyberwarex.com
- search.cyberwarex.com
- osha-search.46-224-157-88.sslip.io
- x402-echo-service.onrender.com
- task-profit-api.62.238.55.212.sslip.io
- bounty-signals.krimskrams.xyz
- staging.getbags.app
- cyre.dev
- aegis-api-mainnet.kadopi.workers.dev
- source-claim-proof.mattskowronis.workers.dev
- agent.api.0x.org
- kino402.com
- api.usesaferoute.com
- byfaro.ai
- centboard.xyz
- ip402.xyz
- tizona-outpost.venusberg.workers.dev
- foundry-par007-machine-revenue-mainnet.inference-chip-index.workers.dev
- raptor-base-yields.vercel.app
- trading-perps.vercel.app
- tenderdelta-preview.mooncakemonkey1.workers.dev
- deadchannel.vercel.app
- fetchharbor.benlab.download
- content-moderation-api-hhy1.onrender.com
- relay.preflightstack.com
- lion-x402-bible.lionmaster-operations.workers.dev
- video.cyberwarex.com
- chain.cyberwarex.com
- api.zfinia.com
- api.newsgurus.ai
- ledger-api.novadyne.ai
- www.moltbillboard.com
- random.preflightstack.com
- amoraw.xyz
- contextslim.friczero.com
- 767-2676.com
- 402rpc.com
- payload402.edgebytenet.workers.dev
- api.runx.ai
- api.ccbaydata.com
- license.ccbaydata.com
- www.vokko.eu
- crawl-preflight.postnov01.workers.dev
- x402.donnyautomation.com
- agent.connskill.com
- spawnxchange-api-485602182462.europe-west4.run.app
- api.m2msentinel.com
- research.lumenhouse.xyz
- musicwire.5432wire.com
- italian-company-check-fdsbh7p2bq-oc.a.run.app
- wellsyncc-x402.2ng-nhan.workers.dev
- api.bakebakebake.no
- money-ai-shop.money-ai.workers.dev
- cryptoops.friczero.com
- godlaws.com
- api.resetparatodos.com
- agents.dubbleblack.com
- agenteconomy.report
- api.x402-hosting.com
- mcpfax-utility.bowling-anthony.workers.dev
- www.productclank.com
- api.realedger.xyz
- doc-extract-api.thestarboy9696-4ef.workers.dev
- link-preview-cache-api.onrender.com
- link-preview-api-z4nf.onrender.com
- api.fuelsignal.ai
- csno.cc
- api.polyform.org
- resolve.exende.dev
- seo.cyberwarex.com
- x402.pkgproof.net
- staging.flint.network
- polyform.polyform-org.workers.dev
- api.virae.ai
- retry.exende.dev
- evidence.guildpilot.app
- vortex.rohnelt.dev
- kortex.rohnelt.dev
- aura.rohnelt.dev
- photos-x402.t77kv6t7wb.workers.dev
- api.whitepapergrey.com
- api.obeliskapp.io
- vendsdk.com
- api.stackgoai.com
- tools.speccy.cloud
- api.agentic-swarm-marketplace.com
- sec-filing-proof.mattskowronis.workers.dev
- srv1553682.hstgr.cloud
- e-commerce-price-monitoring-production.up.railway.app
- api-production-8785.up.railway.app
- derivatives-pricer-production.up.railway.app
- agentic-reservations.vercel.app
- email-preflight-api.vercel.app
- mcp-snowy-dew-9447.fly.dev
- dev.gavedu.com
- kronos.forgemesh.io
- x402.smartmoney.market
- redbtco.com
- alphavantage.x402.paywithlocus.com
- fal.x402.paywithlocus.com
- latamref.dev
- api.safe4.ai
- clado.x402.paywithlocus.com
- hyperliquid-x402.rajdeep-dutta-in.workers.dev
- openrouter.x402.stage.paywithlocus.com
- soren.com
- workbot1.oddsys.org
- sh-origin.walls.sh
- agents.withzero.xyz
- route-catalog.krimskrams.xyz
- hardwarehunter.io
- q402.quackai.ai
- api.x402passport.xyz
- api.trixielasagne.com
- stableproduct.dev
- witnessd.vip
- onchain-toolkit.bowling-anthony.workers.dev
- x402-fuelprice-poc.theliminalguy.workers.dev
- stock-price.api.klymax402.com
- spawnxchange.com
- locus.report
- faultcode-diagnostic-mcp.bowling-anthony.workers.dev
- vps.phoneagent.xyz
- nut402.codenut.xyz
- agents.bytemine.ai
- mapbox.x402.paywithlocus.com
- lazaretto.dev
- thepaliworkernode.com
- live-listing-proof.mattskowronis.workers.dev
- forgesignals.org
- x402-dataviz-poc.theliminalguy.workers.dev
- crypto-news.api.klymax402.com
- dlf-gateway.agentlabel.workers.dev
- agent-economy-signal-x402-mainnet.bronzetti-andrea.workers.dev
- hosaka-agents.vercel.app
- kari.mayim-mayim.com
- pulse.chainverdict.xyz
- endpoint-intelligence-edge.ldbertoldi.workers.dev
- skowron-compliance-gateway.mattskowronis.workers.dev
- tempfile.0000402.xyz
- text-summarizer.pdfextractapi.workers.dev
- translator.pdfextractapi.workers.dev
- job-posting-parser.pdfextractapi.workers.dev
- trust-score.api.klymax402.com
- twitter-scraper.api.klymax402.com
- energybilltoolkit.co.uk
- jsonrecon.com
- content-risk-scanner.pdfextractapi.workers.dev
- sentiment-analyzer.pdfextractapi.workers.dev
- language-detector.pdfextractapi.workers.dev
- url-risk-analyzer.pdfextractapi.workers.dev
- format-validator.pdfextractapi.workers.dev
- gas-price-comparator.pdfextractapi.workers.dev
- ens-resolver.pdfextractapi.workers.dev
- wallet-risk-snapshot.pdfextractapi.workers.dev
- payable.nsgoods.org
- sanctions.nsgoods.org
- toolbelt402.tpoborne.workers.dev
- unit-converter.pdfextractapi.workers.dev
- currency-converter.pdfextractapi.workers.dev
- email-validator.pdfextractapi.workers.dev
- 21millionpixels.art
- fetchdelta.com
- modell.halowerk.com
- currency-converter.api.klymax402.com
- zero1mind.onrender.com
- mcp.blocksize.info
- x402dir.com
- hexscan.xyz
- arn-x402-payguard-payment-security.rajdeep-dutta-in.workers.dev
- api.dexl.io
- ticks.bnm.farm
- wazir-x402.duckdns.org
- api.wickedapi.com
- api.greyridgesignals.ai
- pagedistill.thumm.workers.dev
- travelcheck-x402.fly.dev
- x402engine.app
- mcpfax-reliability.bowling-anthony.workers.dev

### Removals

- api.m2mcent.com
- api.recallradar.dev
- domain-availability-checker.underscoredone.com
- mcp.viridisconservation.com
- api.lmxcloud.io
- sendquotenow.com
- api.rxatlas.dev
- ba-x402-requirements-agent.onrender.com
- vn-gold-fx-x402-production.up.railway.app
- agent-ready.dev
- api-dev.cueframe.ai
- api.apex-db.org
- mortgage-amortization.underscoredone.com
- json-suite.underscoredone.com
- hash-hmac.underscoredone.com
- cors-header-checker.underscoredone.com
- agenttoll.dev
- cloud.hyrule.host
- api.veritylayer.dev
- kenoodl.com
- induction.aarei.ai
- api.x402video.com
- deepseek.x402.press
- autonomy-api-network.onrender.com
- three.ws
- api.santosautomation.com
- nanobanana-x402.fly.dev
- denpyo-api.hp-vladic.workers.dev
- web-production-78e17.up.railway.app
- preview.agenticinsights.com
- donate.0000402.xyz
- api.erb-llm.com
- datagate-x402.onrender.com
- x402-seller-202595743428.europe-west1.run.app
- trinity-throw-thursday-gravity.trycloudflare.com
- techforce-agents.onrender.com
- 402agent.ai
- etherealgoodsco.store
- k2so.wrong.systems
- goldkey-edge-storefront.noah-ing.workers.dev
- agent-offers-api-replitzip.replit.app
- api.andromalius.io
- api.auctiontrace.com
- web3icon.xyz
- sqlguard-io.fly.dev
- specdelta-kl4hfo6j2q-as.a.run.app
- api.capitalspec.com
- api.tantra-authority.com
- bimi-checker.underscoredone.com
- directory-submission-lite.underscoredone.com
- incorpsignal.com
- api.400860.xyz
- x402-seller.558686.xyz
- x402-wallet.558686.xyz
- x402-key.558686.xyz
- x402-utils.558686.xyz
- paysafe-agent.com
- asistent-crypto.vercel.app
- nodeproxy-production.up.railway.app
- justhandled-agent-gateway.netlify.app
- api.pak-labs.com
- x402-defi-signals.onrender.com
- paulgraham.persona.energy
- afriref.dev
- forex-convert.hergertsynthora.com
- api.402.coffee
- twentyonemillion.art
- structdoc-api.hp-vladic.workers.dev
- hermes-storefront.onrender.com
- api.tronenergyfrog.com
- qr.x402tools.xyz
- macro-pulse-x402.onrender.com
- api.carbon-cashmere.de
- agents.dyoeway.org
- promptqualityscore.com
- staging.toolkit.dev
- transit402.dev
- convrgent.ai
- dns.x402tools.xyz
- api.x-402.online
- k2so-8080.on.ascii.dev
- travel.brij.fi
- obol-x402.fly.dev
- reg.chainverdict.xyz
- lex.chainverdict.xyz
- iamrich402.dylan-caponi.workers.dev
- scan.convrgent.ai
- clanker-banker.agentfetcher.workers.dev

### Recoveries

| Host | From | To |
| --- | --- | --- |
| api.invoket.com | not_ready | ready |
| api.oblique.markets | not_ready | ready |
| agent-commerce-factory-jm.austriaeast.cloudapp.azure.com | not_ready | ready |
| payanagent.com | not_ready | ready |
| x402.freeq.one | not_ready | ready |
| whaletape.xyz | not_ready | ready |
| 10x402.com | not_ready | ready |
| zeroclick.affiliate.com | not_ready | ready |
| api.jpverify.com | not_ready | ready |
| error404.life | not_ready | ready |
| api.tickersfeed.net | not_ready | ready |

### Regressions

| Host | From | To |
| --- | --- | --- |
| tick.hugen.tokyo | ready | not_ready |
| api.hyperextend.xyz | ready | not_ready |
| agent402.tools | ready | not_ready |
| voidfeed.ai | ready | not_ready |
| gridpulse.theaslangroupllc.com | ready | not_ready |
| www.getbags.app | ready | not_ready |
| conc-exe.xyz | ready | not_ready |
| store.agentexchange.work | ready | not_ready |
| sandbox.node4all.com | ready | not_ready |
| wallets-demo-seller-server.calebgcarithers.workers.dev | ready | not_ready |
| racingpulse.theaslangroupllc.com | ready | not_ready |
| x402-mcp.onrender.com | ready | not_ready |
| api.nansen.ai | ready | not_ready |
| stablecoinpulse.theaslangroupllc.com | ready | not_ready |
| gate402.app | ready | not_ready |
| pro-api.coinmarketcap.com | ready | not_ready |
| pulse.theaslangroupllc.com | ready | not_ready |
| arbipulse.theaslangroupllc.com | ready | not_ready |
| onchainpulse.theaslangroupllc.com | ready | not_ready |
| x402-stablecoin-data-demo.ryan-ee4.workers.dev | ready | not_ready |
| waterpulse.theaslangroupllc.com | ready | not_ready |
| coil.trade | ready | not_ready |
| macropulse.theaslangroupllc.com | ready | not_ready |
| chain-analyzer.com | ready | not_ready |
| api.osf-master-server.com | ready | unreachable |
| tollbooth-hello-testnet.sjwilliams8.workers.dev | ready | not_ready |
| api.babyblueviper.com | ready | not_ready |
| app.heinrichstech.com | ready | not_ready |
| clinicalintelpulse.theaslangroupllc.com | ready | not_ready |
| citepulse.theaslangroupllc.com | ready | not_ready |
| diet.agentic-jp.com | ready | not_ready |
| prospectpulse.theaslangroupllc.com | ready | not_ready |
| careerpulse.theaslangroupllc.com | ready | not_ready |
| harvestpulse.theaslangroupllc.com | ready | not_ready |
| filingspulse.theaslangroupllc.com | ready | not_ready |
| marketpulse.theaslangroupllc.com | ready | not_ready |
| geopoliticalpulse.theaslangroupllc.com | ready | not_ready |
| gamepulse.theaslangroupllc.com | ready | not_ready |
| alphapulse.theaslangroupllc.com | ready | not_ready |
| api.biotechcatalystsentinel.com | ready | not_ready |
| autopulse.theaslangroupllc.com | ready | not_ready |
| houjin.agentic-jp.com | ready | not_ready |
| weather.agentic-jp.com | ready | not_ready |
| mysticapi.com | ready | not_ready |
| transit.agentic-jp.com | ready | not_ready |
| debtpulse.theaslangroupllc.com | ready | not_ready |
| cryptopulse.theaslangroupllc.com | ready | not_ready |
| compliancepulse.theaslangroupllc.com | ready | not_ready |
| climatepulse.theaslangroupllc.com | ready | not_ready |
| venturepulse.theaslangroupllc.com | ready | not_ready |
| tradepulse.theaslangroupllc.com | ready | not_ready |
| tablepulse.theaslangroupllc.com | ready | not_ready |
| mindpulse.theaslangroupllc.com | ready | not_ready |
| cyberpulse.theaslangroupllc.com | ready | not_ready |
| wealthpulse.theaslangroupllc.com | ready | not_ready |
| truthpulse.theaslangroupllc.com | ready | not_ready |
| taxpulse.theaslangroupllc.com | ready | not_ready |
| talentpulse.theaslangroupllc.com | ready | not_ready |
| scholarpulse.theaslangroupllc.com | ready | not_ready |
| scentpulse.theaslangroupllc.com | ready | not_ready |
| proppulse.theaslangroupllc.com | ready | not_ready |
| policypulse.theaslangroupllc.com | ready | not_ready |
| parentpulse.theaslangroupllc.com | ready | not_ready |
| longevitypulse.theaslangroupllc.com | ready | not_ready |
| legalpulse.theaslangroupllc.com | ready | not_ready |
| immigrationpulse.theaslangroupllc.com | ready | not_ready |
| grantpulse.theaslangroupllc.com | ready | not_ready |
| govspendpulse.theaslangroupllc.com | ready | not_ready |
| glowpulse.theaslangroupllc.com | ready | not_ready |
| footballpulse.theaslangroupllc.com | ready | not_ready |
| fitpulse.theaslangroupllc.com | ready | not_ready |
| fieldpulse.theaslangroupllc.com | ready | not_ready |
| esgpulse.theaslangroupllc.com | ready | not_ready |
| edupulse.theaslangroupllc.com | ready | not_ready |
| econsignalpulse.theaslangroupllc.com | ready | not_ready |
| x402-agent-store.rileycraig14.workers.dev | ready | not_ready |
| rest.staging.wagmi.productions | ready | not_ready |
| x402-stock-indicators.vercel.app | ready | not_ready |
| riskpulse.theaslangroupllc.com | ready | not_ready |
| www.hoodgrow.com | ready | not_ready |
| energy.halowerk.com | ready | not_ready |
| api.you.com | ready | not_ready |
| airdroppulse.theaslangroupllc.com | ready | not_ready |
| agent-arcade.use.x402atlas.com | ready | not_ready |
| twitr.sh | ready | not_ready |
| travelpulse.theaslangroupllc.com | ready | not_ready |
| giftpulse.theaslangroupllc.com | ready | not_ready |
| www.x402financialdata.com | ready | not_ready |
| api-staging.eckari.com | ready | not_ready |
| x402.aispace.bot | ready | not_ready |
| keystone-opportunity-api.keystone-opportunity.workers.dev | ready | unreachable |
| wallets-demo-seller-server.agent-payments-testing.workers.dev | ready | not_ready |
| tiktok.palmyr.ai | ready | not_ready |
| pf-x402-api-testnet.ahndohun1.workers.dev | ready | not_ready |
| agent-fact-receipts-staging.131313122.workers.dev | ready | not_ready |
| gateway.spraay.app | ready | not_ready |
| api2ls.com | ready | not_ready |
| secondopinionx402.com | ready | not_ready |
| animica.dev | ready | not_ready |
| tollbooth-fdic-verify-testnet.sjwilliams8.workers.dev | ready | not_ready |
| api.eucompliance.tools | ready | not_ready |
| x402.yodeler.xyz | ready | not_ready |

### Changed payment routes

| Host | Field | From | To |
| --- | --- | --- | --- |
| x402.ottoai.services | networks | eip155:137, eip155:8453, solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp | eip155:8453, solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp |
| api.hyperextend.xyz | schemes | batch-settlement, exact | exact |
| api.robotsshop.io | networks | eip155:137, eip155:8453 | eip155:8453 |
| x402-mcp.onrender.com | networks | eip155:8453 | eip155:42161, eip155:8453, solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp |
| app.suedeai.ai | networks | base, eip155:8453 | eip155:8453 |
| 402.com.tr | networks | eip155:8453 | eip155:137, eip155:8453 |
| api.invoket.com | networks | eip155:8453, solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp | eip155:8453 |
| x402tap.com | networks | eip155:8453, solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp | eip155:137, eip155:42161, eip155:8453, solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp |
| api.402rates.com | networks | eip155:137, eip155:42161, eip155:8453 | eip155:137, eip155:42161, eip155:50, eip155:8453 |

### Changed prices

| Host | Field | From | To |
| --- | --- | --- | --- |
| api.justaname.id | min_usdc | 0.001 | 0.005 |
| api.justaname.id | max_usdc | 0.001 | 0.005 |
| api.hyperextend.xyz | min_usdc | 0.002 | 0.111 |
| api.hyperextend.xyz | max_usdc | 0.002 | 0.111 |
| dripstack.xyz | min_usdc | 0.5 | 1.5 |
| dripstack.xyz | max_usdc | 0.5 | 1.5 |
| api.stocktrends.com | min_usdc | 0.0025 | 0.05 |
| api.stocktrends.com | max_usdc | 0.0025 | 0.05 |
| options.lonestaroracle.xyz | min_usdc | 0.05 | 0.01 |
| options.lonestaroracle.xyz | max_usdc | 0.05 | 0.01 |
| www.tereno.xyz | min_usdc | 0.03 | 0.005 |
| www.tereno.xyz | max_usdc | 0.03 | 0.005 |
| onchainpulse.theaslangroupllc.com | min_usdc | 0.05 | 0.015 |
| onchainpulse.theaslangroupllc.com | max_usdc | 0.05 | 0.015 |
| coil.trade | min_usdc | 0.005 | 0.001 |
| coil.trade | max_usdc | 0.005 | 0.001 |
| api.babyblueviper.com | min_usdc | 0.030897 | 0.023304 |
| api.babyblueviper.com | max_usdc | 0.030897 | 0.023304 |
| api.kadec0.xyz | min_usdc | 0.05 | 0.03 |
| api.kadec0.xyz | max_usdc | 0.05 | 0.03 |
| api.basefeed.io | min_usdc | 0.005 | 0.001 |
| api.basefeed.io | max_usdc | 0.005 | 0.001 |
| ylk.one | min_usdc | 0.02 | 0.01 |
| ylk.one | max_usdc | 0.02 | 0.01 |
| astatelypleasuredome.com | min_usdc | 0.001055 | 0.001061 |
| astatelypleasuredome.com | max_usdc | 0.001055 | 0.001061 |
| alphapulse.theaslangroupllc.com | min_usdc | 0.1 | 0.08 |
| alphapulse.theaslangroupllc.com | max_usdc | 0.1 | 0.08 |
| x402.cloudpulsepoint.com | min_usdc | 0.01 | 0.03 |
| x402.cloudpulsepoint.com | max_usdc | 0.01 | 0.03 |
| aeml-x402.zeabur.app | min_usdc | 0.03 | 0.01 |
| aeml-x402.zeabur.app | max_usdc | 0.03 | 0.01 |
| api.agentx402.ai | min_usdc | 0.004 | 0.008 |
| api.agentx402.ai | max_usdc | 0.004 | 0.008 |
| api.invoket.com | min_usdc | 0.001 | 0.01 |
| signalpulse.theaslangroupllc.com | min_usdc | 2 | 0.05 |
| signalpulse.theaslangroupllc.com | max_usdc | 2 | 0.05 |
| debtpulse.theaslangroupllc.com | min_usdc | 0.05 | 0.08 |
| debtpulse.theaslangroupllc.com | max_usdc | 0.05 | 0.08 |
| api.certaindata.ai | min_usdc | 0.015 | 0.007 |
| api.certaindata.ai | max_usdc | 0.015 | 0.007 |
| tradepulse.theaslangroupllc.com | min_usdc | 0.1 | 0.12 |
| tradepulse.theaslangroupllc.com | max_usdc | 0.1 | 0.12 |
| tablepulse.theaslangroupllc.com | min_usdc | 0.1 | 0.08 |
| tablepulse.theaslangroupllc.com | max_usdc | 0.1 | 0.08 |
| mindpulse.theaslangroupllc.com | min_usdc | 0.1 | 0.08 |
| mindpulse.theaslangroupllc.com | max_usdc | 0.1 | 0.08 |
| cyberpulse.theaslangroupllc.com | min_usdc | 0.15 | 0.02 |
| cyberpulse.theaslangroupllc.com | max_usdc | 0.15 | 0.02 |
| taxpulse.theaslangroupllc.com | min_usdc | 0.5 | 12 |
| taxpulse.theaslangroupllc.com | max_usdc | 0.5 | 12 |
| scholarpulse.theaslangroupllc.com | min_usdc | 0.12 | 0.08 |
| scholarpulse.theaslangroupllc.com | max_usdc | 0.12 | 0.08 |
| scentpulse.theaslangroupllc.com | min_usdc | 0.1 | 0.08 |
| scentpulse.theaslangroupllc.com | max_usdc | 0.1 | 0.08 |
| longevitypulse.theaslangroupllc.com | min_usdc | 0.2 | 0.12 |
| longevitypulse.theaslangroupllc.com | max_usdc | 0.2 | 0.12 |
| govspendpulse.theaslangroupllc.com | min_usdc | 0.2 | 0.15 |
| govspendpulse.theaslangroupllc.com | max_usdc | 0.2 | 0.15 |
| glowpulse.theaslangroupllc.com | min_usdc | 0.08 | 0.1 |
| glowpulse.theaslangroupllc.com | max_usdc | 0.08 | 0.1 |
| fieldpulse.theaslangroupllc.com | min_usdc | 0.2 | 0.08 |
| fieldpulse.theaslangroupllc.com | max_usdc | 0.2 | 0.08 |
| econsignalpulse.theaslangroupllc.com | min_usdc | 0.2 | 0.15 |
| econsignalpulse.theaslangroupllc.com | max_usdc | 0.2 | 0.15 |
| ot-intel-api.onrender.com | min_usdc | 0.01 | 0.02 |
| ot-intel-api.onrender.com | max_usdc | 0.01 | 0.02 |
| x402.asterpay.io | min_usdc | 0.01 | 0.005 |
| x402.asterpay.io | max_usdc | 0.01 | 0.005 |
| rubric-protocol.com | min_usdc | 0.005 | 0.001 |
| rubric-protocol.com | max_usdc | 0.005 | 0.001 |
| modelprices.xyz | min_usdc | 0.01 | 0.02 |
| modelprices.xyz | max_usdc | 0.01 | 0.02 |
| api.aventtech.com | min_usdc | 0.005 | 0.003 |
| api.aventtech.com | max_usdc | 0.005 | 0.003 |
| api.lastlookdata.com | min_usdc | 0.02 | 0.01 |
| api.lastlookdata.com | max_usdc | 0.02 | 0.01 |
| oyapicks.app | min_usdc | 0.02 | 0.03 |
| oyapicks.app | max_usdc | 0.02 | 0.03 |
| api.truthbear.co | min_usdc | 0.25 | 0.005 |
| api.truthbear.co | max_usdc | 0.25 | 0.005 |
| api.robinx.io | min_usdc | 0.01 | 0.03 |
| api.robinx.io | max_usdc | 0.01 | 0.03 |
| finance-api.kdlcfa.workers.dev | min_usdc | 0.01 | 0.05 |
| finance-api.kdlcfa.workers.dev | max_usdc | 0.01 | 0.05 |
| api.delx.ai | min_usdc | 0.002 | 0.01 |
| api.delx.ai | max_usdc | 0.002 | 0.01 |
| 4yearcycle.com | min_usdc | 0.03 | 0.01 |
| 4yearcycle.com | max_usdc | 0.03 | 0.01 |
| open-pay.jp | min_usdc | 0.005 | 0.01 |
| open-pay.jp | max_usdc | 0.005 | 0.01 |
| x402-filings.datalayer.workers.dev | min_usdc | 0.01 | 0.02 |
| x402-filings.datalayer.workers.dev | max_usdc | 0.01 | 0.02 |
| 5-9-107-124.nip.io | min_usdc | 0.01 | 0.02 |
| 5-9-107-124.nip.io | max_usdc | 0.01 | 0.02 |
| data.rcqsignals.com | min_usdc | 0.03 | 0.05 |
| data.rcqsignals.com | max_usdc | 0.03 | 0.05 |
| api.fetchx402.com | min_usdc | 0.015 | 0.005 |
| api.fetchx402.com | max_usdc | 0.015 | 0.005 |
| rest.coincap.io | min_usdc | 0.01 | 0.002 |
| rest.coincap.io | max_usdc | 0.01 | 0.002 |
| twitr.sh | min_usdc | 0.024 | 0.0012 |
| twitr.sh | max_usdc | 0.024 | 0.0012 |
| eltociear-skill-audit.hf.space | min_usdc | 0.02 | 0.005 |
| eltociear-skill-audit.hf.space | max_usdc | 0.02 | 0.005 |
| tools.halowerk.com | min_usdc | 0.004 | 0.002 |
| tools.halowerk.com | max_usdc | 0.004 | 0.002 |
| api.eckari.com | min_usdc | 0.001 | 0.003 |
| api.eckari.com | max_usdc | 0.001 | 0.003 |
| api.aitrailblazer.net | min_usdc | 0.03 | 0.6 |
| api.aitrailblazer.net | max_usdc | 0.03 | 0.6 |
| ai-data-marketplace-1042299154756.us-central1.run.app | min_usdc | 0.003 | 0.004 |
| ai-data-marketplace-1042299154756.us-central1.run.app | max_usdc | 0.003 | 0.004 |
| agentreader.dev | min_usdc | 0.05 | 0.01 |
| agentreader.dev | max_usdc | 0.05 | 0.01 |
| api.macaroonnetwork.com | min_usdc | 0.001 | 0.015 |
| api.macaroonnetwork.com | max_usdc | 0.001 | 0.015 |
| api.qist.info | min_usdc | 0.1 | 0.01 |
| api.qist.info | max_usdc | 0.1 | 0.01 |
| trust-agent.io | min_usdc | 0.002 | 0.01 |
| trust-agent.io | max_usdc | 0.002 | 0.01 |
| vedetta.dethboy.com | min_usdc | 0.01 | 0.03 |
| vedetta.dethboy.com | max_usdc | 0.01 | 0.03 |
| x402.fenixfoundry.com | min_usdc | 0.003 | 0.005 |
| x402.fenixfoundry.com | max_usdc | 0.003 | 0.005 |
| talkshi.com | min_usdc | 5 | 0.001 |
| talkshi.com | max_usdc | 5 | 0.001 |
| api.jarvisclaw.ai | min_usdc | 0.001656 | 0.003312 |
| api.jarvisclaw.ai | max_usdc | 0.001656 | 0.003312 |
| animica.dev | min_usdc | 0.005932 | 0.005863 |
| animica.dev | max_usdc | 0.005932 | 0.005863 |
| agents.nibiashara.biz | min_usdc | 0.1 | 0.02 |
| agents.nibiashara.biz | max_usdc | 0.1 | 0.02 |
| x402.getautomatedrcm.com | min_usdc | 0.02 | 0.01 |
| x402.getautomatedrcm.com | max_usdc | 0.02 | 0.01 |
| hmo.payapi.market | min_usdc | 0.02 | 0.04 |
| hmo.payapi.market | max_usdc | 0.02 | 0.04 |
| x402-trends-server.onrender.com | min_usdc | 0.05 | 0.005 |
| x402-trends-server.onrender.com | max_usdc | 0.05 | 0.005 |

### Changed pay to

#### gateway.stride20k.com

##### From

- 9754a6d8b3ab65a5a57208f0f0b2447a2301fbd7471c6db4dad946ae9cfa1063

##### To

- 1703c72565b2ec28d1805cc33e17f415b837a91d4dd124518f59e66f67c048d8

##### In common

0

#### api.402rates.com

##### From

- 43a2c4b1c1fafb2af6502ceb5cdcfcc60cd7fd5cf8882e57ef91fc546d094adb

##### To

- 43a2c4b1c1fafb2af6502ceb5cdcfcc60cd7fd5cf8882e57ef91fc546d094adb
- c540f400df02d2e3435cc097c7bbd74cd9f5c97301a53ecd3ce2c355abd76062

##### In common

1

#### x402-mcp.onrender.com

##### From

- 3712167c120f09c4f686773e6b6a0ede92426d39e3c3ecae9f986129a25fdbf8

##### To

- 13e5449bfb9bcac46ef076bb80ca4cfceed7e5731bed75fd3c87db30a9ea97a8

##### In common

0

#### api.certaindata.ai

##### From

- 5dc71f2eb06c03654023fb868256a52b66a99e33d0c52cee5491eaa4fadba6aa

##### To

- 3756accc9a34c351338e9123499dc496fbe97ce105e1875034987e0d76622ed4

##### In common

0

#### api.melvea.com

##### From

- feeb941e56cdeb1543aa926b863cc9ac3f5078376df9b0a57707dc268130321d

##### To

- 837784fc79087fe2e03152ff857f01b72e50040e88fa9a7a138a6f0018688955

##### In common

0

#### api.invoket.com

##### From

- 0e6f6fbdeb408f7ecdb73dd6ad8ce793cfa446c0335951ae77b18785fc549399
- ed40fbc37e38b1207737de6bc20510674c61de6bf5939852335952579f59e5d6

##### To

- ed40fbc37e38b1207737de6bc20510674c61de6bf5939852335952579f59e5d6

##### In common

1

#### api.hergertsynthora.com

##### From

- 55b65500ad1c07c79b8af7eee8b4a83e5e4086e1b57afc87fe285e76927df538

##### To

- 45859136cb838cf236e65e282372f343322ede451f6869a28039b14df01c60e7

##### In common

0

#### api.magentlab.com

##### From

- 2efed542991e8e0d166cb90f2ce211889bf13c365b01cd5f697a5b096b7d6083

##### To

- 5a68de52b4560064ba50ffe9a236254efd0ece6a6f10a168b9236267a2dc88e6

##### In common

0

#### llm-smart.hergertsynthora.com

##### From

- 55b65500ad1c07c79b8af7eee8b4a83e5e4086e1b57afc87fe285e76927df538

##### To

- 45859136cb838cf236e65e282372f343322ede451f6869a28039b14df01c60e7

##### In common

0

#### llm-fast.hergertsynthora.com

##### From

- 55b65500ad1c07c79b8af7eee8b4a83e5e4086e1b57afc87fe285e76927df538

##### To

- 45859136cb838cf236e65e282372f343322ede451f6869a28039b14df01c60e7

##### In common

0

#### payto-preflight.hergertsynthora.com

##### From

- 55b65500ad1c07c79b8af7eee8b4a83e5e4086e1b57afc87fe285e76927df538

##### To

- 45859136cb838cf236e65e282372f343322ede451f6869a28039b14df01c60e7

##### In common

0

#### yahoo-equity-delayed-quote.hergertsynthora.com

##### From

- 55b65500ad1c07c79b8af7eee8b4a83e5e4086e1b57afc87fe285e76927df538

##### To

- 45859136cb838cf236e65e282372f343322ede451f6869a28039b14df01c60e7

##### In common

0

#### coingecko-crypto-price-history.hergertsynthora.com

##### From

- 55b65500ad1c07c79b8af7eee8b4a83e5e4086e1b57afc87fe285e76927df538

##### To

- 45859136cb838cf236e65e282372f343322ede451f6869a28039b14df01c60e7

##### In common

0

#### usgs-realtime-streamflow.hergertsynthora.com

##### From

- 55b65500ad1c07c79b8af7eee8b4a83e5e4086e1b57afc87fe285e76927df538

##### To

- 45859136cb838cf236e65e282372f343322ede451f6869a28039b14df01c60e7

##### In common

0

#### sanctions-screen.hergertsynthora.com

##### From

- 55b65500ad1c07c79b8af7eee8b4a83e5e4086e1b57afc87fe285e76927df538

##### To

- 45859136cb838cf236e65e282372f343322ede451f6869a28039b14df01c60e7

##### In common

0

#### commodity-macro.hergertsynthora.com

##### From

- 55b65500ad1c07c79b8af7eee8b4a83e5e4086e1b57afc87fe285e76927df538

##### To

- 45859136cb838cf236e65e282372f343322ede451f6869a28039b14df01c60e7

##### In common

0

#### inference.hergertsynthora.com

##### From

- 55b65500ad1c07c79b8af7eee8b4a83e5e4086e1b57afc87fe285e76927df538

##### To

- 45859136cb838cf236e65e282372f343322ede451f6869a28039b14df01c60e7

##### In common

0

### Pay to compared

635

### Changed defect state

| Host | Added | Cleared |
| --- | --- | --- |
| api.hyperextend.xyz | amount-atomic | — |
| tick.hugen.tokyo | solana-rail-receivable | — |
| api.anchor-x402.com | bazaar-extension | status-402 |
| www.getbags.app | network-mainnet | — |
| agent402.tools | payto-payable | — |
| voidfeed.ai | solana-rail-receivable | — |
| conc-exe.xyz | payment-required-header | — |
| gridpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| store.agentexchange.work | solana-rail-receivable | — |
| sandbox.node4all.com | network-mainnet | — |
| wallets-demo-seller-server.calebgcarithers.workers.dev | network-mainnet | — |
| pro-api.coinmarketcap.com | transfer-method-signable | — |
| racingpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| agent-arcade.use.x402atlas.com | status-402 | — |
| onchainpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| coil.trade | payto-payable | — |
| x402-mcp.onrender.com | payto-payable | — |
| gate402.app | solana-rail-receivable | — |
| stablecoinpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| macropulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| tollbooth-hello-testnet.sjwilliams8.workers.dev | network-mainnet | — |
| chain-analyzer.com | solana-rail-receivable | — |
| citepulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| arbipulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| pulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| waterpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| api.nansen.ai | transfer-method-signable | — |
| mysticapi.com | solana-rail-receivable | — |
| x402-stablecoin-data-demo.ryan-ee4.workers.dev | network-mainnet | — |
| clinicalintelpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| api.babyblueviper.com | payto-payable | — |
| api.oblique.markets | — | status-402 |
| filingspulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| app.heinrichstech.com | amount-atomic, payto-payable | — |
| tradepulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| autopulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| www.x402financialdata.com | solana-rail-receivable | — |
| careerpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| prospectpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| cryptopulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| taxpulse.theaslangroupllc.com | payto-payable | — |
| geopoliticalpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| compliancepulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| policypulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| shopperpulse.theaslangroupllc.com | amount-atomic, payto-payable | status-402 |
| wealthpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| cyberpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| alphapulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| harvestpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| marketpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| gamepulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| diet.agentic-jp.com | solana-rail-receivable | — |
| houjin.agentic-jp.com | solana-rail-receivable | — |
| api.biotechcatalystsentinel.com | solana-rail-receivable | — |
| transit.agentic-jp.com | solana-rail-receivable | — |
| climatepulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| venturepulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| truthpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| talentpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| tablepulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| scholarpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| scentpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| proppulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| parentpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| mindpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| longevitypulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| legalpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| grantpulse.theaslangroupllc.com | payto-payable | — |
| govspendpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| glowpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| footballpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| fieldpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| esgpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| edupulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| econsignalpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| debtpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| weather.agentic-jp.com | solana-rail-receivable | — |
| airdroppulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| travelpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| immigrationpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| fitpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| wallets-demo-seller-server.agent-payments-testing.workers.dev | network-mainnet | — |
| rest.staging.wagmi.productions | network-mainnet | — |
| x402-stock-indicators.vercel.app | solana-rail-receivable | — |
| payanagent.com | — | payment-required-header |
| api.eucompliance.tools | solana-rail-receivable | — |
| twitr.sh | solana-rail-receivable | — |
| riskpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| api.invoket.com | — | bazaar-extension |
| x402.aispace.bot | status-402 | — |
| giftpulse.theaslangroupllc.com | amount-atomic, payto-payable | — |
| api.jpverify.com | — | status-402 |
| agent-commerce-factory-jm.austriaeast.cloudapp.azure.com | — | status-402 |
| animica.dev | payto-payable | — |
| api.you.com | solana-rail-receivable | — |
| whaletape.xyz | — | status-402 |
| 10x402.com | — | status-402 |
| api-staging.eckari.com | network-mainnet | — |
| zeroclick.affiliate.com | — | status-402 |
| x402.freeq.one | — | status-402 |
| energy.halowerk.com | status-402 | — |
| tiktok.palmyr.ai | status-402 | — |
| www.hoodgrow.com | status-402 | — |
| x402-agent-store.rileycraig14.workers.dev | solana-rail-receivable | — |
| agent-economy-sec-verifier.onrender.com | — | status-402 |
| pf-x402-api-testnet.ahndohun1.workers.dev | network-mainnet | — |
| agent-fact-receipts-staging.131313122.workers.dev | network-mainnet | — |
| error404.life | — | payment-required-header |
| api.tickersfeed.net | — | status-402 |
| api2ls.com | solana-rail-receivable | — |
| secondopinionx402.com | payto-payable | — |
| tollbooth-fdic-verify-testnet.sjwilliams8.workers.dev | network-mainnet | — |
| api-staging.you.com | network-mainnet | status-402 |
| gateway.spraay.app | status-402 | — |
| x402.yodeler.xyz | solana-rail-receivable | — |

### Changelog

- 2026-W36 (snapshot 5) against 2026-W35 (snapshot 4): 1089 hosts this week, 972 hosts last week, 884 hosts in both.
- Newly listed by a feed: agentworld.me, patentpulse.theaslangroupllc.com, ephemeris.561.group, mail.cusethejuice.com, api-onchain.optimai.network, copperhead.lonestaroracle.xyz, cottonmouth.lonestaroracle.xyz, rattler.lonestaroracle.xyz, the-stall.intuitek.ai, signal.keelbase.io, x402.blackswan.wtf, curatoria.dev, api.gmfarcaster.com, x402.sniperx.fun, 402signal.com, stationfx.com, x402.outpimp.com, node-starter--maxujon18.replit.app, www.celerapi.com, agent.massive.com, lion-x402.lionmaster-operations.workers.dev, openrelay.hggfffdfy687.workers.dev, agent-api-production.tim1712.workers.dev, agent-api-testnet.tim1712.workers.dev, grov.fun, oracle.cyberwarex.com, web.cyberwarex.com, search.cyberwarex.com, osha-search.46-224-157-88.sslip.io, x402-echo-service.onrender.com, task-profit-api.62.238.55.212.sslip.io, bounty-signals.krimskrams.xyz, staging.getbags.app, cyre.dev, aegis-api-mainnet.kadopi.workers.dev, source-claim-proof.mattskowronis.workers.dev, agent.api.0x.org, kino402.com, api.usesaferoute.com, byfaro.ai, centboard.xyz, ip402.xyz, tizona-outpost.venusberg.workers.dev, foundry-par007-machine-revenue-mainnet.inference-chip-index.workers.dev, raptor-base-yields.vercel.app, trading-perps.vercel.app, tenderdelta-preview.mooncakemonkey1.workers.dev, deadchannel.vercel.app, fetchharbor.benlab.download, content-moderation-api-hhy1.onrender.com, relay.preflightstack.com, lion-x402-bible.lionmaster-operations.workers.dev, video.cyberwarex.com, chain.cyberwarex.com, api.zfinia.com, api.newsgurus.ai, ledger-api.novadyne.ai, www.moltbillboard.com, random.preflightstack.com, amoraw.xyz, contextslim.friczero.com, 767-2676.com, 402rpc.com, payload402.edgebytenet.workers.dev, api.runx.ai, api.ccbaydata.com, license.ccbaydata.com, www.vokko.eu, crawl-preflight.postnov01.workers.dev, x402.donnyautomation.com, agent.connskill.com, spawnxchange-api-485602182462.europe-west4.run.app, api.m2msentinel.com, research.lumenhouse.xyz, musicwire.5432wire.com, italian-company-check-fdsbh7p2bq-oc.a.run.app, wellsyncc-x402.2ng-nhan.workers.dev, api.bakebakebake.no, money-ai-shop.money-ai.workers.dev, cryptoops.friczero.com, godlaws.com, api.resetparatodos.com, agents.dubbleblack.com, agenteconomy.report, api.x402-hosting.com, mcpfax-utility.bowling-anthony.workers.dev, www.productclank.com, api.realedger.xyz, doc-extract-api.thestarboy9696-4ef.workers.dev, link-preview-cache-api.onrender.com, link-preview-api-z4nf.onrender.com, api.fuelsignal.ai, csno.cc, api.polyform.org, resolve.exende.dev, seo.cyberwarex.com, x402.pkgproof.net, staging.flint.network, polyform.polyform-org.workers.dev, api.virae.ai, retry.exende.dev, evidence.guildpilot.app, vortex.rohnelt.dev, kortex.rohnelt.dev, aura.rohnelt.dev, photos-x402.t77kv6t7wb.workers.dev, api.whitepapergrey.com, api.obeliskapp.io, vendsdk.com, api.stackgoai.com, tools.speccy.cloud, api.agentic-swarm-marketplace.com, sec-filing-proof.mattskowronis.workers.dev, srv1553682.hstgr.cloud, e-commerce-price-monitoring-production.up.railway.app, api-production-8785.up.railway.app, derivatives-pricer-production.up.railway.app, agentic-reservations.vercel.app, email-preflight-api.vercel.app, mcp-snowy-dew-9447.fly.dev, dev.gavedu.com, kronos.forgemesh.io, x402.smartmoney.market, redbtco.com, alphavantage.x402.paywithlocus.com, fal.x402.paywithlocus.com, latamref.dev, api.safe4.ai, clado.x402.paywithlocus.com, hyperliquid-x402.rajdeep-dutta-in.workers.dev, openrouter.x402.stage.paywithlocus.com, soren.com, workbot1.oddsys.org, sh-origin.walls.sh, agents.withzero.xyz, route-catalog.krimskrams.xyz, hardwarehunter.io, q402.quackai.ai, api.x402passport.xyz, api.trixielasagne.com, stableproduct.dev, witnessd.vip, onchain-toolkit.bowling-anthony.workers.dev, x402-fuelprice-poc.theliminalguy.workers.dev, stock-price.api.klymax402.com, spawnxchange.com, locus.report, faultcode-diagnostic-mcp.bowling-anthony.workers.dev, vps.phoneagent.xyz, nut402.codenut.xyz, agents.bytemine.ai, mapbox.x402.paywithlocus.com, lazaretto.dev, thepaliworkernode.com, live-listing-proof.mattskowronis.workers.dev, forgesignals.org, x402-dataviz-poc.theliminalguy.workers.dev, crypto-news.api.klymax402.com, dlf-gateway.agentlabel.workers.dev, agent-economy-signal-x402-mainnet.bronzetti-andrea.workers.dev, hosaka-agents.vercel.app, kari.mayim-mayim.com, pulse.chainverdict.xyz, endpoint-intelligence-edge.ldbertoldi.workers.dev, skowron-compliance-gateway.mattskowronis.workers.dev, tempfile.0000402.xyz, text-summarizer.pdfextractapi.workers.dev, translator.pdfextractapi.workers.dev, job-posting-parser.pdfextractapi.workers.dev, trust-score.api.klymax402.com, twitter-scraper.api.klymax402.com, energybilltoolkit.co.uk, jsonrecon.com, content-risk-scanner.pdfextractapi.workers.dev, sentiment-analyzer.pdfextractapi.workers.dev, language-detector.pdfextractapi.workers.dev, url-risk-analyzer.pdfextractapi.workers.dev, format-validator.pdfextractapi.workers.dev, gas-price-comparator.pdfextractapi.workers.dev, ens-resolver.pdfextractapi.workers.dev, wallet-risk-snapshot.pdfextractapi.workers.dev, payable.nsgoods.org, sanctions.nsgoods.org, toolbelt402.tpoborne.workers.dev, unit-converter.pdfextractapi.workers.dev, currency-converter.pdfextractapi.workers.dev, email-validator.pdfextractapi.workers.dev, 21millionpixels.art, fetchdelta.com, modell.halowerk.com, currency-converter.api.klymax402.com, zero1mind.onrender.com, mcp.blocksize.info, x402dir.com, hexscan.xyz, arn-x402-payguard-payment-security.rajdeep-dutta-in.workers.dev, api.dexl.io, ticks.bnm.farm, wazir-x402.duckdns.org, api.wickedapi.com, api.greyridgesignals.ai, pagedistill.thumm.workers.dev, travelcheck-x402.fly.dev, x402engine.app, mcpfax-reliability.bowling-anthony.workers.dev.
- No longer listed by any feed: api.m2mcent.com, api.recallradar.dev, domain-availability-checker.underscoredone.com, mcp.viridisconservation.com, api.lmxcloud.io, sendquotenow.com, api.rxatlas.dev, ba-x402-requirements-agent.onrender.com, vn-gold-fx-x402-production.up.railway.app, agent-ready.dev, api-dev.cueframe.ai, api.apex-db.org, mortgage-amortization.underscoredone.com, json-suite.underscoredone.com, hash-hmac.underscoredone.com, cors-header-checker.underscoredone.com, agenttoll.dev, cloud.hyrule.host, api.veritylayer.dev, kenoodl.com, induction.aarei.ai, api.x402video.com, deepseek.x402.press, autonomy-api-network.onrender.com, three.ws, api.santosautomation.com, nanobanana-x402.fly.dev, denpyo-api.hp-vladic.workers.dev, web-production-78e17.up.railway.app, preview.agenticinsights.com, donate.0000402.xyz, api.erb-llm.com, datagate-x402.onrender.com, x402-seller-202595743428.europe-west1.run.app, trinity-throw-thursday-gravity.trycloudflare.com, techforce-agents.onrender.com, 402agent.ai, etherealgoodsco.store, k2so.wrong.systems, goldkey-edge-storefront.noah-ing.workers.dev, agent-offers-api-replitzip.replit.app, api.andromalius.io, api.auctiontrace.com, web3icon.xyz, sqlguard-io.fly.dev, specdelta-kl4hfo6j2q-as.a.run.app, api.capitalspec.com, api.tantra-authority.com, bimi-checker.underscoredone.com, directory-submission-lite.underscoredone.com, incorpsignal.com, api.400860.xyz, x402-seller.558686.xyz, x402-wallet.558686.xyz, x402-key.558686.xyz, x402-utils.558686.xyz, paysafe-agent.com, asistent-crypto.vercel.app, nodeproxy-production.up.railway.app, justhandled-agent-gateway.netlify.app, api.pak-labs.com, x402-defi-signals.onrender.com, paulgraham.persona.energy, afriref.dev, forex-convert.hergertsynthora.com, api.402.coffee, twentyonemillion.art, structdoc-api.hp-vladic.workers.dev, hermes-storefront.onrender.com, api.tronenergyfrog.com, qr.x402tools.xyz, macro-pulse-x402.onrender.com, api.carbon-cashmere.de, agents.dyoeway.org, promptqualityscore.com, staging.toolkit.dev, transit402.dev, convrgent.ai, dns.x402tools.xyz, api.x-402.online, k2so-8080.on.ascii.dev, travel.brij.fi, obol-x402.fly.dev, reg.chainverdict.xyz, lex.chainverdict.xyz, iamrich402.dylan-caponi.workers.dev, scan.convrgent.ai, clanker-banker.agentfetcher.workers.dev.
- api.invoket.com answered ready this week after not_ready last week.
- api.oblique.markets answered ready this week after not_ready last week.
- agent-commerce-factory-jm.austriaeast.cloudapp.azure.com answered ready this week after not_ready last week.
- payanagent.com answered ready this week after not_ready last week.
- x402.freeq.one answered ready this week after not_ready last week.
- whaletape.xyz answered ready this week after not_ready last week.
- 10x402.com answered ready this week after not_ready last week.
- zeroclick.affiliate.com answered ready this week after not_ready last week.
- api.jpverify.com answered ready this week after not_ready last week.
- error404.life answered ready this week after not_ready last week.
- api.tickersfeed.net answered ready this week after not_ready last week.
- tick.hugen.tokyo answered not_ready this week after ready last week.
- api.hyperextend.xyz answered not_ready this week after ready last week.
- agent402.tools answered not_ready this week after ready last week.
- voidfeed.ai answered not_ready this week after ready last week.
- gridpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- www.getbags.app answered not_ready this week after ready last week.
- conc-exe.xyz answered not_ready this week after ready last week.
- store.agentexchange.work answered not_ready this week after ready last week.
- sandbox.node4all.com answered not_ready this week after ready last week.
- wallets-demo-seller-server.calebgcarithers.workers.dev answered not_ready this week after ready last week.
- racingpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- x402-mcp.onrender.com answered not_ready this week after ready last week.
- api.nansen.ai answered not_ready this week after ready last week.
- stablecoinpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- gate402.app answered not_ready this week after ready last week.
- pro-api.coinmarketcap.com answered not_ready this week after ready last week.
- pulse.theaslangroupllc.com answered not_ready this week after ready last week.
- arbipulse.theaslangroupllc.com answered not_ready this week after ready last week.
- onchainpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- x402-stablecoin-data-demo.ryan-ee4.workers.dev answered not_ready this week after ready last week.
- waterpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- coil.trade answered not_ready this week after ready last week.
- macropulse.theaslangroupllc.com answered not_ready this week after ready last week.
- chain-analyzer.com answered not_ready this week after ready last week.
- api.osf-master-server.com answered unreachable this week after ready last week.
- tollbooth-hello-testnet.sjwilliams8.workers.dev answered not_ready this week after ready last week.
- api.babyblueviper.com answered not_ready this week after ready last week.
- app.heinrichstech.com answered not_ready this week after ready last week.
- clinicalintelpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- citepulse.theaslangroupllc.com answered not_ready this week after ready last week.
- diet.agentic-jp.com answered not_ready this week after ready last week.
- prospectpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- careerpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- harvestpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- filingspulse.theaslangroupllc.com answered not_ready this week after ready last week.
- marketpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- geopoliticalpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- gamepulse.theaslangroupllc.com answered not_ready this week after ready last week.
- alphapulse.theaslangroupllc.com answered not_ready this week after ready last week.
- api.biotechcatalystsentinel.com answered not_ready this week after ready last week.
- autopulse.theaslangroupllc.com answered not_ready this week after ready last week.
- houjin.agentic-jp.com answered not_ready this week after ready last week.
- weather.agentic-jp.com answered not_ready this week after ready last week.
- mysticapi.com answered not_ready this week after ready last week.
- transit.agentic-jp.com answered not_ready this week after ready last week.
- debtpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- cryptopulse.theaslangroupllc.com answered not_ready this week after ready last week.
- compliancepulse.theaslangroupllc.com answered not_ready this week after ready last week.
- climatepulse.theaslangroupllc.com answered not_ready this week after ready last week.
- venturepulse.theaslangroupllc.com answered not_ready this week after ready last week.
- tradepulse.theaslangroupllc.com answered not_ready this week after ready last week.
- tablepulse.theaslangroupllc.com answered not_ready this week after ready last week.
- mindpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- cyberpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- wealthpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- truthpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- taxpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- talentpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- scholarpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- scentpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- proppulse.theaslangroupllc.com answered not_ready this week after ready last week.
- policypulse.theaslangroupllc.com answered not_ready this week after ready last week.
- parentpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- longevitypulse.theaslangroupllc.com answered not_ready this week after ready last week.
- legalpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- immigrationpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- grantpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- govspendpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- glowpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- footballpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- fitpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- fieldpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- esgpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- edupulse.theaslangroupllc.com answered not_ready this week after ready last week.
- econsignalpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- x402-agent-store.rileycraig14.workers.dev answered not_ready this week after ready last week.
- rest.staging.wagmi.productions answered not_ready this week after ready last week.
- x402-stock-indicators.vercel.app answered not_ready this week after ready last week.
- riskpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- www.hoodgrow.com answered not_ready this week after ready last week.
- energy.halowerk.com answered not_ready this week after ready last week.
- api.you.com answered not_ready this week after ready last week.
- airdroppulse.theaslangroupllc.com answered not_ready this week after ready last week.
- agent-arcade.use.x402atlas.com answered not_ready this week after ready last week.
- twitr.sh answered not_ready this week after ready last week.
- travelpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- giftpulse.theaslangroupllc.com answered not_ready this week after ready last week.
- www.x402financialdata.com answered not_ready this week after ready last week.
- api-staging.eckari.com answered not_ready this week after ready last week.
- x402.aispace.bot answered not_ready this week after ready last week.
- keystone-opportunity-api.keystone-opportunity.workers.dev answered unreachable this week after ready last week.
- wallets-demo-seller-server.agent-payments-testing.workers.dev answered not_ready this week after ready last week.
- tiktok.palmyr.ai answered not_ready this week after ready last week.
- pf-x402-api-testnet.ahndohun1.workers.dev answered not_ready this week after ready last week.
- agent-fact-receipts-staging.131313122.workers.dev answered not_ready this week after ready last week.
- gateway.spraay.app answered not_ready this week after ready last week.
- api2ls.com answered not_ready this week after ready last week.
- secondopinionx402.com answered not_ready this week after ready last week.
- animica.dev answered not_ready this week after ready last week.
- tollbooth-fdic-verify-testnet.sjwilliams8.workers.dev answered not_ready this week after ready last week.
- api.eucompliance.tools answered not_ready this week after ready last week.
- x402.yodeler.xyz answered not_ready this week after ready last week.
- x402.ottoai.services changed its networks: ["eip155:137","eip155:8453","solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp"] to ["eip155:8453","solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp"].
- api.hyperextend.xyz changed its schemes: ["batch-settlement","exact"] to ["exact"].
- api.robotsshop.io changed its networks: ["eip155:137","eip155:8453"] to ["eip155:8453"].
- x402-mcp.onrender.com changed its networks: ["eip155:8453"] to ["eip155:42161","eip155:8453","solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp"].
- app.suedeai.ai changed its networks: ["base","eip155:8453"] to ["eip155:8453"].
- 402.com.tr changed its networks: ["eip155:8453"] to ["eip155:137","eip155:8453"].
- api.invoket.com changed its networks: ["eip155:8453","solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp"] to ["eip155:8453"].
- x402tap.com changed its networks: ["eip155:8453","solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp"] to ["eip155:137","eip155:42161","eip155:8453","solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp"].
- api.402rates.com changed its networks: ["eip155:137","eip155:42161","eip155:8453"] to ["eip155:137","eip155:42161","eip155:50","eip155:8453"].
- api.justaname.id changed its min_usdc: 0.001 to 0.005.
- api.justaname.id changed its max_usdc: 0.001 to 0.005.
- api.hyperextend.xyz changed its min_usdc: 0.002 to 0.111.
- api.hyperextend.xyz changed its max_usdc: 0.002 to 0.111.
- dripstack.xyz changed its min_usdc: 0.5 to 1.5.
- dripstack.xyz changed its max_usdc: 0.5 to 1.5.
- api.stocktrends.com changed its min_usdc: 0.0025 to 0.05.
- api.stocktrends.com changed its max_usdc: 0.0025 to 0.05.
- options.lonestaroracle.xyz changed its min_usdc: 0.05 to 0.01.
- options.lonestaroracle.xyz changed its max_usdc: 0.05 to 0.01.
- www.tereno.xyz changed its min_usdc: 0.03 to 0.005.
- www.tereno.xyz changed its max_usdc: 0.03 to 0.005.
- onchainpulse.theaslangroupllc.com changed its min_usdc: 0.05 to 0.015.
- onchainpulse.theaslangroupllc.com changed its max_usdc: 0.05 to 0.015.
- coil.trade changed its min_usdc: 0.005 to 0.001.
- coil.trade changed its max_usdc: 0.005 to 0.001.
- api.babyblueviper.com changed its min_usdc: 0.030897 to 0.023304.
- api.babyblueviper.com changed its max_usdc: 0.030897 to 0.023304.
- api.kadec0.xyz changed its min_usdc: 0.05 to 0.03.
- api.kadec0.xyz changed its max_usdc: 0.05 to 0.03.
- api.basefeed.io changed its min_usdc: 0.005 to 0.001.
- api.basefeed.io changed its max_usdc: 0.005 to 0.001.
- ylk.one changed its min_usdc: 0.02 to 0.01.
- ylk.one changed its max_usdc: 0.02 to 0.01.
- astatelypleasuredome.com changed its min_usdc: 0.001055 to 0.001061.
- astatelypleasuredome.com changed its max_usdc: 0.001055 to 0.001061.
- alphapulse.theaslangroupllc.com changed its min_usdc: 0.1 to 0.08.
- alphapulse.theaslangroupllc.com changed its max_usdc: 0.1 to 0.08.
- x402.cloudpulsepoint.com changed its min_usdc: 0.01 to 0.03.
- x402.cloudpulsepoint.com changed its max_usdc: 0.01 to 0.03.
- aeml-x402.zeabur.app changed its min_usdc: 0.03 to 0.01.
- aeml-x402.zeabur.app changed its max_usdc: 0.03 to 0.01.
- api.agentx402.ai changed its min_usdc: 0.004 to 0.008.
- api.agentx402.ai changed its max_usdc: 0.004 to 0.008.
- api.invoket.com changed its min_usdc: 0.001 to 0.01.
- signalpulse.theaslangroupllc.com changed its min_usdc: 2 to 0.05.
- signalpulse.theaslangroupllc.com changed its max_usdc: 2 to 0.05.
- debtpulse.theaslangroupllc.com changed its min_usdc: 0.05 to 0.08.
- debtpulse.theaslangroupllc.com changed its max_usdc: 0.05 to 0.08.
- api.certaindata.ai changed its min_usdc: 0.015 to 0.007.
- api.certaindata.ai changed its max_usdc: 0.015 to 0.007.
- tradepulse.theaslangroupllc.com changed its min_usdc: 0.1 to 0.12.
- tradepulse.theaslangroupllc.com changed its max_usdc: 0.1 to 0.12.
- tablepulse.theaslangroupllc.com changed its min_usdc: 0.1 to 0.08.
- tablepulse.theaslangroupllc.com changed its max_usdc: 0.1 to 0.08.
- mindpulse.theaslangroupllc.com changed its min_usdc: 0.1 to 0.08.
- mindpulse.theaslangroupllc.com changed its max_usdc: 0.1 to 0.08.
- cyberpulse.theaslangroupllc.com changed its min_usdc: 0.15 to 0.02.
- cyberpulse.theaslangroupllc.com changed its max_usdc: 0.15 to 0.02.
- taxpulse.theaslangroupllc.com changed its min_usdc: 0.5 to 12.
- taxpulse.theaslangroupllc.com changed its max_usdc: 0.5 to 12.
- scholarpulse.theaslangroupllc.com changed its min_usdc: 0.12 to 0.08.
- scholarpulse.theaslangroupllc.com changed its max_usdc: 0.12 to 0.08.
- scentpulse.theaslangroupllc.com changed its min_usdc: 0.1 to 0.08.
- scentpulse.theaslangroupllc.com changed its max_usdc: 0.1 to 0.08.
- longevitypulse.theaslangroupllc.com changed its min_usdc: 0.2 to 0.12.
- longevitypulse.theaslangroupllc.com changed its max_usdc: 0.2 to 0.12.
- govspendpulse.theaslangroupllc.com changed its min_usdc: 0.2 to 0.15.
- govspendpulse.theaslangroupllc.com changed its max_usdc: 0.2 to 0.15.
- glowpulse.theaslangroupllc.com changed its min_usdc: 0.08 to 0.1.
- glowpulse.theaslangroupllc.com changed its max_usdc: 0.08 to 0.1.
- fieldpulse.theaslangroupllc.com changed its min_usdc: 0.2 to 0.08.
- fieldpulse.theaslangroupllc.com changed its max_usdc: 0.2 to 0.08.
- econsignalpulse.theaslangroupllc.com changed its min_usdc: 0.2 to 0.15.
- econsignalpulse.theaslangroupllc.com changed its max_usdc: 0.2 to 0.15.
- ot-intel-api.onrender.com changed its min_usdc: 0.01 to 0.02.
- ot-intel-api.onrender.com changed its max_usdc: 0.01 to 0.02.
- x402.asterpay.io changed its min_usdc: 0.01 to 0.005.
- x402.asterpay.io changed its max_usdc: 0.01 to 0.005.
- rubric-protocol.com changed its min_usdc: 0.005 to 0.001.
- rubric-protocol.com changed its max_usdc: 0.005 to 0.001.
- modelprices.xyz changed its min_usdc: 0.01 to 0.02.
- modelprices.xyz changed its max_usdc: 0.01 to 0.02.
- api.aventtech.com changed its min_usdc: 0.005 to 0.003.
- api.aventtech.com changed its max_usdc: 0.005 to 0.003.
- api.lastlookdata.com changed its min_usdc: 0.02 to 0.01.
- api.lastlookdata.com changed its max_usdc: 0.02 to 0.01.
- oyapicks.app changed its min_usdc: 0.02 to 0.03.
- oyapicks.app changed its max_usdc: 0.02 to 0.03.
- api.truthbear.co changed its min_usdc: 0.25 to 0.005.
- api.truthbear.co changed its max_usdc: 0.25 to 0.005.
- api.robinx.io changed its min_usdc: 0.01 to 0.03.
- api.robinx.io changed its max_usdc: 0.01 to 0.03.
- finance-api.kdlcfa.workers.dev changed its min_usdc: 0.01 to 0.05.
- finance-api.kdlcfa.workers.dev changed its max_usdc: 0.01 to 0.05.
- api.delx.ai changed its min_usdc: 0.002 to 0.01.
- api.delx.ai changed its max_usdc: 0.002 to 0.01.
- 4yearcycle.com changed its min_usdc: 0.03 to 0.01.
- 4yearcycle.com changed its max_usdc: 0.03 to 0.01.
- open-pay.jp changed its min_usdc: 0.005 to 0.01.
- open-pay.jp changed its max_usdc: 0.005 to 0.01.
- x402-filings.datalayer.workers.dev changed its min_usdc: 0.01 to 0.02.
- x402-filings.datalayer.workers.dev changed its max_usdc: 0.01 to 0.02.
- 5-9-107-124.nip.io changed its min_usdc: 0.01 to 0.02.
- 5-9-107-124.nip.io changed its max_usdc: 0.01 to 0.02.
- data.rcqsignals.com changed its min_usdc: 0.03 to 0.05.
- data.rcqsignals.com changed its max_usdc: 0.03 to 0.05.
- api.fetchx402.com changed its min_usdc: 0.015 to 0.005.
- api.fetchx402.com changed its max_usdc: 0.015 to 0.005.
- rest.coincap.io changed its min_usdc: 0.01 to 0.002.
- rest.coincap.io changed its max_usdc: 0.01 to 0.002.
- twitr.sh changed its min_usdc: 0.024 to 0.0012.
- twitr.sh changed its max_usdc: 0.024 to 0.0012.
- eltociear-skill-audit.hf.space changed its min_usdc: 0.02 to 0.005.
- eltociear-skill-audit.hf.space changed its max_usdc: 0.02 to 0.005.
- tools.halowerk.com changed its min_usdc: 0.004 to 0.002.
- tools.halowerk.com changed its max_usdc: 0.004 to 0.002.
- api.eckari.com changed its min_usdc: 0.001 to 0.003.
- api.eckari.com changed its max_usdc: 0.001 to 0.003.
- api.aitrailblazer.net changed its min_usdc: 0.03 to 0.6.
- api.aitrailblazer.net changed its max_usdc: 0.03 to 0.6.
- ai-data-marketplace-1042299154756.us-central1.run.app changed its min_usdc: 0.003 to 0.004.
- ai-data-marketplace-1042299154756.us-central1.run.app changed its max_usdc: 0.003 to 0.004.
- agentreader.dev changed its min_usdc: 0.05 to 0.01.
- agentreader.dev changed its max_usdc: 0.05 to 0.01.
- api.macaroonnetwork.com changed its min_usdc: 0.001 to 0.015.
- api.macaroonnetwork.com changed its max_usdc: 0.001 to 0.015.
- api.qist.info changed its min_usdc: 0.1 to 0.01.
- api.qist.info changed its max_usdc: 0.1 to 0.01.
- trust-agent.io changed its min_usdc: 0.002 to 0.01.
- trust-agent.io changed its max_usdc: 0.002 to 0.01.
- vedetta.dethboy.com changed its min_usdc: 0.01 to 0.03.
- vedetta.dethboy.com changed its max_usdc: 0.01 to 0.03.
- x402.fenixfoundry.com changed its min_usdc: 0.003 to 0.005.
- x402.fenixfoundry.com changed its max_usdc: 0.003 to 0.005.
- talkshi.com changed its min_usdc: 5 to 0.001.
- talkshi.com changed its max_usdc: 5 to 0.001.
- api.jarvisclaw.ai changed its min_usdc: 0.001656 to 0.003312.
- api.jarvisclaw.ai changed its max_usdc: 0.001656 to 0.003312.
- animica.dev changed its min_usdc: 0.005932 to 0.005863.
- animica.dev changed its max_usdc: 0.005932 to 0.005863.
- agents.nibiashara.biz changed its min_usdc: 0.1 to 0.02.
- agents.nibiashara.biz changed its max_usdc: 0.1 to 0.02.
- x402.getautomatedrcm.com changed its min_usdc: 0.02 to 0.01.
- x402.getautomatedrcm.com changed its max_usdc: 0.02 to 0.01.
- hmo.payapi.market changed its min_usdc: 0.02 to 0.04.
- hmo.payapi.market changed its max_usdc: 0.02 to 0.04.
- x402-trends-server.onrender.com changed its min_usdc: 0.05 to 0.005.
- x402-trends-server.onrender.com changed its max_usdc: 0.05 to 0.005.
- gateway.stride20k.com changed where it asks to be paid: 1 address digest last week, 1 address digest this week, 0 in common. Whether that is a rotated wallet or a hijacked door is not something two observations can say; a buyer holding the address recomputes the digest and matches.
- api.402rates.com changed where it asks to be paid: 1 address digest last week, 2 address digests this week, 1 in common. Whether that is a rotated wallet or a hijacked door is not something two observations can say; a buyer holding the address recomputes the digest and matches.
- x402-mcp.onrender.com changed where it asks to be paid: 1 address digest last week, 1 address digest this week, 0 in common. Whether that is a rotated wallet or a hijacked door is not something two observations can say; a buyer holding the address recomputes the digest and matches.
- api.certaindata.ai changed where it asks to be paid: 1 address digest last week, 1 address digest this week, 0 in common. Whether that is a rotated wallet or a hijacked door is not something two observations can say; a buyer holding the address recomputes the digest and matches.
- api.melvea.com changed where it asks to be paid: 1 address digest last week, 1 address digest this week, 0 in common. Whether that is a rotated wallet or a hijacked door is not something two observations can say; a buyer holding the address recomputes the digest and matches.
- api.invoket.com changed where it asks to be paid: 2 address digests last week, 1 address digest this week, 1 in common. Whether that is a rotated wallet or a hijacked door is not something two observations can say; a buyer holding the address recomputes the digest and matches.
- api.hergertsynthora.com changed where it asks to be paid: 1 address digest last week, 1 address digest this week, 0 in common. Whether that is a rotated wallet or a hijacked door is not something two observations can say; a buyer holding the address recomputes the digest and matches.
- api.magentlab.com changed where it asks to be paid: 1 address digest last week, 1 address digest this week, 0 in common. Whether that is a rotated wallet or a hijacked door is not something two observations can say; a buyer holding the address recomputes the digest and matches.
- llm-smart.hergertsynthora.com changed where it asks to be paid: 1 address digest last week, 1 address digest this week, 0 in common. Whether that is a rotated wallet or a hijacked door is not something two observations can say; a buyer holding the address recomputes the digest and matches.
- llm-fast.hergertsynthora.com changed where it asks to be paid: 1 address digest last week, 1 address digest this week, 0 in common. Whether that is a rotated wallet or a hijacked door is not something two observations can say; a buyer holding the address recomputes the digest and matches.
- payto-preflight.hergertsynthora.com changed where it asks to be paid: 1 address digest last week, 1 address digest this week, 0 in common. Whether that is a rotated wallet or a hijacked door is not something two observations can say; a buyer holding the address recomputes the digest and matches.
- yahoo-equity-delayed-quote.hergertsynthora.com changed where it asks to be paid: 1 address digest last week, 1 address digest this week, 0 in common. Whether that is a rotated wallet or a hijacked door is not something two observations can say; a buyer holding the address recomputes the digest and matches.
- coingecko-crypto-price-history.hergertsynthora.com changed where it asks to be paid: 1 address digest last week, 1 address digest this week, 0 in common. Whether that is a rotated wallet or a hijacked door is not something two observations can say; a buyer holding the address recomputes the digest and matches.
- usgs-realtime-streamflow.hergertsynthora.com changed where it asks to be paid: 1 address digest last week, 1 address digest this week, 0 in common. Whether that is a rotated wallet or a hijacked door is not something two observations can say; a buyer holding the address recomputes the digest and matches.
- sanctions-screen.hergertsynthora.com changed where it asks to be paid: 1 address digest last week, 1 address digest this week, 0 in common. Whether that is a rotated wallet or a hijacked door is not something two observations can say; a buyer holding the address recomputes the digest and matches.
- commodity-macro.hergertsynthora.com changed where it asks to be paid: 1 address digest last week, 1 address digest this week, 0 in common. Whether that is a rotated wallet or a hijacked door is not something two observations can say; a buyer holding the address recomputes the digest and matches.
- inference.hergertsynthora.com changed where it asks to be paid: 1 address digest last week, 1 address digest this week, 0 in common. Whether that is a rotated wallet or a hijacked door is not something two observations can say; a buyer holding the address recomputes the digest and matches.
- api.hyperextend.xyz now fails amount-atomic.
- tick.hugen.tokyo now fails solana-rail-receivable.
- api.anchor-x402.com now fails bazaar-extension.
- api.anchor-x402.com no longer fails status-402.
- www.getbags.app now fails network-mainnet.
- agent402.tools now fails payto-payable.
- voidfeed.ai now fails solana-rail-receivable.
- conc-exe.xyz now fails payment-required-header.
- gridpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- store.agentexchange.work now fails solana-rail-receivable.
- sandbox.node4all.com now fails network-mainnet.
- wallets-demo-seller-server.calebgcarithers.workers.dev now fails network-mainnet.
- pro-api.coinmarketcap.com now fails transfer-method-signable.
- racingpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- agent-arcade.use.x402atlas.com now fails status-402.
- onchainpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- coil.trade now fails payto-payable.
- x402-mcp.onrender.com now fails payto-payable.
- gate402.app now fails solana-rail-receivable.
- stablecoinpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- macropulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- tollbooth-hello-testnet.sjwilliams8.workers.dev now fails network-mainnet.
- chain-analyzer.com now fails solana-rail-receivable.
- citepulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- arbipulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- pulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- waterpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- api.nansen.ai now fails transfer-method-signable.
- mysticapi.com now fails solana-rail-receivable.
- x402-stablecoin-data-demo.ryan-ee4.workers.dev now fails network-mainnet.
- clinicalintelpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- api.babyblueviper.com now fails payto-payable.
- api.oblique.markets no longer fails status-402.
- filingspulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- app.heinrichstech.com now fails amount-atomic, payto-payable.
- tradepulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- autopulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- www.x402financialdata.com now fails solana-rail-receivable.
- careerpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- prospectpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- cryptopulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- taxpulse.theaslangroupllc.com now fails payto-payable.
- geopoliticalpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- compliancepulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- policypulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- shopperpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- shopperpulse.theaslangroupllc.com no longer fails status-402.
- wealthpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- cyberpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- alphapulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- harvestpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- marketpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- gamepulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- diet.agentic-jp.com now fails solana-rail-receivable.
- houjin.agentic-jp.com now fails solana-rail-receivable.
- api.biotechcatalystsentinel.com now fails solana-rail-receivable.
- transit.agentic-jp.com now fails solana-rail-receivable.
- climatepulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- venturepulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- truthpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- talentpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- tablepulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- scholarpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- scentpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- proppulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- parentpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- mindpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- longevitypulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- legalpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- grantpulse.theaslangroupllc.com now fails payto-payable.
- govspendpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- glowpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- footballpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- fieldpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- esgpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- edupulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- econsignalpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- debtpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- weather.agentic-jp.com now fails solana-rail-receivable.
- airdroppulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- travelpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- immigrationpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- fitpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- wallets-demo-seller-server.agent-payments-testing.workers.dev now fails network-mainnet.
- rest.staging.wagmi.productions now fails network-mainnet.
- x402-stock-indicators.vercel.app now fails solana-rail-receivable.
- payanagent.com no longer fails payment-required-header.
- api.eucompliance.tools now fails solana-rail-receivable.
- twitr.sh now fails solana-rail-receivable.
- riskpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- api.invoket.com no longer fails bazaar-extension.
- x402.aispace.bot now fails status-402.
- giftpulse.theaslangroupllc.com now fails amount-atomic, payto-payable.
- api.jpverify.com no longer fails status-402.
- agent-commerce-factory-jm.austriaeast.cloudapp.azure.com no longer fails status-402.
- animica.dev now fails payto-payable.
- api.you.com now fails solana-rail-receivable.
- whaletape.xyz no longer fails status-402.
- 10x402.com no longer fails status-402.
- api-staging.eckari.com now fails network-mainnet.
- zeroclick.affiliate.com no longer fails status-402.
- x402.freeq.one no longer fails status-402.
- energy.halowerk.com now fails status-402.
- tiktok.palmyr.ai now fails status-402.
- www.hoodgrow.com now fails status-402.
- x402-agent-store.rileycraig14.workers.dev now fails solana-rail-receivable.
- agent-economy-sec-verifier.onrender.com no longer fails status-402.
- pf-x402-api-testnet.ahndohun1.workers.dev now fails network-mainnet.
- agent-fact-receipts-staging.131313122.workers.dev now fails network-mainnet.
- error404.life no longer fails payment-required-header.
- api.tickersfeed.net no longer fails status-402.
- api2ls.com now fails solana-rail-receivable.
- secondopinionx402.com now fails payto-payable.
- tollbooth-fdic-verify-testnet.sjwilliams8.workers.dev now fails network-mainnet.
- api-staging.you.com now fails network-mainnet.
- api-staging.you.com no longer fails status-402.
- gateway.spraay.app now fails status-402.
- x402.yodeler.xyz now fails solana-rail-receivable.

### Hosts in week

1089

### Hosts in previous

972

### Hosts in both

884

### How to rederive

Fetch https://scvd.store/corpus/4.json and https://scvd.store/corpus/5.json, compare the rounds' rows yourself, and check both digests against the chain.

## Sources

### Live

6

### Partial

0

### Stale

0

### Never answered

1

### Unread

4

### Not answering

- x402scan.com

## Weeks missing

none

## Corrections this week

### 2026-09-06

#### What was wrong

The correction dated 2026-09-05, describing the machinery built after two operators corrected two of this desk's notes in one afternoon, said of the re-read: 'one press knocks again on every door a note went to and lays the current instrument's reading beside the row the note was drafted from.' It did not lay it beside that row. It laid it beside whatever row the LATEST weekly census held for that host, which is the same row only until the next census runs and then is a different fact entirely — after a walk, the comparison was this week's census against a live probe, a staleness check on the census rather than a check on the note. Worse, the disagreement rule compared one bit: ready against not-ready. A note that named `payto-payable` at a door now failing `amount-atomic` read AGREE, because both readings are not-ready — so the exact failure mode the re-read was built to catch, a note whose named finding no longer holds, was the one it was blind to. Both flaws shipped in the same commit as the sentence describing them, and the page repeated the sentence on the keeper's own screen.

#### How long

One day, 2026-09-05 to 2026-09-06, in the ledger entry, in the section heading and prose on /admin/outreach, and in the code itself. No wrong note was sent because of it; what it cost is a day in which the desk's own audit could have called a wrong note quiet and nobody would have known. The re-read had been pressed by hand a small number of times in that window, all against the census round that produced the notes, where the two comparisons happen to coincide.

#### Found by

The keeper, asking where the press was and then what happens when it disagrees — which made the desk read its own comparison aloud and find that it did not do what its own correction said. Not found by any test: the specs asserted the rule as written, and a test that pins the wrong rule passes forever.

#### What changed

The claim a note makes is now frozen on the ledger the moment the note goes out (OutreachEntry.claimed — the reading it was drafted from, its week, and the rails the door offered then), by the wire at send and by the stamp routes for hand delivery, and it is never overwritten. The re-read is held against THAT, and a note stamped before the field existed says on its own row that it is falling back to the census. The comparison is on the checks the note named, not on the readiness bit. The call is three ways: `agree`; `ours`, DERIVED from the retraction ledger when every check the note named has since been retracted, which needs no judgement and drafts the correction email itself; and `look`, everything else, which stays the keeper's because healed-since and ours are the same shape from outside a door. And it no longer waits for a press: auditSweep rides the half-hourly tick, five doors a pass, each door at most once a day, and pages the keeper with the drafted correction attached. It still sends nothing — rule 30 does not relax because a cron is in front of it. test/outreach-audit.spec.ts pins all three calls, the daily floor, and the drafted correction; test/outreach-desk-hygiene.spec.ts pins the freezing.

### 2026-09-06

#### What was wrong

Checkout gained Arbitrum and World, but secondary copy still described Base alone or Base, Polygon and Solana. The browser wallet indicator omitted the new EVM networks and its signature advice assumed one USDC domain name. The practice counter also called half a cent the cheapest price beside a cheaper shelf; the standards and dependency pages retained obsolete settlement-order claims.

#### How long

The remaining network-copy gaps were confirmed on 2026-09-06 after activation. The price and settlement-order wording predated this check; their exact introduction dates were not established. The payment offers and certificate signatures were not changed by this correction.

#### Found by

The keeper reported a successful browser-till purchase, cert_et6zuesrrn, and pasted the surrounding practice-counter copy. A repository and live-response sweep found the same drift in receipt identity, discovery descriptions and dependency disclosures.

#### What changed

Browser network hints now derive from enabled checkout configuration, and signature advice compares with the selected quote. Static checkout descriptions point to current quotes; statement copy refers to its own network input contract. README, practice-counter pricing, receipt identity, discovery descriptions, trust, stack, standards and skill bundles were corrected together. The reported browser test and its limits are recorded in docs/BROWSER_CHECKOUT_2026-09-06.md; secondary-payment-copy.spec.ts checks the connected surfaces.

### 2026-09-05

#### What was wrong

After the rail double-count was reversed, the storefront's ledger line read '2 from before we logged the rail' — two organic settles the books held with no chain against them. They were not new and they were not unknowable: two settles counted at the till between the Solana door opening (2026-08-04) and the till learning to write rails down (2026-08-07T21:16Z), with no certificate to carry a rail, exactly the closed set /stats had described since August. The reversal did not create them; it stopped two double-counted Solana entries from silently standing in for them. The store's own rule for that set was a chain read against the transaction hash, and nobody had done the read.

#### How long

The two settles have been unplaced in the books since 2026-08-07. The line was visible on the storefront for about an hour on 2026-09-05, between the rail-seam press and this placement; before that the double count hid it.

#### Found by

The keeper, reading the front of the store and refusing the wording for the second time: 'we have already been through this.' The first time (2026-08-13) the unplaced sale was a July penny page, placed by the fact that Base was the only door then. This time both doors were open, so only the chain could place them.

#### What changed

The read was done. Every USDC transfer into the Base receiving wallet from 2026-08-01 to the rail meter's first tick was listed from the chain and matched against the certificate drawer. Exactly three outside payments in the window carry no certificate, all from one wallet, 0x42b3…029f, inside one minute on 2026-08-07: two of $0.005 (small_blessing's price, an item that mints a certificate — so two deliveries died after the money moved, the failure rule 9's settle-last ordering later closed) and one of $0.01 (a penny page's price, which mints none by design). The till counted two settles there; the books cannot say which two, and do not pretend to. Both placements are entered in RAILS_ENTERED_BY_HAND on Base with their transaction hashes as the evidence — the second entry cites both candidate hashes and says so — and the shape now allows exactly that: an entry is one placed sale carrying the hash or hashes that prove its chain, never a bare count. The storefront reads 25 on Base, 3 on Solana, and the remainder is zero. Not read: the Solana receiving wallet over the same window, because this session's network could not reach a Solana RPC; a certificate-less Solana payment in that window would mean one of these two placements is wrong, and the net statement's Solana inflow line is where it would show.

### 2026-09-05

#### What was wrong

The storefront, /stats and /rails read 5 organic sales settled on Solana and 0 from before the till logged the rail, when the books hold 3 on Solana and 2 unplaced. The same afternoon's repair, which books a settle the till never ran from its certificate, rebooked two Solana settles from 2026-08-05 and bumped the till's August Solana rail counter for both — but both certificates predate the rail-meter seam, so the certificate walk had already placed them. Two sales, four Solana entries. The organic total (28) was right throughout: the paid counter is the only organic count and it took each settle once. The rail split was wrong, and the identity check that guards it (base + solana + unplaced = organic) never fired, because two rail-less penny settles from the same August window were silently absorbing the surplus.

#### How long

From the press of POST /admin/repair/payer-settles on 2026-09-05, around 15:00 UTC, until the rail-seam repair is pressed after this ships — the front of the store keeps reading 5 on Solana until that press. Every surface that prints the rail split: the storefront's ledger line, /stats, /rails, the skill's track-record sentence.

#### Found by

The keeper, reading the front of the store against his own ledger: 28 organic with 5 on Solana on the page, 2 organic settles on the day in the office, and no idea where three Solana sales had come from. Not found by the books sweep, whose rail identity held by arithmetic accident.

#### What changed

The rebook stops at the seam: rebookSettleFromCertificate bumps the till's rail COUNT only for a certificate dated at or after KV_KEYS.railMeterStart, where the till is the rail record; before it, the walk is, and the repair reports the rail as left to the certificates (rail_left_to_certificates on the response). The money per rail is booked either way, since the net statement reads booked revenue against chain inflow and the walk carries no money. The two bumps already on the books are reversed by POST /admin/repair/rail-seam, which takes the transactions from the repair's own counters_rebooked list and checks each against the certificate on the shelf before moving a counter — a payer, a rail, a date before the seam, a settle record the backfill wrote — and writes a marker per transaction so a second press is a no-op. test/reconciliation.spec.ts holds both: a pre-seam rebook books the settle and not the rail, and the reversal moves one counter once and refuses a till-booked settle, a post-seam certificate, and a transaction no certificate names.

### 2026-09-05

#### What was wrong

The service-window check on /api/verify, shipped 2026-08-24 as 'layer 3' and described as closing the stolen-retired-key gap, answered `in_service` on the strength of the date the artifact carries — and that date is the one field a holder of a stolen retired key chooses. A receipt minted today, dated inside a retired key's window, citing a real settlement from that window and signed with that key, read `in_service` with prose that placed it inside the window as if the placement had been checked. The check caught the careless forgery (dated after retirement) and passed the careful one. The store's key log, which the /attestation page offered as the Bitcoin-anchored half of the answer, bounds when a handover was ANNOUNCED and says nothing about when any artifact the retired key signed came to exist; the settlement transaction inside each receipt gives a not-before and nothing gave a not-after.

#### How long

From 2026-08-24, when the window check shipped with that description, to 2026-09-05: twelve days on every certificate verify response, and on the /attestation page's framing of the key log for the whole time it has been anchored.

#### Found by

navigatorbuilds, an outside reader on the x402 settlement-attestation-receipt thread (coinbase/x402 PR 46), replying to CV's description of the anchor log: the log's existed-by bounds the announcement, not the artifact, so 'a key that appears having already issued artifacts is a compromise' is only decidable if the artifact's own existence is bounded, and the honest verdict without that is 'signed by a key that was once current'. Not found by any test here: test/key-window.spec.ts forged the shape the check catches and never the shape it does not.

#### What changed

Every certificate's signed bytes are now digested and submitted to OpenTimestamps by the hourly sweep (services/certificate-anchors.ts), upgraded to a Bitcoin attestation, and the block height is read off the completed proof. /api/verify serves it as `existence`, with the digest compared against artifact_hash on the same response and a five-state verdict that never collapses: a bound on or before the key's retirement is 'signed while the key was current'; a bound after it is 'issue time unproven' — the shape of every receipt anchored on backfill AND of a stolen retired key, which the artifact alone cannot tell apart, and the verdict says so instead of guessing; no bound yet is 'unproven', never a pass. The artifact's own date is not an input to that verdict. Receipts minted before 2026-09-05 were anchored on backfill and carry the weaker verdict permanently. The /attestation page's line on chains now says what the per-receipt bound does and does not add. test/certificate-anchors.spec.ts holds the walk, the proof parse, the block lookup, and the verdict on each key state, including the careful forgery.

### 2026-09-05

#### What was wrong

The passport chip — the one artifact this store asks operators to paste into their README — drew its own text on top of itself. Two runs shared the top baseline with no width budget between them, so on any host with a tier the label ran through the freshness and date: `SCVD PASSPORT · INDETERMINATE` overprinted `FRESH • 2026-09-01`, illegibly, and the two words a reader could pick out of the wreck contradicted each other. On the line below, the hostname ran through a verify URL printed at the right edge. The share card that a pasted passport link unfurls into had the matching problem of kind rather than of overlap: a 5x7 hand set enormous on a blank field, which reads as a terminal dump rather than as a document. The keeper, looking at a live chip: "why would anyone post this on their readme."

#### How long

The chip has rendered at /badges/passport/{host}.svg since 2026-08-21 and gained the tier on its face on 2026-09-02; from that date any host with a tier — which is every census-observed host — drew the overlap. Three days, on every chip anyone had pasted, plus the passport page's own To Share block. The share card has looked as it did since 2026-09-02. No verdict was wrong: this is a defect in what we published, not in what we observed, and it is in this ledger because the ledger is where things this store put in front of people that were not fit to be there get dated.

#### Found by

The keeper, opening a live chip for bykaranteli.com and the share card on the same passport page.

#### What changed

SVG text does not wrap and a Worker cannot measure a glyph, so every label in badge-svg.ts had been placed at hand-picked coordinates and hoped. A character count could not have caught it either — the old fit was host.slice(0, 34), and WWW.EXAMPLE.COM is nowhere near the width of illinois.io. So there is now a width estimate by glyph class (textWidth) that errs WIDE on purpose, a fitter that truncates to a stated budget (fitToWidth), and the chip's geometry lives in CHIP_LAYOUT with every budget DERIVED from it rather than typed twice. test/chip-geometry.spec.ts walks every drawn run against its budget for the inputs that actually break a layout — the longest registrable hostname, the widest possible caps, every freshness word, every tier — so an edit that moves the seal without moving the budget fails in the suite instead of on somebody's front page. The chip was then redrawn as a letterpress label: one hairline frame with squared corners, a struck seal, tracked small caps over the host over one record line, and printer's inks rather than a dashboard's greens. The tier's word no longer rides on the face when it is `indeterminate` — that is a statement about how many rounds we hold, not about the door, and it had been the loudest thing on a chip whose own decision was READY. The share card was rebuilt on a coverage buffer with a 6x9 engraved alphabet, proportional metrics, and a certificate's frame, rules and seal; it encodes as a sixteen-step indexed PNG so the type is inked rather than tiled. A third pass then gave the chip a SPINE inked in the freshness colour — a cream label is quiet on a light page and invisible in a row of shields, and the chip now carries its own contrast onto any background while an expired reading goes visibly dead rather than announcing it in six-point type. A long hostname is no longer cut: fitHost walks a size ramp and sets the whole name smaller, mutes everything before the registrable domain so the eye lands on the name a reader knows, and only past the ramp cuts — from the FRONT, where the subdomains are. The seal is struck at a small angle derived from the hostname, so a chip renders identically every time and neighbouring hosts never sit at the same angle. A fourth pass, on the keeper's read that the result was still "second tier of five", made it a CARD at 400x110 rather than a 300px strip — the store's own copy calls it a colophon to paste beside your door, and a colophon is not a shield — and gave it the one visual language the artifact's own name implies: an engraved ground under the type, a seal with its legend set around the top arc, and the freshness STRUCK across the corner as an entry stamp carrying the observation date. The aspect changed with it, which an already-pasted embed cannot follow; every generator here emits the new dimensions from CHIP_LAYOUT rather than repeating them, and the keeper's desk carries the note. A contrast audit of that pass then found the design had walked into a WCAG failure while nobody was measuring: the secondary tone, #8a7b64, sat at 3.69:1 against the paper and was carrying BOTH small runs — the eyebrow and the record line — on an artifact we ask other people to embed, where their own accessibility audit would have failed them for our defect. It is #6f6250 now, at 5.31:1; the expired stamp's date was at 4.36:1 purely because it was set at 0.9 opacity, so no run of text on the chip carries a fill-opacity at all any more; the two runs a reader is meant to read went from 7px and 8px to 8px and 9.5px; and the seal's ornament is a drawn path rather than a ◆ set in a font, which some platforms give an emoji face. test/chip-contrast.spec.ts walks every ink against the paper at 4.5:1 and fails the build under it, because contrast is arithmetic and arithmetic belongs in a test rather than in a review note. A fifth pass answered the last of the keeper's read — "I don't like the off white paper texture, I want premium... I see it on the page and I don't click, I scroll right past" — by naming the fault, which is not a taste one: a pale label sits at the same VALUE as the README around it, and equal value is exactly what an eye skips. The ground is now the forest-black the store's own favicon badge is cut from, under a gradient, with a lit rim and a shadowed one for the bevel; the frame and the seal are struck in foil; the eyebrow, the host and the stamp's date are set bold; and the seal holds the STORE'S DINOSAUR rather than the letters SCVD, drawn from the same path data the favicon draws, since a mark kept in two files is a mark that drifts. The share card follows onto the same dark ground with the same mark, which needed a scanline polygon filler and a path flattener in a renderer that until then knew only rectangles. Every ink was re-checked against the lit end of the new gradient before it shipped.

### 2026-09-05

#### What was wrong

Two notes went out by hand on 2026-09-05 and both operators wrote back the same afternoon with a fact of ours that did not hold. To 402signal.com: "got a response that no x402 buyer can pay: payto-payable" — drafted from the week's stored row, a payTo on an Algorand rail misread as unpayable by the instrument this store had corrected the day BEFORE (the 2026-09-04 entry below). The operator ran our free preflight and got ready on both batteries, three payable accepts. And "no x402 buyer can pay" is not what one failed check on one of three rails means even when the check is right. To tensorfeed.ai, a welcome: "On 2026-09-05 our weekly pass ... fetched" a door whose passport, linked in the same note, said observed 2026-09-01. Both notes dated the observation to the day the round was sealed, not the moment the row was read — the walk knocks in hourly batches across the week and Sunday only assembles, and no row carried its own time.

#### How long

The wire has re-probed every door live at press time since 2026-08-20 (rule 30's condition), so a note it sent was never a stored reading. The wire has been paused since 2026-08-26, and hand delivery — copying the card's draft, then the mailto: link of 2026-09-04 and the Gmail link of 2026-09-05 — drafted from the stored row for as long as the desk has existed. The seal-time date is older: every note and every welcome since the desk opened on 2026-08-19 carried the round's `at`, and every passport carried the corpus snapshot's `taken_at`, and neither was the knock. Two hosts are known to have received a note that was wrong in one of these ways; the outreach ledger holds which others were hand-delivered from rows of round 2026-W36.

#### Found by

Ross McIntyre of 402Signal, replying with the live preflight verdict, the live challenge, and the passport's stale state side by side; and TensorFeed.ai's operator, replying that the note's date and the passport's should be the same date "for a shop whose whole pitch is dated observations".

#### What changed

Three mechanisms. (1) The hand road walks the wire's law: a broken-door card has no note until the keeper presses verify live — one probe by the instrument as deployed at that moment (verifyProspect); a door that answers ready is stamped fixed and gets no note; a door that still reads broken has its reading written on the ledger, dated, with the battery that spoke, and handDraftFor drafts from that and nothing else. The Gmail and mail-app links render only while a reading under LIVE_READING_FRESH_HOURS old exists; past it the button is back. A batch button verifies the next ten and sends nothing. (2) The probe stamps every row with the moment it knocked (WardHostResult.observed_at, on the answered and the unanswered branch alike); the queue, the welcome, the subject history and the fresh set date a row by that stamp and fall back to the seal only for rows walked before it existed — so the note, the corpus row, the fresh set and the passport now carry one date by derivation, not by agreement. (The fresh set's own comment had said "per-row where the row knows it" for two weeks while reading the seal.) (3) The note's finding says what the check saw — "got an answer that did not pass our readiness check. What failed, by name: …" with the check definitions linked — and its subject names a failed check; "turning buyers away" is kept for doors that gave no answer at all. The re-check line carries the re-check's own timestamp. test/outreach-verify.spec.ts, test/outreach.spec.ts, test/ward-round-evidence.spec.ts, test/subject-history.spec.ts and test/fresh-set.spec.ts hold all three. Two more mechanisms exist because the keeper asked how the desk finds the NEXT wrong note before its operator does. THE RE-READ: one press knocks again on every door a note went to (auditSentNotes, ten a press, oldest first, sends nothing) and lays the current instrument's reading beside the row the note was drafted from; a disagreement is named at the top of the desk and never resolved by arithmetic, because 'healed since' and 'ours' look identical from here and only the keeper can tell them apart. AND THE STRUCTURAL GUARD (rule 46): test/one-date-per-observation.spec.ts asserts that neither the outreach page nor its routes can reach the raw drafter at all — the only road to a note runs through the live-reading gate — and that the note and the passport it links derive their date from the same field, so a surface that grows its own clock again fails in the suite rather than in somebody's inbox.

### 2026-09-05

#### What was wrong

The correction dated 2026-09-04, one line below this one, said that an EIP-3009 authorization nonce is a value 'no node will ever answer' — and 0200project, reasonably, drew the consequence in public: any ledger row keyed on the nonce can never be verified against the chain by anyone. Both were too strong. As a TRANSACTION identifier the nonce is unaddressable and the null lookups stand. But a nonce is indexed on chain: the settlement emits AuthorizationUsed(authorizer, nonce) on the USDC contract with the nonce as an indexed topic, and eth_getLogs on that topic answers it with the settlement transaction. Run on 2026-09-05, that lookup recovered settlement hashes for six of the seven rows this store had published, one day earlier, as unrecoverable. Each receipt has status 0x1, was mined within two seconds of observed_at, and carries one USDC transfer from the declared house wallet to the row's payTo for exactly amount_usd. The seventh — row 1, the very settlement we handed the other instrument for the cross-check — has no AuthorizationUsed on any contract in ±25 hours and no transfer into its payTo at all: on Base mainnet its $0.10 did not move. Its 'settled' was the door's word.

#### How long

The overstatement stood one day, 2026-09-04 to 2026-09-05, in the ledger's basis fields, its README, and two public comments on issue #188. The six unrecorded settlement hashes had been recoverable from public chain data since the moment each settled on 2026-09-02; nothing about them was ever lost, only unlooked-for. Row 1's unconfirmed settlement has stood since 2026-09-02 and stands still, stated now.

#### Found by

The keeper, reading 0200project's reply and calling its consequence 'a little extreme' — which sent us to check the consequence before agreeing with it, and the check found the lookup that both instruments had missed. Not found by any test: the guard shipped on 2026-09-04 held the schema, and the schema was right; what was wrong was a sentence about what the chain could do, and a sentence is what a schema guard cannot see.

#### What changed

Rows 2–7 carry settlement_tx_hash with a settlement_tx_hash_basis naming the RPC, the event, the block, the mined time against observed_at, and the transfer matched to payTo and amount. Row 1 carries settlement_confirmation: not_found_on_base_mainnet, a basis naming both negative searches and the chains not searched, and terminal_state_basis saying plainly that 'settled' is the door's report. scripts/walk-ledger-verify.mjs now reads every row two ways — as a transaction and as an authorization — and exits non-zero when a settlement hash did not spend the row's nonce, or when the chain shows a nonce spent that the row carries no settlement for: the chain knowing more than the row now fails the build, not a comment on a thread; test/walk-ledger-identifiers.spec.ts still holds the schema beside it. The README retracts the sentence by name.

### 2026-09-04

#### What was wrong

cert_a7qcdbh98v and cert_6fbvtpdwgu, a pair this store signed and sold on 2026-09-04, attest to nothing: their `attests` field is the sha256 of the empty string, a signed attestation over zero observations. Both signatures are genuine, and /api/verify answered valid: true for both, correctly and unhelpfully. WHY THEY EXISTED, since the entry beside this one says what the defect was: the store's two doors had grown apart. The HTTP door ran twenty-three pre-payment checks and mapped every query parameter into the till; the MCP door read a handful of arguments by name and dropped every other one its own published schema advertised. So the buyer sent two transaction hashes for a sheaf, the tool's schema accepted them, the till received none, observed nothing, hashed the empty sheaf, settled the $0.05, and signed. The buyer's money was real; the artifacts were void. Under house rule 56 both are withdrawn as evidence.

#### How long

Minted 2026-09-04, both inside one afternoon, on the deployed store while the fix sat unmerged on a branch. They stay on the wall as the record; they are withdrawn as evidence, and /api/verify says so on each.

#### Found by

CV, an outside agent testing the store on 2026-09-04, who bought the same sheaf twice, once over MCP and once over HTTP, and compared the two artifacts: the HTTP twin carried a real content hash and both settlements; the MCP one attested to the empty string, recognisable on sight.

#### What changed

The till refuses a sheaf of zero hashes before settlement, whatever door it came through, so no future door can buy a signature over nothing (test/round-two-integrity.spec.ts). /api/verify says, beside valid: true, when an attestation is the hash of the empty string, with the digest derived rather than typed, so an automated check no longer passes a void artifact in silence. And a knock never made is no longer signed as "unreachable": a target that is not a URL is a refused target on every probing door, and the deliverable says we did not knock.

### 2026-09-04

#### What was wrong

The x402 walk ledger carried one key, `authorization_or_tx_id`, whose own documentation read "the authorization nonce or settlement tx". Nothing in a row said which of the two a value was, and the two are opposite in what they permit: an EIP-3009 nonce is client-generated random bytes no node will ever answer to, a settlement hash is addressable by anyone with an RPC endpoint. Same shape on the page. On 2026-09-03 the store then published row 1's value into a public cross-check on issue #188 as "Transaction: 0x3e366c96…f794090 on Base mainnet" — a sentence the ledger's own schema never supported. It is the authorization nonce; `buildAuthorization` in scripts/lib/walkabout.mjs mints it as 0x + randomBytes(32) before the payment is signed, and the walker keeps the settlement hash in a separate field it reads off the PAYMENT-RESPONSE receipt. The ledger collapsed two distinct captured fields into one key and prose resolved the ambiguity in the wrong direction, in public, in the exact artifact whose selling point is that a reader can check it. The class was already ours: `nonce-unbound-from-settlement` has been in this store's public defect vocabulary since 2026-08-27 — marks the nonce spent without naming what spent it, sourced by SolomonisBlack — with the repair hint 'store the settlement transaction hash beside the nonce'. We wrote it, aimed it at other people's tills, and failed it on our own record.

#### How long

The union key from the ledger's publication on 2026-09-02 to 2026-09-04, across all seven rows. The mislabel built on it was live for one day, 2026-09-03 to 2026-09-04, on a public issue thread, and was the first thing an outside instrument tried to use.

#### Found by

0200project (base-tx-explain), from outside, inside 24 hours of being handed the identifier — in the cross-check this store proposed, doing exactly what a cross-check is for. They ran eth_getTransactionByHash and eth_getTransactionReceipt on Base mainnet and Base Sepolia, got null from all four, and ran a control hash from the head block through the same endpoint to prove the null was about our identifier and not their reach. Then asked whether it was a transaction hash at all rather than asserting it was not. No test here could have caught it: every guard on that ledger checked that fields were present, none asked whether a field's name could be read.

#### What changed

The rows carry `authorization_nonce`, `settlement_tx_hash` (null on all seven, so the absence is in the bytes instead of behind a union) and `identifier_kind` + `identifier_kind_basis`, which names the kind and what it rests on. Shape decides nothing — the two kinds are the same 32 bytes — so the basis is a chain read: both lookups returned null for all seven values on Base mainnet at head block 50879438 on 2026-09-04, with a control hash from that block resolving through the same endpoint, replicating the read 0200project made independently and first. It names its falsifier too: any node, on any chain, answering one of these values. scripts/walk-ledger-verify.mjs (npm run walk-ledger:verify) is that read, kept — it refuses to claim anything if its control does not resolve, and exits non-zero on a nonce that resolves or a settlement hash that does not. test/walk-ledger-identifiers.spec.ts fails the build if any row reintroduces a union identifier key, drops the kind or its basis, omits settlement_tx_hash, publishes one value as both, or names a settlement hash without a settlement_tx_hash_basis carrying a dated read; it was run red against the pre-fix ledger first and reproduced all four failures. The ledger README states the hole in the verify-it-yourself section rather than leaving a reader to hit it, and records the correction with the outside instrument named.

### 2026-09-04

#### What was wrong

The weekly walk published not_ready verdicts against doors that were payable, because two of its checks read every chain as if it were Ethereum or Solana. payto-payable resolved any unrecognised CAIP-2 namespace to the EVM branch: an XRPL classic address is base58 in a band that sits inside the Solana window, so a correct XRPL payTo was reported as "a base58 Solana address ... no buyer on this rail can pay this offer", and Stellar and Algorand addresses, being base32, matched nothing and were reported as neither an address nor a name service. amount-atomic applied the USDC atomic-units rule to XRPL issued currencies, which the ledger itself denominates in decimals, and told those doors that "0.01" underprices by a factor of a million. In round 2026-W36, 63 of 1,089 hosts walked failed payto-payable and 56 failed amount-atomic; every one of those 56 also offered a chain the desk could not read. The verdicts were signed and published against named hosts.

#### How long

One published round. The three checks were promoted from advisories into the v2 verdict on 2026-08-30. Round 2026-W35, walked 2026-08-24, carried zero such failures; round 2026-W36, walked 2026-09-01, carried 65, of which 61 hosts had read ready the week before. Before the promotion the same misreads existed but rode as advisories, visible and not verdict-changing. For the week the verdicts stood, the affected hosts’ passport pages showed not_ready and their README chips refused to render, since the chip publishes names only on the ready side. Round W36 stays in the chain as walked; the corrected instrument publishes fresh rows on the next walk beside it.

#### Found by

The keeper asked how to double-check an operator who had replied "I forsure know mine works". Running our own preflight against his door returned 7 of 8 checks passing and one failure, and the failure was ours: his XRPL address read as a Solana one. Reading the round for the same signature found 63 hosts, 3 of them on our own outreach list — we had written to operators about doors our instrument had misjudged.

#### What changed

familyOf now names xrpl, stellar and algorand and returns "unknown" instead of defaulting to evm, and readPayTo gained a fourth verdict kind, unknown-network, whose payable is null: not judged, never failed. l3bChecks threads that null through, keeps unjudged entries out of the verdict, and prints them beside the pass so the reading names what it did not judge. amount-atomic now judges amounts only on the rails this store settles on and has tested, EVM and Solana, and names every other rail's amount beside the pass rather than ruling on it — a first draft exempted only XRPL issued currencies and kept judging Stellar and Algorand on the same assumption that had just been wrong, and the rule-52 guard below caught it before it shipped. transfer-method-signable no longer calls a non-EVM method unbuildable, since the methods it knows are EVM signature standards. Rule 52 already forbade all of this; its enforcement walked only KV reads, so test/bounded-read-honesty.spec.ts now also walks the readers that judge strangers, asserting that no unrecognised chain can ever produce a "no". test/value-checks.spec.ts holds the three real doors that were misjudged, by their actual addresses, and holds a genuinely broken EVM door still failing both checks.

### 2026-09-04

#### What was wrong

The source register at /sources, and the ward page beside it, said the CDP discovery feed had never answered this store: status never_answered, roster_disagrees true, and on the keeper's page the line "Not answering: discovery." The feed had answered every one of the five rounds the register read. In W32 through W34 its paging served page one to every offset and the round kept 100 rows; in W35 and W36 it answered all sixty pages the read asked for, 6,000 rows, and declared more. The census rightly refused both as short lists, since a listing cut short cannot tell a delisting from a next page, and wrote null. The register, built the same day, had two words for a null, stale and never_answered, and neither means answered short. So a feed that had outgrown our read was published as a feed that was down, and the keeper read it as one.

#### How long

The register opened on 2026-09-04 and carried the word for part of that day. The read it described had been short for five rounds: page one only from W32, and capped at 6,000 rows of a larger listing from W35. Every round said coverage_suspect and its row count, so the shortfall was on the record the whole time; the word for it was not.

#### Found by

The keeper, pressing /admin/ward after the sweep shipped, pasted the line and asked whether everything else was done. Reading the five rounds back showed listed_resources at exactly 100 and exactly 6,000, the two shapes of a read that stopped, under a status that said nothing had ever come back.

#### What changed

The census writes WHY beside every null (per_source[].why: unreadable, capped or pagination), and the register gained a fifth status the same day, partial, for a feed that answered and whose short list the census refused; /sources and /admin/ward say it in words. The read itself no longer caps: the long walk's start firing was given a 300-page cap the same day, and past that the walk reads the feed across hourly firings on a stored cursor until the feed's own declared total is reached, so a listing of any size is read whole a few hours into the week. The walk's roster is capped at 2,000 feed doors, where the KV value that holds a week's evidence would otherwise fail near 3,900, and the round says when that binds; the census still counts every host the feed named. test/long-walk.spec.ts reads a feed larger than one pass over two firings and holds the cap announced; test/population.spec.ts holds that the reason rides beside the null and never beside an answer.

### 2026-09-04

#### What was wrong

The MCP door took a buyer's arguments, validated the arguments of a handful of items, and carried a short list of fields into fulfillment. Every other field an item needs to know what it is being asked about — `url`, `address`, `tx_hash`, `tx_hashes`, `wallet`, `digest`, `mandate` and the rest — was read off the wire and dropped before the goods were made. Three shapes came out of that one defect. good_buyer and launch_check each produced and SETTLED a signed artifact about the empty string: at $0.99 and $5.00 respectively, both on 2026-09-04: each probed "", folded the unreachable result into a signed reading exactly as they are built to do, and took the money — so the buyer holds two real, correctly signed observations about no endpoint on earth. attestation_bundle minted a certificate over an empty sheaf, settled, and then threw on its way out, leaving money moved, a certificate issued and a 500 in the buyer's hand, recoverable only via /trust if they knew to look. passport_refresh and provenance_check threw before the settle, so those cost nothing — the deliver-first rule holding — but answered a paying customer with an error page roughly half the time. The HTTP door was never affected: it had the whole map and the whole set of refusals.

#### How long

From the day the MCP buy shelves opened until 2026-09-04. No purchase over MCP of any affected item was ever correct, and the store cannot say how many there were beyond the first buyer's, because the argument that would have identified the subject is the argument that was dropped. Making the buyer whole for the two settled artifacts is the keeper's hand, not this fix's.

#### Found by

The first outside agent to shop the MCP shelf with a real wallet, reporting all three shapes with the amounts and the item ids, on the day they happened. Nothing in here found it: the store's own MCP tests bought the items whose arguments the door DID carry, and the one spec that came near it wrote the reason down — "service_audit takes its url later, so it reaches the challenge instead" — and treated that as a fact about the test rather than as the defect it was.

#### What changed

Both doors now read one argument map and one set of pre-payment refusals out of src/lib/purchase-args.ts; the MCP door's forked copies of both are deleted, so an item that grows a field gets it on both doors or on neither. test/mcp-carries-the-buyers-arguments.spec.ts derives its guard from the published input schema rather than from a list: for every item on every MCP shelf, removing a required argument must change what fulfillment is handed, and both doors must build byte-identical input from the same values. A second derived guard buys nothing and asserts that no shelf issues payment terms for a call missing a required argument. Dropping one item out of the shared map fails all of them.

### 2026-09-04

#### What was wrong

Every conversion figure on /pulse and /stats was computed against an organic ask count that subtracted only the machines that named themselves. The census had computed the other kind since July — clients that touch four or more doors inside a minute are walking the catalog whatever their user-agent says — and published them on the office wall as undeclared_walkers, a report and not a correction. So September's standing correction removed 2 rows of 7,017; August's per-door visits sat between 70 and 101 for a half-cent blessing and a $25 collaboration alike; and 48,566 all-time asks stood against 97 wallets ever opened, a ratio that held at a quarter of a percent across months whose volumes differed sevenfold. The published corrected figures were ceilings and said so, but they were far higher ceilings than the store already knew how to draw.

#### How long

From the day the standing correction shipped (2026-09-02) until today, and in spirit from the day the census first listed undeclared walkers (2026-07-26) — the rule existed, the books did not use it.

#### Found by

The keeper, asking what was upstream of a funnel row that read 77 asks and 0 sales. The answer came off the store's own public surfaces — /pulse, /observatory — and one directory's probe counter, which alone runs ninety unpaid 402 handshakes a day against these doors.

#### What changed

The walk rule moved into one module (lib/walkers.ts) that the census, the monthly reclassification walk and the funnel all import, so the three cannot disagree about who walked. The reclassification walk now moves a walker's asks out of organic as a second, separately-published half — known_machinery_by_behaviour beside known_machinery_by_user_agent — so a reader can see which part of the correction is a name a machine gave itself and which part is what it did. The funnel reports asks_walked and leaves them out of every organic figure. Payments are never reclassified by behaviour: a crawler that pays is a customer, the rule the counters have always used. Tests hold the rule in one place and the three surfaces to it.

### 2026-09-03

#### What was wrong

The organic 402 count per item on /pulse and the books could drop increments under a burst of price-checks against one door. Every other hot counter had been spread over shards on 2026-08-27; the per-item challenge counter stayed one KV key per item, KV allows one write a second per key, and a write that outlived its retries was logged and dropped. The counts were presented as counts and were, under bursts, floors of unknown depth.

#### How long

From the day the meter went in until 2026-09-03, on any door polled faster than once a second — which the uptime monitors do. How many increments were lost is not recoverable: a dropped write leaves no row.

#### Found by

Our own CI log on 2026-09-02, which printed the line the gate writes when a count is dropped, "challenge count lost: KV PUT failed: 429", during an ordinary run. Nobody outside reported a wrong number, and nobody could have: the number that was wrong was the one that was never written.

#### What changed

The per-item challenge counter now shards its writes the same way the day and channel counters do, and the ledger sums shards on read instead of assigning one key's value to the row. test/hot-counter-shards.spec.ts asserts the item counter is spread across keys and that the item row still comes back as one item with the whole count; a reader that assigned instead of summed would fail it.

### 2026-09-03

#### What was wrong

The attestation spec page said, since 2026-08-20, that the draft-vauban-x402 family covered receipt-format negotiation, a claim algebra and delegation binding, and that this store's signature_jcs "already verifies under" the RFC 8785 discipline those drafts and draft-hopley-x402-canonicalisation-jcs-v1 pin. The first was stale: the consolidated draft defers the claim algebra, the lifecycle FSM and the delegation binding to companion documents with no normative content. The second was overstated: both draft families add pre-canonicalisation rules our artifacts do not meet (integer-millisecond timestamps only, NFC strings; our artifacts carry ISO 8601 dates, the spec's own test vector included), and neither assigns any verification role to an ed25519 signature. signature_jcs verifies under the raw RFC 8785 byte primitive, not under either draft's discipline.

#### How long

2026-08-20 to 2026-09-03, on the spec page every verifier is pointed at. No artifact was affected: the signatures were and are what the page's canonical-form section says they are. What was wrong was the claim of interoperability with drafts that would reject our preimages.

#### Found by

A full read of the three drafts at their current revisions, our spec page and the signer, at the keeper's request, as the AEO plan's A10 (docs/bylines/CV_PROMPT_IETF_2026-09.md). The overstatement was in a paragraph written from a summary of the drafts, not from the drafts.

#### What changed

The paragraph is replaced by relation_to_other_x402_receipt_work on the spec page: per draft, at the revision read, what it defines, what we share, and where we are not aligned, ending with the plain statement that we have no post-quantum discipline and that the conformance desk parses neither format. jcs_dual_emit now says what signature_jcs verifies under, and what it does not. test/namespace-spec.spec.ts holds the block to naming all three drafts with a revision and a date, and holds the old sentence absent.

### 2026-09-01

#### What was wrong

The public bounty board listed five doors as open that had expired unclaimed on 2026-08-27. A bounty's stored status is written at two moments — 'open' at posting, 'paid' at claim — and nothing ever wrote 'expired', so the board and its JSON repeated the stored word while the claim door, which checks the clock, would have refused every one of them. A shopper who read /bounties on any of those five days, paid one of the doors with their own wallet and claimed, would have lost the door's price and been told the bounty had expired. The room and the JSON also carried no count, so nothing on the front could say whether there was anything to walk.

#### How long

Five days, 2026-08-27 through 2026-09-01, the whole span between the first board's expiry and its next read. No claim was attempted in that window, which is the only reason nobody was refused.

#### Found by

A read of the live board during the keeper's own question about why the board was not being found — not by a test, because the listing had no test for a record aged past its expiry.

#### What changed

The board derives each bounty's status from its expiry at read time, through the same check the claim door applies, and publishes open_count beside the list. The storefront strip reads the same figure live and says how many doors are open and what is left of the week's budget, or says the board is between postings; it never prints a count from copy. test/bounty-board.spec.ts ages a record past its expiry in KV exactly as the live ones were and fails if any face — the JSON, the room, or the claim door — disagrees with the others. Reposting bounties weekly remains the keeper's press.

### 2026-09-01

#### What was wrong

The $5 Once-Over cited preflight-v1 as its headline battery while the weekly census had applied preflight-v2 since 2026-08-24. Same GET, same bytes, different headline: a door with a dollar-typed amount (or any other v2-only fold) could buy a signed ready the same week the corpus called it not_ready. The paid report already computed the v2 score and hid it in also_under as DISAGREED — so the contradiction was visible inside the artifact and still published as ready on the face a buyer hands to a stranger. Same class as 0.14: the check existed; the flagship record did not consume it.

#### How long

From the Once-Over's listing through 2026-09-01. Every report signed before this date still cites preflight-v1 and keeps that citation forever; we do not resign old artifacts.

#### Found by

The store's own roadmap, as N1 / leftover #82, after the census citation was corrected on 2026-08-26 and the paid headline was left on the loose battery.

#### What changed

AUDIT_CRITERIA_VERSION is now PREFLIGHT_BATTERY_NEXT, the same string the census cites. The paid headline and the sample headline are the v2 set; also_under carries the frozen v1 overlap. A dated note on /criteria records the instrument change. test/battery-inside-the-bytes.spec.ts fails the build if the two producers part again, and test/service-audit.spec.ts fails the paid door on a v1-only fixture (dollar-typed amount) so deleting the fold turns a signed ready green in a test that watched it happen.

### 2026-08-31

#### What was wrong

The skill bundle published to ClawHub — the copy that gets INSTALLED into somebody else's agent — priced `service_audit` at $0.10 when it has cost $5 the whole time that document has existed, and `trust_profile` at $19 after the keeper repriced it to $21. It also described the shelf as running '$0.005 to $50' when it runs $0.001 to $300, and its frontmatter advertised entry 'from $0.004' when the cheapest door is $0.001. Two failures with different shapes and the second is the worse one. The `service_audit` price was wrong in the bundle's FIRST COMMIT: nothing ever compared it to the shelf, so it was never right. The `trust_profile` price was correct when written and went stale two days later when the keeper's 2026-08-29 repricing reached the shelf, the room and the JSON, and not the bundle. A wrong price here fails silently in the worst direction: an agent budgets a tenth of what the 402 will ask, declines the purchase it meant to make, and concludes this store is unaffordable. We would never hear about it, and we cannot edit the copy already installed.

#### How long

`service_audit`: four days, 2026-08-27 to 2026-08-31, the entire life of the document. `trust_profile`: two days, from the 2026-08-29 repricing. Neither was found by anyone using them.

#### Found by

The store's own keeper, asking for the skill to be brought current — not by a check, because no check existed. Every guard on this document asked whether a thing was NAMED: the item ids, the credentials promise, the position sentence, the key registry. Not one of them looked at a number beside a name, so the bundle was free to advertise the right door at the wrong price indefinitely, and did.

#### What changed

test/skill-prices.spec.ts, shipped 2026-08-31, reads every price the bundle quotes beside a menu item and fails the build when it disagrees with MENU_ITEMS, plus the stated shelf range and the frontmatter's entry price against the real ends of the shelf. It was written before the fix and run red against the live document first — it reproduced both errors and one the overhaul had missed. Two of its three findings that day were the READER'S fault rather than the document's: a $0.004 attributed across a list boundary to the next bullet's item, and an amount the store PAYS at your till read as the item's price. Both are now regression cases in the same file, alongside the two real errors reduced to the sentences that carried them, so a future tightening that narrows the reader past what it exists to catch fails and names what it lost.

## Population

- **Known** — 6367
- **Walked** — 1088

## Findings

### reach

#### Kind

gap

#### Headline

We knocked on 1,088 of the 6,367 hosts every directory we read named this week — 17.1%.

#### Detail

Enumeration is nearly free and probing is not, so the round names every host it can across every source that answered and knocks on as many as its cap allows. The 5,279 unknocked hosts are not dead and are not healthy: they are unmeasured, and no figure on this page is taken over them. Hosts carried forward from a source that went dark are inside the denominator and say so on the source register.

#### Derived from

- population.population_walked
- population.population_known

### payable

#### Kind

finding

#### Headline

634 of the 1,084 doors that answered served a challenge a buyer could pay — 58.5%.

#### Detail

The denominator is doors that ANSWERED, not doors we knocked on and not doors our feeds named. 4 did not answer at all, which this store attributes to the door only when its own vantage was sound; the observer-degraded count below is the ticks where it was not.

#### Derived from

- doors.payable
- doors.not_payable
- doors.unreachable

### defects

#### Kind

finding

#### Headline

The most common named defect this week was status-402 (320 doors), ahead of 9 others.

#### Detail

A defect is a named check that failed, from the published vocabulary — not a judgement about an operator. The same door can carry several. Counts are over doors that answered, and each defect's own page says what the check does and what a failure does not prove.

#### Derived from

- defects[].id
- defects[].count

### movement

#### Kind

finding

#### Headline

Against 2026-W35: 205 appeared, 88 left, 11 recovered, 102 regressed.

#### Detail

Both weeks' denominators travel with the comparison: 1,089 doors this week, 972 last, 884 in both. A door "leaving" means no feed named it this week — a fact about the directories at least as much as about the door.

#### Derived from

- changes.additions
- changes.removals
- changes.recoveries
- changes.regressions
- changes.hosts_in_both

### not-probed

#### Kind

gap

#### Headline

1 named door was never knocked on this week.

#### Detail

Ours, not theirs. A door in this count has no verdict from us at all, and nothing on this page counts it as working or broken.

#### Derived from

- our_gaps.not_probed

### coverage-suspect

#### Kind

gap

#### Headline

The round flagged its own coverage as suspect this week.

#### Detail

A feed answered with a full page and no recognisable cursor, so the round cannot tell a short list from a truncated one. Every count on this page should be read as a floor.

#### Derived from

- our_gaps.coverage_suspect

### sources-quiet

#### Kind

gap

#### Headline

1 source is not answering: x402scan.com.

#### Detail

Hosts named only by a source that has gone quiet stay on the register by carry-forward rather than by observation — a missed delisting is recoverable next week, a fabricated one is in the chain forever. The full register says when each last answered.

#### Derived from

- sources[].status
- sources[].last_successful_read

### corrections

#### Kind

note

#### Headline

19 corrections were published against this store during this week.

#### Detail

Corrections are dated, kept, and never quietly edited away. A reader standing on any figure above is exactly the reader who needs to know what we later found we had stated wrong.

#### Derived from

- corrections[].date

## What this is not

Not a ranking, not a score, and not a forecast. Every sentence on this page is a count over one signed week's rows, or a statement about what this instrument could not see that week. No host is ranked against another, and no figure appears without the two numbers it came from. What may be derived from these rows — a tier, a fraction — is published only with its rule, its denominator and its rows.

## How to rederive

Nothing on this page is stored. Every number is a count over https://scvd.store/corpus/5.json — the signed snapshot for 2026-W36, digest a69a2144fb5b0feee0da1003d6356dca331ccf58917e6f136ff369706d9f3722 — joined to the live source register at https://scvd.store/sources.json and the corrections record at https://scvd.store/corrections. Fetch those three and you can rebuild every sentence here, including the findings, whose rules are in services/week-ledger.ts.

## Previous week

2026-W35

## Next week

2026-W37

## Weeks held

- 2026-W32
- 2026-W33
- 2026-W34
- 2026-W35
- 2026-W36
- 2026-W37
- 2026-W38
- 2026-W39
- 2026-W40
- 2026-W41
- 2026-W42