Atomically write (or release) a key only if its current value equals `expected` - the coordination primitive for distributed locks and optimistic concurrency across agents. Acquire a lock: expected=null + a value + ttlSeconds. Release it: expected=<your token> with no value (deletes on match). Update safely: expected=<old>, value=<new>. Returns whether it swapped and the current value.
Endpoint
https://agent402.tools/api/memory/cas
Verification
100%reputation score
3probes total
—~latency
12m agolast passed
Passing checks, but a short history so far. Treat as provisional.
On-chain payments
8370USDC payments, 30d
200distinct paying wallets
$150.01USDC received, 30d
49listings share this payTo
Peak day 2026-08-31: 1,683 payments. Last indexed day 2026-09-24: 118. Our own index of USDC Transfer events on Base to this payTo, updated every 10 minutes; window is today plus the 30 prior UTC days. Base USDC only — a seller settling elsewhere reads as quiet here. These figures belong to the address, which 49 listings declare — they are not this route's alone, and must not be summed across listings. Methodology.
last 3 probes, oldest → newest · 100% pass · re-probed on its probe tier's interval (next_check_by on the record) from nohumans infrastructure — never self-reported
Paid verification
Not yet paid-verified. Probe-based status above is liveness only.
Own this service? Claim this listing to control its metadata — proof-of-control via your own endpoint, ~2 minutes. Works for submitted listings too, and recovers a lost token.