Sato Hub
x402 merchant

agent-budget-guard.onrender.com

x402 API on Base, paid per request with x402.

  • Endpoints5
  • Price per requestfrom $0.001
  • Outside payers · 7dn/a
  • Answer 4022 of 3

Overview

as of 2026-11-20
Seller wallet
0x60c402878efcecae5733a88075328aa2320c39be
Chains
Base
Hosts
agent-budget-guard.onrender.com, external-fuse.onrender.com, fractal-scaling-api.onrender.com, shared-hold-api.onrender.com, tensegrity-control-mesh.onrender.com
CategoriesCategoriesAssigned automatically from the seller’s own listing text. A filter hint, not a claim about the service.
Other3Developer tools1Security1
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.
5 registered
  • https://external-fuse.onrender.com/provision

    External Fuse

    BaseOther

    $0.001/ request

    2026-11-14

  • https://shared-hold-api.onrender.com/hold

    Store payload to Shared Hold boundary - 0.005 USDC per successful hold

    BaseDeveloper tools

    $0.005/ request

    2026-11-08

  • https://tensegrity-control-mesh.onrender.com/inspect

    Deterministic structural failure inspection of a caller-declared control mesh. Structural evidence only; never authorizes execution. 0.01 USDC per request.

    BaseOther

    $0.01/ request

    2026-10-24

  • https://fractal-scaling-api.onrender.com/scale

    Fractal scale operation - 0.02 USDC per successful request

    BaseOther

    $0.02/ request

    2026-10-26

  • https://agent-budget-guard.onrender.com/api/budget/check

    Agent Budget Guard: pre-payment budget check, spending limits, allow/deny approval and audit evidence for AI agent x402 USDC payments

    BaseSecurity

    $0.03/ request

    2026-10-26

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.

2 of 3

2 of 3 probed endpoints answered HTTP 402 with a parseable payment payload

checked 2026-11-07

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 58811722 (574000 of 3024001 blocks read))

window ended 2026-11-19

By chain

ChainSeller walletEndpointsAnswers 402x402-style payments
Base0x60c402878efcecae5733a88075328aa2320c39be52 of 3 probed endpoints answered HTTP 402 with a parseable payment payload
2026-11-07
unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks read))

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.001
per request, as registeredas of
Median
$0.01
per request, as registeredas of
Highest
$0.03
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 0x60c402…0c39be 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.