xrplme.online is a data service for AI agents. It covers 30 countries — economic and regulatory data — and it runs on the XRP Ledger.
The part that matters is how an agent pays. It reads a public manifest, picks the country it needs, and settles a single query in XRP over x402. No API keys, no accounts, no billing setup — the things that usually keep an agent from using a data source at all.
Two tiers, priced per call. A standard query costs 0.1 XRP. An AI-enhanced query — where the source material is parsed and summarised for a machine to read — costs 0.5 XRP. Everything settles in XRP on XRPL mainnet; RLUSD isn’t supported.
Discovery starts at the manifest: /.well-known/xrplme.json. It lists the
platform, all 30 countries, current pricing, and the endpoint shape for each country. An agent
reads it once and can drive everything else from it — no documentation pass required.
The MCP server runs at https://api.xrplme.online/mcp over Streamable HTTP. The
current tool set:
xrplme_list_countries — the 30-country list (free)xrplme_get_country_status — live health probe for one country (free)xrplme_get_pricing — current tiers (free)xrplme_get_country_schema — field schema for a country (0.1 XRP)xrplme_get_country_data — latest data plus freshness (0.5 XRP)xrplme_regional_research — a preview, feature-flagged and limited to a few
countries. Not a production tool yet.Same data, plain HTTP. A paid route like /wc/v1/<country>/bot answers with
HTTP 402 and the payment terms if you haven’t paid. Settle in XRP, retry, and the data
comes back. Thailand was the first country wired this way; the pattern now covers all 30.
There’s a blog index at /blog/ and an RSS 2.0 feed at
/blog/feed.xml, if you’d rather follow along that way.
The MCP connector is live on Glama.ai. Submissions are in with MCP Market and mcpservers.org, and a merchant listing was requested with the XRPL AI Hub / x402 directory. Those queues run in weeks, so treat them as pending — not done.
Plan a trip to Thailand. Before anything is booked, an agent pulls the regulatory and cost context — entry requirements, tourism statistics, local cost indicators. A few tenths of an XRP beats scraping pages and guessing at numbers.
Compare macro indicators. A research agent walks the country list, pulls the same field from each country, and builds the comparison from one source. Because every country’s schema is discoverable, the agent knows what it’s buying before it pays.
Check compliance first. A compliance agent verifying local rules before a cross-border move queries the jurisdiction first, and keeps the response as a timestamped record of what the rule said that day. Small payment for a check that’s otherwise manual and easy to get wrong.
Where this goes next is mostly about removing friction: making it easier for agents to pay from existing wallets, adding more examples and reference implementations so the flow is obvious rather than inferred, and exploring partnerships and directories. None of it is a commitment or a schedule — everything described above is what exists today, and anything that changes will show up here first.
Found a bug, or need a country that isn’t covered? Open an issue on GitHub.