Sato Hub
x402 merchant

fmcsa-mcp-843680657471.us-central1.run.app

Security API on Base and Polygon, paid per request with x402.

  • Endpoints6
  • Price per requestfrom $0.01
  • Outside payers · 7d1
  • Answer 4024 of 4

Overview

as of 2026-10-14
Seller wallet
0x4c96766f29d98a363a23c30cf739e4dd1cbca5d4
Chains
BasePolygon
Hosts
fmcsa-mcp-843680657471.us-central1.run.app
CategoriesCategoriesAssigned automatically from the seller’s own listing text. A filter hint, not a claim about the service.
Security4Identity2
First seen
2026-10-14 · last seen 2026-10-14

What we observed

Paid by 1 outside payer · 7d, observedAnswers 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.
6 registered

  • https://fmcsa-mcp-843680657471.us-central1.run.app/x402/lookup_carrier

    Use this when you already have a carrier's USDOT number and need its current profile: safety rating, authority status, insurance flags, fleet size. Returns Active, Inactive, and Pending carriers alike. Billed only when …

    BaseSecurity

    $0.01/ request

    2026-10-13

  • https://fmcsa-mcp-843680657471.us-central1.run.app/x402/search_carriers

    Use this when you don't have a USDOT number yet and need to filter carriers by state, safety tier, authority status, or cargo type — for example, every carrier with an unsatisfactory rating in a given state. Capped at 1…

    BaseSecurity

    $0.02/ request

    2026-10-13

  • https://fmcsa-mcp-843680657471.us-central1.run.app/x402/check_carrier_identity

    Use this when a carrier looks suspicious — a name change, a new USDOT number tied to an old fleet, a business you suspect re-registered after a revocation — and you need the full evidence: every other USDOT number shari…

    BaseIdentity

    $0.05/ request

    2026-10-13

  • https://fmcsa-mcp-843680657471.us-central1.run.app/x402/check_carrier_identity

    Use this when a carrier looks suspicious — a name change, a new USDOT number tied to an old fleet, a business you suspect re-registered after a revocation — and you need the full evidence: every other USDOT number shari…

    PolygonIdentity

    n/a/ request

    2026-10-13

  • https://fmcsa-mcp-843680657471.us-central1.run.app/x402/lookup_carrier

    Use this when you already have a carrier's USDOT number and need its current profile: safety rating, authority status, insurance flags, fleet size. Returns Active, Inactive, and Pending carriers alike. Billed only when …

    PolygonSecurity

    n/a/ request

    2026-10-13

  • https://fmcsa-mcp-843680657471.us-central1.run.app/x402/search_carriers

    Use this when you don't have a USDOT number yet and need to filter carriers by state, safety tier, authority status, or cargo type — for example, every carrier with an unsatisfactory rating in a given state. Capped at 1…

    PolygonSecurity

    n/a/ request

    2026-10-13

Evidence

as of 2026-10-14

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.

4 of 4

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

checked 2026-10-14

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.

1outside payer

2 x402-style payments from 1 distinct payer, $0.02 USDC in the last 7 days (Base, exact read)

window ended 2026-10-14

Payments
2
Payers
1
USDC
0.02

This window shows the pattern of machine noise (few payers, dust amounts), so it does not count toward the evidence ranking.

All USDC received at this payout address: $0.02 (includes payments that are not x402)

Reading: x402-style payments to this payout address on Base, exact read of the 7 days to 2026-10-14, every block of the window: 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; Sato Hub's own payer wallets are left out

By chain

ChainSeller walletEndpointsAnswers 402x402-style payments
Base0x4c96766f29d98a363a23c30cf739e4dd1cbca5d432 of 2 probed endpoints answered HTTP 402 with a parseable payment payload
2026-10-14
2 x402-style payments from 1 distinct payer, $0.02 USDC in the last 7 days (Base, exact read)
Polygon0x4c96766f29d98a363a23c30cf739e4dd1cbca5d432 of 2 probed endpoints answered HTTP 402 with a parseable payment payload
2026-10-14
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
$0.01
per request, as registeredas of
Highest
$0.05
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 0x4c9676…bca5d4 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-10-14. Appearing here is not an endorsement. Check an endpoint with the doctor.