API reference
Everything in the directory is a plain JSON API — no key, read-only — so an agent can check a service, or a wallet, before it pays.
Base URL https://api.verantis.ai. All responses are JSON and include a data_generated_at timestamp for provenance. No authentication, no rate-limit key — it's a public read layer. Informational only; not financial advice.
Search the verified directory. All parameters optional.
| Param | Example | Meaning |
|---|---|---|
q | weather | Free-text over domain, name, description. |
verified | true | Only services that returned a valid live 402 challenge. |
max_price | 0.05 | Max live price, USD per call. |
chain | base | Settlement network (e.g. base, solana). |
protocol | x402 | Rail: x402 or mpp. |
limit | 20 | Result cap (default 20). |
curl "https://api.verantis.ai/v1/services?q=gas&verified=true&limit=5"
The full record for one domain — classification, live price, pay-to wallet, score breakdown, on-chain reputation, and uptime history. Extra endpoints for the same domain appear under other_records.
curl "https://api.verantis.ai/v1/services/vibesprings.net"
The pre-payment check: pass a recipient wallet and get its earned reputation before you send funds. Returns whether it's known, its tier, human-readable reasons, on-chain retention, and which services it fronts.
curl "https://api.verantis.ai/v1/check?pay_to=0x38C0..44C8"
{
"pay_to": "0x38c0…44c8",
"known": true,
"reputation": "established",
"reasons": ["217 distinct buyers in the last 90d, 83% repeat"],
"onchain": { "distinct_buyers": 217, "repeat_buyer_rate": 0.834,
"top_buyer_share": 0.257, "verdict": "distributed" },
"services_fronted": 1
}
Services grouped by the operator behind them — listings count, how many are verified, chains used, best reputation, and a neutral concentrated flag for operators fronting many listings.
curl "https://api.verantis.ai/v1/operators"
Index-level totals: endpoints, services, operators, verified count, price drift, and the rails covered.
curl "https://api.verantis.ai/v1/stats"
Verantis is also a native Model Context Protocol (MCP) tool — a thin client of this same API — so any MCP-capable agent can query the directory, and check a wallet before it pays, without touching raw HTTP. Two ways to connect:
What this MCP can and can’t do
Can: read the public directory; check a service or wallet before your agent pays.
Can’t: move money, see your keys, or read your files — it only ever calls api.verantis.ai, nothing else.
Writes: nothing on the hosted endpoint; the local package stores only a random anonymous install id (no personal data).
No account, no API key. MIT-licensed. Read-only. How we measure →
Local (stdio) — install with uvx verantis-mcp (or pip install verantis-mcp):
{
"mcpServers": {
"verantis": { "command": "uvx", "args": ["verantis-mcp"] }
}
}
Hosted (streamable HTTP) — connect a remote-capable client straight to the endpoint, no install:
{
"mcpServers": {
"verantis": { "url": "https://api.verantis.ai/mcp" }
}
}
Published on PyPI and the official MCP registry. Tools: find_paid_service, get_service, check_wallet, directory_stats.
Fields describe what our probes and on-chain reads observed at a point in time and can change between checks. The API is read-only and informational — not financial, investment, or legal advice. See the methodology for how each field is measured.