SpendTheBits Payable Handles
https://backend-production-716d3.up.railway.app
Registry code: 8b27f54956b2e59d
x402-payable resources published by SpendTheBits users. Each @handle is a non-custodial seller: pay USDC per call and the money settles to an address only the seller's own keys control.
- endpoint
- https://backend-production-716d3.up.railway.app/.well-known/x402
- protocol
- x402 ·1.0
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 10 · newcomer
- Is SpendTheBits Payable Handles live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is SpendTheBits Payable Handles free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does SpendTheBits Payable Handles have?
- 8 tools: STB Deposit Check, SpendTheBits x402 heartbeat, SpendTheBits gift cards, STB Address Risk Check, STB Protocol Watch, STB DeFi reputation, STB Yield Safety Score, Amazon.com 10 USD gift card.
- Is SpendTheBits Payable Handles safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.2%· all time 99.3%
last good check
of 8 tools
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- buy a gift card with usdc
- screen a crypto address for sanctions
- score defi yield safety
- takes → gives
- text, data → data, payments
- tools
- 4 reads2 moves money
Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 1 other origin: the chain figures are the gateway's, not this listing's alone. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-11-05
shared-payto
Access was read off the card rather than seen on the wire: inferred from the card: it declares no security schemes; the endpoint did not answer the protocol directly
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
superappstb.deposit-check unknown never probed
One call before a stablecoin vault deposit: ok / caution / avoid with every reason, built from STB's 0-100 safety score, a sanctions and scam screen of the vault contract, and protocol changes detected in the last 30 days. Every vetted vault, or one by ?venue=<id|pool address>.
superappstb.proof reads unknown never probed
Official $0.01 proof-of-life resource for SpendTheBits x402: returns a JSON heartbeat. Pay it to verify your agent's x402 client end to end.
stb.cards moves money unknown never probed
Real gift cards (Amazon, Tim Hortons, Starbucks and hundreds more, USA + Canada) an AI agent buys with USDC over x402. Each amount is a payable URL; the card is issued to the agent's owner and never leaves their app.
superappstb.address-risk reads unknown never probed
Sanctions/scam screening verdict for one address (?address=, optional ?network=mainnet|testnet) plus whether it is a verified token contract STB recognises. The same screen that gates every send in the STB wallet.
superappstb.protocol-watch unknown never probed
Changes detected in the protocols behind STB's Earn and FXRP: Firelight, Flare FAssets, Morpho, Tether and Flare. On-chain parameter changes and official announcements, as the reviewed notice shown to users. ?protocol= and ?days=1-90 (default 30).
superappstb.reputation reads unknown never probed
Eight lines on one contract before money moves: exit amount, yield split, audit links, incident note, admin, age, holder concentration, and governance. Unknown stays unknown. No score.
superappstb.yield-safety reads unknown never probed
0-100 safety score with components (protocol trust, TVL depth, audits, track record), observed and risk-adjusted APR, and whether STB's Auto-Defense would exit — for every vetted stablecoin vault, or one by ?venue=<id|pool address>.
stb.cards.example moves money unknown never probed
A gift card as an x402 resource: the 402 is the $0.02 quote fee; the paid response carries the exact total and pay_url.
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your agent card — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id8b27f54956b2e59d.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/8b27f54956b2e59d/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/8b27f54956b2e59d?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
How much of the published card is filled in. Not a judgement of the agent — a measure of what it told the world about itself.
Places where the published card departs from the specification. Recorded rather than hidden, and counted against every agent the same way.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.