All articles
Agent services4 min read

Three new external x402 services: hotel search, a company registry search and a VIN decode

Three more small, pay-per-call tools an assistant can use while it plans a trip, checks a supplier or looks at a used car, each bought once before we listed it.

By GenesisPay Engineering Published Oct 16, 2026
A bright fintech directory showing service cards, payment-offer check marks and a separate external-services section.

What the three services do

ServiceProviderWhat the agent getsPrice per call
Hotel search by destinationx402AtlasOne page of hotels for a destination, with nightly rates, ratings, amenities and coordinates0.05 USDC
Company registry search (UK Companies House)CelerAPIRanked candidate companies for a name, with company number, status and registered address0.005 USDC
VIN decode with factory warranty termsVindexMake, model, year, engine and body for one VIN, plus the manufacturer's original warranty terms0.01 USDC

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

Shortlist hotels for a trip. An assistant that is planning travel can call GET https://hotels.use.x402atlas.com/search?query=… with a destination such as “hotels in Vienna” and receive one page of properties: name, star class, guest rating and review count, the nightly and total rate for the provider's default two-night window, amenities and coordinates. The curated request takes only the destination; dates, currency and paging stay at the provider's defaults. The rates are x402Atlas's snapshot at the time of the call, not a booking quote, and the answer is about 160 KB of JSON, so the agent should summarise rather than paste it.

Check who a supplier legally is. Before a shop pays a new UK supplier, an agent can call GET https://www.celerapi.com/v1/company/search?q=… with the business name and get ranked candidates from the Companies House public register: legal name, company number, status, company type, incorporation date and registered office address, each marked with its source authority. CelerAPI describes the result as public-register evidence, not a KYC or KYB determination, and the agent should say the same. GenesisPay already lists a UK company search from ukintel; this one adds entity identifiers that CelerAPI's other endpoints build on and also covers Norway, though the curated request uses the provider's default country.

Decode a used car's VIN. A buyer who pastes a 17-character VIN into a chat can have the agent call GET https://api.vindexapi.dev/v1/decode?vin=…. Vindex returns the normalised decode from the public NHTSA vPIC database—make, model, year, engine, body class, drive type and plant—together with the manufacturer's original new-vehicle warranty terms for that make and model year (basic, powertrain, corrosion, roadside and EV battery). The provider is explicit that this is informational data, not a vehicle-history report: it carries no liens, accidents, odometer readings or remaining coverage.

Together, the three calls cost 0.065 USDC before GenesisPay's buyer fee. Each is a separate signed payment to a different provider, 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 16 October 2026. Each purchase settled on Base and returned a complete JSON result of the expected shape: a hotel page for Vienna, the register candidates for a well-known bank's name, and the decode of the provider's own sample vehicle.

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

Each answers a question a traveller, a shop owner or a car buyer actually asks an assistant, costs a few cents or less per call, and returns one JSON answer an agent can use straight away. 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. 03Hotel Search, Rates & Reviews: OpenAPI descriptionx402Atlas
  4. 04CelerAPI Machine Resource API: OpenAPI descriptionCelerAPI
  5. 05Companies House public registerCompanies House (UK)
  6. 06Vindex API: OpenAPI descriptionVindex
  7. 07vPIC: Vehicle Identification Number decodingNational Highway Traffic Safety Administration (US)

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