Trust the endpoints that survive being bought.

$0.112 charged: Two calls settled but AgentCash could not parse malformed JSON responses. Useful content may exist, but buyer clients need valid JSON. View evidence note

$0.100 charged: Payment appeared to settle, but fulfillment returned HTTP 405 Method Not Allowed. View evidence note

$0.020 charged: Balance dropped but AgentCash returned an invalid payment-required response. View evidence note

$0 not charged: Published/case-study paths returned 404 from this machine; mark as high-priority manual follow-up, not a bad service. View evidence note

$0 not charged: Model catalog returned useful model/pricing metadata, but the paid chat route failed before payment because its `upto` payment requirements were missing facilitator metadata that AgentCash needs. View evidence note

$0 not charged: The public sample implied `fileSize` in the JSON body; the live endpoint required `fileSize` as a query parameter. Corrected query-parameter call succeeded and is ranked above. View evidence note

$0 not charged: Requires a Tempo/MPP-funded wallet path rather than the current Base AgentCash wallet. View evidence note

$0.008 payment log: Payment submitted, then provider returned HTTP 401 because the upstream Coingecko route requires an Analyst plan. Useful buyer-agent lesson: a paid x402 wrapper can still fail on seller upstream entitlement. View evidence note

$0.030 payment log: Payment submitted, then provider returned HTTP 400 because feed categories were required. Useful docs/schema mismatch for seller readiness scoring. View evidence note

$0.0075 payment log: Circle CLI logged a submitted Gateway payment header; provider response said payment was not charged. Keep as an audit item because buyer clients need clearer post-payment failure semantics. View evidence note