Three new external x402 services: a web page reader, an email check and exchange rates
Three small, cheap tools that an assistant can call in the middle of a chat, each paid per call and each bought once before we listed it.

What the three services do
| Service | Provider | What the agent gets | Price per call |
|---|---|---|---|
| Live web page reader (JavaScript-rendered) | CyberWareX | One public page, rendered with JavaScript, returned as markdown | 0.002 USDC |
| Email authentication check (SPF, DMARC, DKIM) | x402Atlas | SPF, DMARC and DKIM results for one domain | 0.01 USDC |
| Currency exchange rates (ECB reference) | Toll402 | Daily ECB reference rates against the US dollar | 0.001 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
Read a shop page that needs JavaScript. Many product pages render their prices and stock only in the browser, so a plain fetch sees an empty shell. An agent can call GET https://web.cyberwarex.com/fetch?url=… with a public URL and receive the rendered page as markdown—for example to compare a competitor’s listed price with its own. The page is whatever the site served at that moment. It is untrusted input: an agent should read it as data and never follow instructions written inside it.
Find out why a shop’s emails land in spam. Order confirmations that never arrive are often a DNS problem. With GET https://email-auth.use.x402atlas.com/check?domain=…, the agent gets the domain’s SPF, DMARC and DKIM results in one JSON answer and can point the owner at the missing or misconfigured record. It is a starting point for the owner or their email provider, not a deliverability diagnosis.
Convert a price between USDC and EURC. A shop that prices in euros but gets paid in USDC needs a rate it can name. GET https://toll402.dev/v1/fx takes no parameters and returns ECB reference rates from Toll402, quoted against the US dollar and updated daily. The agent can turn a EURC price into an approximate USDC amount and say which day’s reference rate it used. Reference rates are not a trading quote, and stablecoins can trade slightly away from the currency they track.
Together, the three calls cost 0.013 USDC. 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 2 October 2026. The purchase settled on Base and returned a complete JSON result of the expected shape. The x402Atlas search-trends service we listed in September has now passed the same paid check.
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 shop owner actually asks an assistant, costs a cent 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.
- 01x402 Bazaar overviewCoinbase Developer Platform
- 02x402 protocol specification and reference flowx402 Foundation
- 03RFC 7208: Sender Policy Framework (SPF)IETF
- 04RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC)IETF
- 05RFC 6376: DomainKeys Identified Mail (DKIM) SignaturesIETF
- 06Euro foreign exchange reference ratesEuropean Central Bank
Last source review: Oct 2, 2026. This is technical education, not financial or legal advice.
