For agent developers

Let your agent buy the data itself

725 datasets. 14.2 million US and Canadian business locations — manufacturer dealer networks, state-licensed trade contractors, retail and restaurant chains, healthcare practices, and firms drawn from federal credential registries. Every one is compiled from the official locator, license register or government file that publishes it, and refreshed on a schedule. Your agent can query any of them and pay per row in USDC — no card, no account, no human at the keyboard.

Claude Desktop: install the extension

Claude holds no keys and cannot sign a payment, so the wallet lives in a tool it calls. Download the extension, double-click it, and give it a funded Base wallet plus two spending caps. Then just ask Claude a question about where businesses are.

Download the extension

MIT licensed · source on GitHub

How the payment works

Your agent asks for data it does not have

It calls query_locations on our MCP server at locationlists.com/mcp. No key, no signup, nothing to register first.

We answer HTTP 402 with the price

The response carries x402 payment terms: the amount in USDC, the network, and the address to pay. Priced per row from the dataset, so a county-sized query is cents.

Your agent signs and retries

It signs an EIP-3009 authorization and repeats the call with an X-PAYMENT header. Gasless — the facilitator broadcasts and pays the gas, so your wallet needs USDC and nothing else.

We settle, then serve

Money moves only after the query succeeds. A failed call, or one that matches nothing, costs you nothing — the authorization is simply never settled.

Any MCP client

The server is plain MCP over HTTP. Point any client at it and read the 402:

POST https://locationlists.com/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call",
 "params":{"name":"query_locations",
           "arguments":{"dataset":"generac-dealers","state":"CO","limit":20}}}

The free tools — search_datasets, get_dataset, get_sample — need no payment at all, so an agent can decide whether a dataset is worth buying before it spends anything.

When this beats gathering it yourself

An agent with a browser can read a brand’s dealer locator, and for who is near me it should. A locator returns what is close to one point, capped per search. Three kinds of question that breaks:

Coverage and gaps. “Where is coverage thin” depends on the complete set. A partial sweep does not just take longer — it returns a wrong answer, because every location you missed looks like a gap that isn’t there.
National scale. One brand can be thousands of locations across every state. That is hundreds of capped queries, or one call here.
Comparing brands. No single locator can show you two networks at once. These datasets share one schema.

For anything smaller than that, honestly, read the locator. We would rather you bought the right thing than the expensive thing.

Buying the whole file

Metered queries are for slices. If you want an entire dataset, that is a one-time purchase from $9 to $199 by record count, delivered as a CSV — and per row it is far cheaper than querying. Datasets under 5,000 records are only sold whole; the query tool will tell your agent so and hand back the link.