obolpay-x402-gateway
Registry code: d89d5f8b6913d031
Free, keyless tools for Obolpay Gateway (paid data over the x402 protocol; x402™ is a trademark of LF Projects, LLC.): discover (manifest), preview (evaluate before paying; pass types to scope), balance (account balance lookup), verify_receipt (proof-of-purchase check). Purchasing itself uses the standard x402 HTTP 402 flow at /api/v1/protected-data — never send private keys anywhere.
- endpoint
- https://pay.obolpay.xyz/mcp
- door code
- b140abb641204760
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is obolpay-x402-gateway live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is obolpay-x402-gateway free to use?
- Not measured yet.
- What tools does obolpay-x402-gateway have?
- 4 tools: discover, preview, balance, verify_receipt.
- Is obolpay-x402-gateway 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.5%· all time 99.8%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- read a paid data gateway's price manifest
- preview a paid dataset before buying
- look up an account balance
- verify a signed purchase receipt
- takes → gives
- text, data → data
- tools
- 4 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
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.
discover reads unknown never probed
Return this x402 gateway's machine-readable manifest: price, token, network, recipient, payment flow, capabilities. Same document as GET /.well-known/x402. No payment required.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linespreview reads unknown never probed
Free preview of the paid dataset so you can evaluate BEFORE paying (trustless). Optionally pass `types` to scope the preview to the categories you would actually buy (?types=). No invoice is created; to purchase, GET /api/v1/protected-data and follow the 402 challenge.
{ "type": "object", "properties": { "types": { "type": "array", "items": { "type": "string" }, "description": "Optional category filter, e.g. [\"jp-business-day\"]. Unknown categories are listed in the result's available_types." } }, "additionalProperties": false }arguments 13 linesbalance reads unknown never probed
Look up an existing account balance at this gateway (top-ups are not accepted; a balance comes only from earlier top-ups or automatic refund credits): balance_units, calls_remaining, next_nonce and the voucher message to sign. Read-only. Signing and spending happen on YOUR side with YOUR key — this server never asks for a private key.
{ "type": "object", "required": [ "address" ], "properties": { "address": { "type": "string", "description": "0x… EVM address" } }, "additionalProperties": false }arguments 13 linesverify_receipt reads unknown never probed
Verify a signed purchase receipt issued by this gateway: recovers the EIP-191 signer of (message, signature) and checks it equals the server's receipt signer. Anyone can verify — no payment required.
{ "type": "object", "required": [ "message", "signature" ], "properties": { "message": { "type": "string" }, "signature": { "type": "string" } }, "additionalProperties": false }arguments 16 lines
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 idd89d5f8b6913d031.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/d89d5f8b6913d031/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/d89d5f8b6913d031?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.