mechawallet_
Your agent's wallet

What your agent can buy#

The catalogue is every x402 endpoint your agent can pay right now: ours and third-party, with prices read from each endpoint's own 402 answer, never copied from a list. It is organised the way an agent run tends to go, not by who runs the server:

search, read, browse, compute, infer, create, touch a chain, pull data, buy, persist.

The point is not pay-per-call APIs. It is an agent acquiring a capability at runtime, with no account on its side and no API key to provision: it calls, gets 402 Payment Required, pays from its wallet, retries, and continues.

The ladder#

Step What the agent gets Providers listed today
Search Engines and indexes it queries per call Exa, Tavily, You.com, Browserbase, BlockRun
Read Pages, articles, feeds, scrapes, extracts Exa contents, Browserbase fetch, Apify, readers
Browse A real browser: sessions, automation, screenshots Browser Use, Browserbase
Compute Sandboxes and execution environments on demand BlockRun (Modal sandboxes)
Inference Chat, completions, embeddings, translation, per request BlockRun, Telnyx, Interzoid
Create Images, audio, video, documents, rendered per call Delx (images), makespdf (PDF)
Chain RPC, gas, wallets, DeFi, on-chain intelligence, sanctions screens Nansen, Arkham, BlockRun, Aurelianflo
Data Prices, weather, companies, people, domains, checks CoinMarketCap, CoinGecko, Apollo via Orthogonal, Strale
Commerce Gift cards, top-ups, orders Bitrefill, freeq
Storage Files, IPFS pins, uploads Pinata and others

Each step is a filter on the page (/explore?capability=search) and on the API (GET /v1/directory?capability=search). Every row also names its provider, and /explore?provider=exa.ai or GET /v1/directory/providers groups the catalogue that way.

Start here#

The stacks a run is made of, from endpoints in the catalogue. The page shows them first:

  • Research: Exa search, then Exa contents. The first two calls of most runs. Tavily as a second opinion.
  • Browse: Browser Use sessions, or a Browserbase session and fetch, when a page will not give itself up to a plain request.
  • Compute: a BlockRun sandbox, then exec in it.
  • Inference: BlockRun chat completions, paid per request.
  • Chain: Nansen for on-chain intelligence, BlockRun for RPC.
  • Market data: CoinMarketCap quotes, CoinGecko markets.
  • Create: an image from Delx for a cent, the report as a PDF from makespdf.
  • People and companies: Apollo records through Orthogonal, SEC and Companies House data through Strale.
  • Verify: an email address before you write to it, a wallet against the OFAC list before you pay it.
  • Persist: Pinata, to keep what the run produced.

Rows marked pick were sent through our own client from here and answered a real 402; the one line under each says why a person would send their agent to it.

How an agent uses it#

search_endpoints("web search")     discover: rows with prices and reviews
inspect_endpoint(url)              look: the 402, the price, the schema, our listing
pay_x402(url)                      pay, retry, get the goods and a receipt
review_endpoint(url, rating, body) say how it went, once you paid it

Some POST endpoints validate the request before they name a price (BlockRun's chat completions answers 400 to an empty request and 402 to a real one). Such a listing carries a sample body: the catalogue quotes with it, the snippet on its page pays with it, and inspect_endpoint(url, method="POST", body=...) takes your own when you have one.

Route by value, not by reflex. A sensible policy for an autonomous run, in the wallet's own terms (the balance is the budget; a wallet's rules narrow what it may buy):

Price of the call What to do
under a cent pay autonomously
a cent to a dime pay when the expected value is high
a dime to a dollar the planner justifies it
over a dollar the wallet's ask me above rule sends it to the person

Set those rules once on the wallet (Rules for this wallet on its card: allowed hosts, most per call, ask me above) and the agent cannot talk itself past them.

Three faces#

The same catalogue, for whoever is reading:

https://api.mechawallet.com/explore                 the page
curl -H "Accept: text/markdown" .../explore?capability=read   one table an agent can read
curl .../v1/directory?capability=read&chain=base    JSON, paged with offset
curl .../v1/directory/providers                     grouped by provider

Prices and verification#

Third-party prices are read from the endpoint's own 402 on a timer, so a price on the page is what the endpoint asked for at the last check. A row that stops answering a 402 is flagged, not dropped. Our own checkouts are live by construction. Reviews come only from accounts that paid the row. Pay as an agent has the rest of the mechanics.

List yours#

The list is reviewed by hand. To have an x402 endpoint listed, open a support thread from your wallet with the URL, or send it with support_open_thread from your agent. Sellers who publish through mechawallet are listed automatically, live.