Three new external x402 services: App Store search, UK company search and Steam catalog search

What the three services do

All three appear under “Selected external services” on /explore, and agents find them through the MCP tools genesispay_discover_external and genesispay_describe_external_service. They are not GenesisPay merchants. The directory shows each one as an external x402 service from an independent provider, with its sources and the date of its paid check.

Three small jobs in one chat

Compare apps before recommending one. Asked for a good weather or budgeting app, an assistant can call GET https://appstore.use.x402atlas.com/search?term=… and get the first ten App Store results as JSON: who publishes each app, what it costs, how it is rated and how large it is. It can then answer with real listings instead of names it half remembers. Ratings and prices are the store’s at the time of the call and can change the next day.

Check a British company before paying it. GET https://api.ukintel.uk/v1/company/search?q=… returns up to five companies from the public Companies House register that match a name, with the company number, whether it is active or dissolved, and when it was incorporated. A shop that is asked to pay a new UK supplier can see at once whether a company of that name exists and is still active. A match on the register says that a company exists; it says nothing about whether the person you are dealing with acts for it.

Price a game before buying it. GET https://dataforagents.net/v1/steam/search?q=… returns the Steam games that match a name, with the developer, the current price in US dollars and the genres. An assistant can tell its owner what a game costs today, or find the base game among its soundtracks and demos. Prices change with every Steam sale, and some fields can be empty for smaller titles.

Together, the three calls cost 0.035 USDC. Each is a separate signed payment, and each passes through the owner’s spending policy—by default 5 USDC per payment and 20 USDC per day. Nothing is prepaid, and the assistant can stop after any step.

What “purchase-tested” means

Before listing each service we checked its payment offer, recorded the provider’s payment address and price, and then bought one call with a synthetic example request on 10 October 2026. Each purchase was paid on Base and returned a complete JSON result of the expected shape.

One paid check establishes that, on that day, the endpoint accepted a payment and delivered a result. It does not establish:

• the accuracy or completeness of what a later call returns;
• that every paid request will be delivered;
• that the price or the provider will stay the same.

When an agent buys, GenesisPay reads the live payment offer again and refuses it if the address or price no longer matches what we recorded—before anything is signed. The owner’s agent wallet then pays the provider directly; GenesisPay does not hold the money at any point. The JSON result stays retrievable for seven days through genesispay_result, so a lost chat message never means paying twice.

Why these three

Agents that shop and research for their owners keep asking the same small questions: which app, which company, what does it cost. These three answer one each, with one search term and one payment. We still add external services a few at a time, and each one is bought once before it is listed. How we check them is described in our first post on external x402 services.

Primary sources

Check the original sources.

1. 01x402 Bazaar overviewCoinbase Developer Platform
2. 02x402 protocol specification and reference flowx402 Foundation
3. 03ukintel.uk OpenAPI descriptionukintel
4. 04DataForAgents OpenAPI descriptionDataForAgents

Last source review: Oct 10, 2026. This is technical education, not financial or legal advice.