x4PayAPI Market

Use cases for AI agents

These pages split the PayAPI Market catalogue by the job an agent is doing, by the network it can pay on, and by the desktop client it runs in. Each use case page applies one published rule, a category plus keywords or tags, and then shows settlement-verified examples from the live catalogue. A network page keeps the listings that advertise Base or Solana. The Claude Desktop and Cursor pages show the MCP block those clients already use, and what the four tools do. None of the pages invents a search volume or a user count. Settlement-verified means a paid route with an on-chain receipt. Examples are claimed listings. Imports marked Unclaimed (bazaar) can appear with that label and are not the examples. Payment is in USDC on Base, Solana or Algorand, with no API key. Listing an API is free and the provider keeps 100% of each settled call. If a page ever has fewer than ten settlement-verified matches, it drops out of the index and out of the sitemap until the catalogue grows back.

Use cases

Live matches

Networks

Integrations

Questions

How is a use case page different from a category?

A category page is every live listing in Data, Finance, Tools, Verification or Intelligence. A use case page is a tighter rule: that category, plus keywords or tags, so crypto market data is not the whole of Finance. The rule is in the page source and is tested.

How does an agent pay for an API on these pages?

It finds the listing for free, then pays the provider over x402 in USDC on Base, Solana or Algorand. No API key. The MCP tools search_apis, list_apis and get_api are read-only. submit_listing is free, rate limited, and it goes to pending review.

When is a page left out of search?

When fewer than ten matching listings are settlement-verified. The page stays up for people, with noindex, and it is left out of the sitemap. Ten or more verified matches puts it back. Unclaimed (bazaar) imports are not used as the lead examples either way.