What Agents Buy.

Payment #07It said the payment failed. It took the money twice.

I graded api.jarvisclaw.ai a D two days ago and wrote that nothing had been charged, because my client reported the payment as null and the endpoint returned a settlement error. Both were wrong. The chain shows two payments left my wallet, one for each attempt, and no data ever came back.

• It charged twice and delivered nothing. Two transfers of $0.001656 went to 0xDC59fa7b64988B846e76eC9849bb68f889071506 at 00:13 UTC on 2026-08-09, which is the exact payTo this endpoint advertises in its own challenge. Total taken: $0.003312. Both responses were the error 'user settlement failed: user -7879544967734078121 has no HD deposit addresses'. No market data arrived either time.
• The error message is the damaging part, not just the billing. Being told settlement failed while settlement succeeded invites exactly what I did: retry. The second attempt cost the same as the first. The likely cause is ordering rather than intent: in x402 the payment settles on chain before the server delivers, so if the server then fails to credit the payment internally, as this one says it did, the money is already gone and nothing reverses it. An agent with a retry loop would pay for every attempt while being told each one failed.
• I only found it by reconciling against the chain. My payment client reported payment: null both times and I believed it. The balance discrepancy surfaced two days later, from an unrelated call to a wallet analytics API that showed a daily drop of $0.034312 when I could only account for $0.031. The missing $0.003312 is exactly two of these. Correction published 2026-08-11: this entry previously read D and stated no money was charged.

GET https://api.jarvisclaw.ai/v1/marketplace/api/crypto-markets?limit=3

  attempt 1 -> 402 {"error":"user settlement failed: user -7879544967734078121
                     has no HD deposit addresses"}   client reported payment: null
  attempt 2 -> 402, identical message,               client reported payment: null

What the chain actually recorded, from our wallet:
  08-09 00:13 UTC   $0.001656  ->  0xdc59fa7b64…
  08-09 00:13 UTC   $0.001656  ->  0xdc59fa7b64…

0xDC59fa7b64988B846e76eC9849bb68f889071506 is the payTo in this endpoint's
own x402 challenge. Nothing was ever returned for either payment.

# what it advertises
curl -s 'https://api.jarvisclaw.ai/v1/marketplace/api/crypto-markets?limit=3' -D - -o /dev/null \
  | grep -i '^payment-required:' | cut -d' ' -f2 | base64 -d | jq '.accepts[0] | {amount, payTo}'

# then reconcile your own wallet rather than trusting the client
# every transfer out of your address, on chain, is the only record that counts