Sato Hub
x402 merchant

agentpay.tools

Market data API on Stellar, paid per request with x402.

  • Endpoints3
  • Price per requestn/a
  • Outside payersn/a
  • Answer 4021 of 1

Overview

as of 2026-10-28
Seller wallet
GB7THTEVT2T7CZQ5TFUOIQSI32XCJ7BHWS35OBTAI2V4FNL7BXZZ2GM2
Chains
Stellar
Hosts
agentpay.tools
CategoriesCategoriesAssigned automatically from the seller’s own listing text. A filter hint, not a claim about the service.
Market data1Onchain data1Security1
First seen
2026-10-28 · last seen 2026-10-28

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://agentpay.tools/tools/pre_trade_check/call

    Pre-trade risk check for AI agents trading crypto: live orderbook slippage at YOUR size, side-aware funding carry, open-interest crowding, and optional contract security — composed into a single ok/caution/avoid verdict…

    StellarMarket data

    n/a/ request

    2026-10-28

  • https://agentpay.tools/tools/session_create/call

    A stateful, multi-chain spending session for AI agents. One session enforces a hard USDC budget cap across every tool call, with a verifiable receipt and running ledger for each payment — not a one-shot budget check, bu…

    StellarOnchain data

    n/a/ request

    2026-10-28

  • https://agentpay.tools/tools/verified_route/call

    Buyer-side trust oracle for the x402 marketplace: 'I need X, budget $Y — which tool is real?' Sweeps the WHOLE catalog across many queries, collapses sybil/factory clusters (one wallet stamping many fake-distinct listin…

    StellarSecurity

    n/a/ request

    2026-10-28

Evidence

as of 2026-10-28

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-05

x402-style payments, last 7 days (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. not measured on this chain yet

no reading date

By chain

ChainSeller walletEndpointsAnswers 402x402-style payments
StellarGB7THTEVT2T7CZQ5TFUOIQSI32XCJ7BHWS35OBTAI2V4FNL7BXZZ2GM231 of 1 probed endpoints answered HTTP 402 with a parseable payment payload
2026-10-05
unknown. not measured on this chain yet

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
n/a
per request, as registeredas of
Median
n/a
per request, as registeredas of
Highest
n/a
per request, as registeredas of

Unknown. Prices are decoded only for USDC on Base and Solana.

Claim this merchant

Sign a message from the payout address GB7THTEV…ZZ2GM2 to claim this page. 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.

The payment ledger covers Base only for now, so it is not offered for Stellar.

Data CC-BY-4.0, attribution: data by satohub.ai. Data: x402-list.com (CC BY 4.0). Data as of 2026-10-28. Appearing here is not an endorsement. Check an endpoint with the doctor.