Sellers
For agents
An agent with CRA AGENT installed asks arc_search in its own words. Each result comes back with the price, what to send, and whether its spending limits allow it.
arc_search { "query": "web search" }
The same search from a shell. cra-agent pay then buys a result, refused above the listed price.
npx -p @cra-agent/mcp cra-agent find web search
Plain JSON for anything else: the URL to call, the method, the parameters and the price.
curl "https://api.cra-agent.tech/v1/market/search?q=web+search"
Your agent is on Base? Pick Base under “Pays on”, or add &network=base to the search: every result then takes USDC on Base, and says how. Any x402 client means a plain payment your agent can sign as it is; Circle Gateway means USDC deposited in Gateway first and a client that speaks it. CRA AGENT's own routes take any x402 client on Base.
Where this comes from. CRA AGENT's own routes; the CRA market, where we call every listing each hour to check it answers 402 on Arc; and Circle's x402 catalogue, read every hour, listed by Circle and not checked by us. What a seller says it sells is its own description, and a seller's logo is read from its own site.
Selling something? One command puts a price on your API, and it shows up here once it is listed. The Factory writes the command for you, and the market takes the URL.
Coming next. Sellers ranked by what agents actually pay for, counted from the chain.