Sato Hub
x402 merchant

mcp.agenteconomy.cloud

x402 API on Base, paid per request with x402.

  • Endpoints1
  • Price per request$0.10
  • Outside payers · 7dn/a
  • Answer 4021 of 1

Overview

as of 2026-11-20
Seller wallet
0xeed6af31937a6123924d4ecdc3b3ed729f92867e
Chains
Base
Hosts
mcp.agenteconomy.cloud
CategoriesCategoriesAssigned automatically from the seller’s own listing text. A filter hint, not a claim about the service.
Other1
First seen
2026-10-05 · last seen 2026-11-20

What we observed

Payments unknown, unknownAnswers 402, observedNot claimed
See the readings

Endpoints

EndpointsDescriptions are the seller's own words from the catalogue and are not checked by us. A listed price is a registration, not an observed charge.
3 registered
  • https://mcp.agenteconomy.cloud/api/v1/verify

    Use when your agent is about to pay an x402 seller it has never paid before, or before a large spend. Is this x402 seller safe to pay? One call returns its on-chain payment history — verified USDC revenue, real distinct…

    BaseOther

    $0.10/ request

    2026-11-16

  • https://mcp.agenteconomy.cloud/api/v1/check

    Does this x402 seller actually deliver when paid? We test the full flow as a real buyer: quote, 402 requirements validation, a real capped probe purchase, settlement and delivery — not a lint that stops before money mov…

    BaseDeveloper tools

    $0.25/ request

    2026-09-06

  • https://mcp.agenteconomy.cloud/api/v1/diagnose

    Listed but never paid? One call answers why. We run a real paid test purchase against your x402 endpoint (not a lint) and name the exact fault when the flow breaks — 402-again loops, invalid_payload, malformed accepts. …

    BaseDeveloper tools

    $1.00/ request

    2026-09-06

Evidence

as of 2026-11-20

Answers HTTP 402

Answers HTTP 402Method: one unpaid request per listed endpoint. A 402 with a payment payload a client could parse counts. Nothing is paid.

1 of 1

1 of 1 probed endpoints answered HTTP 402 with a parseable payment payload

checked 2026-10-03

x402-style payments, 7-day window (Base)

x402-style paymentsMethod: counted when the transaction carries a signed USDC authorization (EIP-3009), the settlement x402's exact scheme uses. Some non-x402 gasless sends use it too.

unknown

unknown. the 7-day payments read on Base did not complete (time budget spent at block 58121486 (400000 of 3024001 blocks read; the request in flight ran out of time))

window ended 2026-11-17

By chain

ChainSeller walletEndpointsAnswers 402x402-style payments
Base0xeed6af31937a6123924d4ecdc3b3ed729f92867e11 of 1 probed endpoints answered HTTP 402 with a parseable payment payload
2026-10-03
unknown. the 7-day payments read on Base did not complete (time budget spent at block 58121486 (400000 of 3024001 blocks read; the request in flight ran out of time))

One seller wallet, each chain read on its own. We never send a payment, so we never observe what a paid call returns. Unknown means we hold no reading, not that anything failed.

Pricing

Lowest
$0.10
per request, as registeredas of
Median
$0.10
per request, as registeredas of
Highest
$0.10
per request, as registeredas of

The price each endpoint registered in the x402 catalogue. A listed price is a registration, not an observed charge.

Claim this merchant

Sign a message from the payout address 0xeed6af…92867e to claim this page or download its payment ledger. Claiming proves control of the payout key. It says nothing about the service behind the address, and it does not change how this merchant is ranked. No email, no account: the signature is the whole credential, and signing a message costs no gas and moves nothing.

Data CC-BY-4.0, attribution: data by satohub.ai. Data as of 2026-11-20. Appearing here is not an endorsement. Check an endpoint with the doctor.