Roundhouse
Capabilities

Unified Services

Endpoints grouped by the job they do. Every provider of one capability is mapped onto the same request and the same response, so a price is comparable to the price beside it.

34
Capabilities
each with its own canonical output
1,465
Endpoints grouped
matched with high confidence
903
Provider wallets
counted once per capability
1,000×
Widest price spread
cheapest to dearest, domain and dns lookup

One card per capability, in registry order.

Web & Content

Crypto Markets

Onchain Data

Risk & Compliance

Company & People

Location & Weather

AI & Media

How a capability is decided

An endpoint joins a capability on four signals: the last segment of its URL, its own name, phrases in its description and tags, and the subject it is about. A match needs two of those to agree before it is counted here — a bare /search path is published by 173 different wallets and they are not all searching the web. Endpoints matched on one signal alone are kept out of the comparison and shown separately on each capability page.

Prices are the figure the catalog carries, in USDC, per the unit named on each capability. Read the live 402 before paying: a catalog price is a claim, not a quote.

The spot rate is what a call to a capability costs on average, weighted by how often each endpoint is called. A plain median would count one wallet’s forty near-identical listings as forty votes for its price, which turns a listing strategy into a market rate. Each supplier is indexed against spot on its capability page, where 100 is the going rate.

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will compare every provider of one capability over the free read API. No key, no account.

GET www.roundhouse.studio/api/v0/endpoints

Open skill.md
Show the prompt
Using Roundhouse Unified Services, tell me which x402 providers offer
the capability I need and what each one charges for the same unit of work.

curl -s 'https://www.roundhouse.studio/unified.json'
curl -s 'https://www.roundhouse.studio/unified.json?capability=<slug from the list above>'

Every offer in one capability is mapped onto the same request and response, so
the prices compare directly. Read the live 402 before paying, never the catalog price,
and check the provider's payment record first:
curl -s 'https://www.roundhouse.studio/api/v0/merchants/<the payTo wallet on the offer>'

If you do not have Roundhouse tools or skills installed, read
https://www.roundhouse.studio/skill.md first — it is the whole procedure, and it needs no key.