Neutral · cross-rail · continuously verified
As agents start paying for services, someone has to check what's actually real. Verantis probes every listing live, measures on-chain settlement, and publishes a track record anyone can recompute.
Live from the index, refreshed on a schedule — the numbers above update themselves. Full feed at api.verantis.ai/v1/stats.
The problem
Agents can now pay for APIs and services autonomously across a growing set of rails — Coinbase's x402, the Merchant Payment Protocol, and more arriving. But there is no neutral place to answer the questions that matter before a machine spends money: Is this endpoint real? Is it live right now? Does it charge what it says? Has it actually earned trust over time?
Verantis exists to answer exactly those questions — for every listing, continuously, in the open.
How it works
Two independent layers — live verification and earned on-chain reputation — reported separately, never blended into one opaque score.
We send an unpaid probe to every service and read the live HTTP 402 payment challenge it returns — confirming the endpoint is reachable, payable, and priced as advertised. Each listing is classified by what we actually observed, and re-checked on a schedule.
For services that settle on-chain, we measure real stablecoin settlement and buyer retention over a fixed window (Base and Solana USDC) — so reputation is comparable across services and reflects sustained use, not a single big day.
See it live
Every listing shows its live-verification status, earned reputation tier, price, and settlement history — filterable, and refreshed on a schedule.
Illustrative layout with example domains. Explore the real, live directory at app.verantis.ai.
Why trust it
The one thing that can't be faked is a track record. Because we re-verify continuously, every service accumulates an uptime and price-stability history that cannot be back-dated — a record you can check today and check again next month.
For agents & builders
Everything on the directory is available as a plain JSON API and as a Model Context Protocol (MCP) tool, so an agent can check a service — or a wallet — before it pays.
Check a service, or a wallet before paying it:
GET https://api.verantis.ai/v1/services?q=weather&verified=true GET https://api.verantis.ai/v1/check?pay_to=0x…
Add the Verantis MCP server and any MCP-capable agent can query the verified directory directly. See the methodology for what each field means.