Best RPC and data APIs for Xahau (2026)

Documentation based guide: compiled from each maker's own docs on Oct 20, 2026. We have not load-tested these endpoints, and the guide contains no code we ran.

For most Xahau projects, the answer is short: build against the free public nodes the Xahau docs list (wss://xahau.network for Mainnet, wss://xahau-test.net for Testnet), use the Bithomp API when you need indexed data such as account history, NFTs or token lists, and run your own xahaud node once you go to production. Unlike the XRP Ledger, Xahau has no big managed RPC market yet: none of the four large multichain providers we checked names Xahau on its network list.

This guide goes deeper than our Xahau developer tools page: what each option gives you, the limits the makers publish, and the gotchas that trip up XRPL developers moving to Xahau. It is a summary of what each maker says, not a ranking.

Contents

• Quick answer
• Are there managed RPC providers for Xahau?
• Xahau public nodes
• Xahau Data API
• Bithomp API (via Xahau Explorer)
• Running your own xahaud node
• Tools that sit on top of the RPC
• How to choose

Quick answer

Are there managed RPC providers for Xahau?

Not among the big ones. On Oct 20, 2026 we searched the network lists of QuickNode, Chainstack, GetBlock and NOWNodes. All four name the XRP Ledger, and none names Xahau. Xahau is a separate network with its own network IDs, so an XRPL endpoint from one of these providers will not serve Xahau.

If you came here from our XRP Ledger RPC guide, this is the main difference: on Xahau, the free public nodes and your own node are the realistic choices, with Bithomp covering the indexed-data side.

Xahau public nodes

The Xahau docs list free public endpoints for three networks (Source: Xahau public nodes):

• Mainnet (network ID 21337): wss://xahau.network and https://xahau.network, plus xahau.org as an alias for both. The docs note the alias exists because "some ad-blockers block .network", which is worth knowing if your app calls the endpoint from a browser.
• Testnet (21338): wss://xahau-test.net and https://xahau-test.net.
• JSHooks Testnet (31338): wss://jshooks.xahau-test.net and https://jshooks.xahau-test.net, for Hooks written in JavaScript.

Trade-offs. The page names no operator and states no rate limits, history depth or uptime commitment. That is fine for development and light reads. For a production app, treat a public node as shared infrastructure you don't control: add a fallback (the .org alias, or your own node) and handle disconnects. The same docs page lists the Testnet faucet and explorers (Source: Xahau faucet and explorers); there is no Mainnet faucet.

Gotcha: NetworkID. Xahau transactions must carry a NetworkID field. The transaction reference says the field is required on networks with an ID of 1025 or higher, which includes Xahau Mainnet (21337) and Xahau Testnet (21338), and must be omitted on XRPL Mainnet (Source: Xahau transaction common fields). If you reuse XRPL code and transactions fail on Xahau, check this first.

Xahau Data API

The Xahau docs list a Data API at data.xahau.network as the primary data API (Source: Xahau data APIs). The current version "offers live Xahau DEX (IOU trades) and ledger info data", and its navigation shows endpoints for DEX rates, trades, volume and tickers, plus XAH supply and ledger-index-to-time conversions (Source: Xahau Data API).

Trade-offs. No API key or numeric rate limit is documented. Each response carries headers with the limit, the requests remaining and the reset time, so read those rather than guessing. Responses use a wildcard CORS policy, so browser apps can call it directly. Pagination uses an `x-has-more-data` header and a `skip` parameter. It is not a general account or transaction history API; for that, look at Bithomp or your own node.

Bithomp API (via Xahau Explorer)

Bithomp API is the indexed-data option. Its docs list a separate base URL per network, including Xahau Mainnet at xahauexplorer.com/api/v2/ and Xahau Testnet at test.xahauexplorer.com/api/v2/, each with its own API key (Source: Bithomp API docs). Its endpoints cover addresses, NFTs, transactions, tokens and more, and its changelog includes Xahau-specific additions such as URI Token remarks.

Pricing and limits (all from the same docs page):

• Test networks: "Bithomp API is FREE on the test networks."
• Mainnet free tier: non-commercial use only, 10 requests per minute and 2,000 per day.
• Paid tiers: Basic is 30 EUR/month for 100 requests per minute and 30,000 per day; Standard is 100 EUR/month (400/min, 120,000/day). Prices are in euros.
• On-demand: pay per request instead of a subscription; the Basic on-demand rate is listed as 0.003 XAH per request on Xahau.
• Some endpoints (historical rates, for example) are available only on Standard and higher.

Trade-offs. The free mainnet tier rules out commercial apps, so budget for a paid tier before launch. It is a third-party indexer, not a raw node, so use it for lookups and history, and a node for submitting transactions and live subscriptions.

Running your own xahaud node

The Xahau docs describe two install paths for a Mainnet node: a Docker setup (the `mainnet-docker` repository with `build` and `up` scripts) and a binary build for Ubuntu 22.04 run with a `xahaud.cfg` config file. Once running, the node serves WebSocket on port 16006 and HTTP RPC on 16007 locally, and peers on network ID 21337 (Source: running a Mainnet node).

The interaction guide explains how ports are opened in the `[server]` section of `xahaud.cfg`, how to restrict admin requests to specific IPs, how to cap clients per port with `limit`, and how to enable TLS. It also documents UDP RPC on port 16008 for read-only queries, and says transaction submission should use WebSocket or HTTP RPC (Source: interacting with xahaud).

Trade-offs. The setup page does not state hardware requirements or how to configure history depth, so size the server from your own testing. You also take on uptime, upgrades and amendment changes yourself. In return you get no third-party rate limits and full control over who can call admin methods.

Tools that sit on top of the RPC

These are not RPC providers, but most Xahau builders will pair one with the endpoints above:

• xahau.js: the Xahau GitHub organization's fork of the xrpl.js client library (Source: xahau.js repo). Its README is still the xrpl.js text, so point it at a Xahau endpoint yourself.
• Hooks Toolkit: its getting-started example generates testnet accounts and sets the WebSocket to wss://jshooks.xahau-test.net (Source: Hooks Toolkit docs). Testnet example only in the docs we checked.
• xahau-mcp: an MCP server that lets AI agents read Xahau ledger state and simulate Hooks. Its README says it is read-only toward the network, has no submit or sign function, and its transaction builders default to testnet (Source: xahau-mcp README).
• Evernode SDK: Evernode is a hosting network whose host registry is a Hook on Xahau (Source: Evernode). If you are building an Evernode app, you will still read Xahau through one of the options above.

How to choose

• Prototyping or a hackathon: Testnet public nodes plus the Testnet faucet. Use the JSHooks Testnet if you write Hooks in JavaScript.
• Reading balances and submitting transactions in production: public Mainnet node with the xahau.org alias as fallback, then your own xahaud node once traffic matters.
• Account history, NFTs (URI Tokens) or token lists: Bithomp API; check that your use is non-commercial before relying on the free tier.
• DEX prices or XAH supply data: Xahau Data API, reading its rate-limit headers.
• Porting XRPL code: add NetworkID to every transaction and change every endpoint; XRPL providers do not serve Xahau.
• Before you commit: confirm limits on each maker's page. They change, and the public nodes publish none.

For every Xahau tool we list, with the chain evidence for each, see Xahau developer tools.