verantis
Registry code: 99d3fad74cb8b758
Verified directory for machine payments (x402 & MPP): check services and wallets before agents pay.
from a public catalogue that lists it, not from the operator
- endpoint
- https://api.verantis.ai/mcp
- 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 verantis live?
- Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
- Is verantis free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does verantis have?
- 4 tools: check_wallet, find_paid_service, get_service, directory_stats.
- Is verantis 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%· all time 99%
last good check
of 4 tools
- degraded → live
- live → degraded· HTTP 502
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- check a wallet before paying it
- search machine-payable services
- get a paid service's reputation record
- takes → gives
- text → 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.
check_wallet reads open 13h ago
Check a recipient wallet BEFORE your agent pays it — a pre-payment guard. Pass the pay-to address a service asked you to pay; returns whether Verantis knows the wallet, its EARNED reputation tier, and human-readable reasons. A wallet IS a settlement rail, so the reply names the rail it settles on ('rail': chain + protocols), its host, on-chain buyer retention (distinct buyers, repeat rate, distribution), and the host's OTHER rails ('also_settles_on'). If 'shared_wallet' is true the address fronts many services (a relay/treasury) so the reputation reflects the pool, not one service — treat with care. An unknown or low-reputation recipient is a reason to pause.
{ "type": "object", "required": [ "pay_to" ], "properties": { "pay_to": { "type": "string", "description": "recipient wallet address (0x… for Base/EVM, base58 for Solana)" } } }arguments 12 linesfind_paid_service reads open 13h ago
Search Verantis's verified directory of machine-payable services (x402, MPP). Results are UNIFIED per service (host): each carries its settlement rails ('rails': base / solana / tempo), and every rail has its OWN reputation, price, and buyer retention — never blended. Pass 'chain' and 'matched_rail' marks that chain's rail so you see the reputation for the rail you'll actually pay on. 'coming_soon' lists advertised chains not yet measured. Each rail's 'wallet_scope' says if its pay-to wallet is 'dedicated' (the buyers/payments/volume are this service's own) or 'shared' (a relay/treasury fronting 'wallet_services' services, so those figures are the pool's inbound, not this service alone). Prefer verified=true before paying anyone.
{ "type": "object", "required": [ "query" ], "properties": { "chain": { "type": "string", "description": "settlement network, e.g. base, solana, polygon, tempo" }, "limit": { "type": "integer", "default": 10, "description": "maximum number of results to return (default 10)" }, "query": { "type": "string", "description": "what you need, e.g. 'twitter data', 'web search', 'rpc ethereum'" }, "protocol": { "enum": [ "x402", "mpp" ], "type": "string", "description": "restrict to one payment protocol: x402 or mpp" }, "min_score": { "type": "integer", "description": "minimum trust score 0-100 — set high (e.g. 85) for money-moving tasks" }, "proven_only": { "type": "boolean", "default": false, "description": "only services that have EARNED reputation over time (excludes 'new' services and 'watch' services whose on-chain payments are concentrated / not yet broadly distributed). Reputation is earned via consistent history + on-chain buyer retention; a brand-new well-behaved service is verified but new, not top-trust." }, "max_price_usd": { "type": "number", "description": "max price per call in USD" }, "require_fresh": { "type": "boolean", "default": false, "description": "live re-probe stale results before returning — use before paying real money; adds ~1s per stale service" }, "verified_only": { "type": "boolean", "default": true, "description": "only services that passed the latest live probe" }, "max_latency_ms": { "type": "integer", "description": "reject services slower than this (ms)" }, "exclude_concentrated": { "type": "boolean", "default": false, "description": "exclude services from operators with many listings under one registrable owner (a neutral concentration signal, not a fraud claim)" } } }arguments 61 linesget_service reads open 6h ago
Full unified record for one service host: every settlement rail it accepts on, each with its own reputation, price, buyers, volume and history, plus coming-soon chains. Each rail's 'wallet_scope' marks a 'shared' pay-to wallet (buyers/volume are pooled inbound across 'wallet_services' services, not this one alone) vs 'dedicated' (this service's own). Pass the host (domain).
{ "type": "object", "required": [ "domain" ], "properties": { "domain": { "type": "string", "description": "the service host / domain to look up, e.g. api.nansen.ai" } } }arguments 12 linesdirectory_stats reads open 13h ago
Index-level statistics: services, verification breakdown, data freshness.
{ "type": "object", "properties": {} }arguments 4 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 id99d3fad74cb8b758.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/99d3fad74cb8b758/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/99d3fad74cb8b758?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.