What the score read on this service: status online, 99.9% uptime 30d, 883ms response p95, x402 compliance 14 of 14, price not captured, no known payTo, so no on-chain traction to read. Each of those is measured, and each is published in full below.
The score comes from our own monitoring, never from reviews, operator claims, or a language model: reliability, x402 compliance, price against the category, a deterministic risk flag, and a small on-chain traction term, weighted by ranking generation 3. It is not placement anyone can buy: the paid verify tier is reported beside it and is not one of its inputs. Every component below stays published and read-only.
It is a score inside Data, and only there: price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, which here means 300 listings, this one among them. That set is wider than the 300 the position above is counted against, because a listing we have measured too little of to rank still sits in the field the price and the speed are normalized over. The same service in a different field would read differently. The same engine answers GET /api/v1/best, and asked for a different pool (the whole directory, or another filter) it returns a different number for this service under this same ranking generation. Neither is more correct: they answer different questions, and the methodology states which is which.
Bands on the 0 to 100 measured score: strong at 93 and above, solid from 75, mixed from 55, weak below 55. Price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, so the score places a service in its own field.
ALTERNATIVES IN DATA
Other Data services in this directory, ordered by the same measured score. The figures are ours: 30-day uptime from our own probes, 30-day settlement volume read on-chain (a conservative undercount, and null where we cannot measure it, never a zero).
Ranked alternative x402 services in the same category, with band, measured score, 30-day uptime and 30-day on-chain settlement volume
The parts the verdict above is computed from, each with its proof. Click any chip. Measured values stay read-only; unknown is honest, and an unknown is never counted as a zero.
reliability99.9%
uptime 24h
100%
uptime 7d
99.8%
uptime 30d
99.9%
uptime 90d
99.7%
response p95
883ms
avg response
556ms
total checks
7,277
Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.
complianceA (14/14)
14 of 14 x402 conformance checks pass. Full checklist below.
No deterministic risk flag. Risk fires only on an exact blocklist match, or a reserved-brand name with a mismatched verified payTo. Never from low uptime, a high price, or a model guess.
domain age
-
registrar
-
hosting
custom
domain created
---
Identity facts, not a risk score.
traction---
No settlement address is mapped for this service yet, so on-chain volume cannot be measured. Shown as unmeasured, not zero.
WHAT IT DOES
ai-derived
Retrieves NFT and token balances for blockchain addresses
category
crypto-balance
in
path
blockchainnfttoken-balancescrypto
AI-generated summary. The measured data is never altered by it.
ENDPOINTS
Service endpoints with HTTP method, path, description, pricing, and network
METHOD
PATH
DESCRIPTION
PRICE
NETWORK
ASSET
402 CHANNEL
GET
/{chain}/address/{address}/balances_nft/
NFT balances
---
Base Sepolia
USDC
header
GET
/{chain}/address/{address}/balances_v2/
Token balances
---
Base Sepolia
USDC
header
2 endpoints
REQUEST / RESPONSE EXAMPLE
An unpaid request to GET /{chain}/address/{address}/balances_nft/ returns HTTP 402 with the payment terms. Settle onchain via your facilitator, then retry with the X-Payment header.
All charts use the 90d selector; each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/goldrush/price, /scores, /volume and /buyers. On-chain volume and distinct buyers are measured over the service's settlement address and are a conservative undercount (only settlements that reach a measured facilitator are counted). The on-chain series roll up hourly, so the latest day can be up to about an hour behind; distinct buyers are counted per payout address, so a service that settles to more than one address is an upper bound.
UPTIME
90d UPTIME███▇██████████████████████████99.7%
RESPONSE TIME
AVG RESP556ms
PRICE (captured 402, USD)
SUB-SCORES (uptime + x402 compliance)
checklist grew 11->14 on 2026-07-28; a step here is a metric change, not a regression
PILLARS OVER TIME (measured)
price percentile in Data
site signals present (of 6)
Measured site and economics pillars from the assessment history, so the latest value shown elsewhere on this page reads as a point on a trend rather than a permanent state.
VOLUME (on-chain settlement, USD)
No settlement address is mapped for this service yet, so on-chain volume cannot be measured. Shown as unmeasured, not zero.
DISTINCT BUYERS
No settlement address is mapped for this service yet, so distinct on-chain buyers cannot be measured. Shown as unmeasured, not zero.
COMPLIANCE
14/14 checks pass · grade A
last 402 captured 2026-06-16 · last up 2026-09-20
ok402 payload captured
okaccepts[] array present
okpayTo address recoverable
okpayTo at accepts[0].payTo (conformant shape)
okpayTo is a valid on-chain address
okatomic price declared
okatomic price in a sane range
okasset (token) address declared
oknetwork resolves to CAIP-2
okpayment scheme declared
okserved over HTTPS
okdeclares the current x402 version (2)
okEIP-712 domain parameters present on every EVM entry
okx402 v2 envelope delivered in the payment-required header
SITE PILLARS
xhomepage reachable
xopenapi doc
xpricing page
xllms.txt
xrobots.txt
xterms page
recent checks (18) live · click to expand
TIMESTATUSRESPCAUSE
● OK158ms
● OK240ms
● OK561ms
● OK532ms
● OK445ms
● OK424ms
● OK607ms
● OK503ms
● OK468ms
● OK526ms
● OK456ms
● SLOW1025ms
● OK233ms
● OK629ms
● OK502ms
● OK465ms
● SLOW884ms
● OK466ms
EMBED THIS BADGE
Show that GoldRush is monitored on x402-list. Paste this on your site or README, it links back to this live listing.
statuslive uptime
// HTML
<a href="https://x402-list.com/services/goldrush?utm_source=badge&utm_medium=referral&utm_campaign=embed">
<img src="https://x402-list.com/badge/goldrush.svg" alt="GoldRush listed on x402-list" height="28">
</a>
// Markdown
[](https://x402-list.com/services/goldrush?utm_source=badge&utm_medium=referral&utm_campaign=embed)
// HTML · live uptime variant
<a href="https://x402-list.com/services/goldrush?utm_source=badge&utm_medium=referral&utm_campaign=embed">
<img src="https://x402-list.com/badge/goldrush.svg?data=uptime" alt="GoldRush uptime on x402-list" height="28">
</a>
RUN THIS SERVICE?
Keep this listing accurate: propose changes to the name, description, website, category or add new endpoints to monitor. Ownership is verified with a domain proof and every change is reviewed manually; measured data stays read-only.
Earn the verified tier: x402list pays a real call to this endpoint and, if it delivers, the service is delivery-verified. The fee covers the cost of the probe, not the badge; there is no refund if the call does not deliver. Agent and API only, no in-browser signing. See /api.