raptor-x402
https://raptor-base-yields.vercel.app
Registry code: 0aba8d4a4cff70cc
Live USDC lending APY on Base, read on-chain: Aave V3 USDC vs Morpho Gauntlet USDC Prime. Size-aware pick for parking idle USDC: USD per year, days to break even vs Base gas, skip if entry is uneconomic. Conservative two venues only.
from a public catalogue that lists it, not from the operator
- endpoint
- https://raptor-base-yields.vercel.app/
- door code
- 5c6c9b212fa6f316
- protocol
- HTTP+JSON ·1.0
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 10 · newcomer
- Is raptor-x402 live?
- Yes — it answered the hub's last check (checked 18h ago). It answered 100% of checks over the last 30 days.
- Is raptor-x402 free to use?
- No — it charges per call, quoted in its own 402 answers.
- What tools does raptor-x402 have?
- 2 tools: get_yields, get_wallet.
- Is raptor-x402 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.1%· all time 98.5%
last good check
of 2 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- compare stablecoin lending yields
- decide where to park idle stablecoins
- takes → gives
- data → data
- tools
- 2 reads
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. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-11-04
no flags
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.
get_yields reads unknown never probed
Base USDC lending APY. Live USDC lending yield on Base, read on-chain: Aave V3 USDC vs Morpho Gauntlet USDC Prime. Size-aware pick for parking idle USDC: USD per year, days to break even vs Base gas, skip if entry is uneconomic. Conservative two venues only. No leverage, looping, memecoins, or perps.
get_wallet reads unknown never probed
Base USDC lending APY. Should you park this wallet's USDC on Base? Snapshot of native USDC + ETH, then the same size-aware Aave V3 vs Morpho Gauntlet USDC Prime yield pick (USD per year, days to break even, skip if gas eats it). Not a deposit instruction.
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 MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id0aba8d4a4cff70cc.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/0aba8d4a4cff70cc/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/0aba8d4a4cff70cc?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.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
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.