The XRP Ledger has no company you must sign up with to get an RPC endpoint. A handful of public servers answer JSON-RPC over HTTPS and WebSocket for free, with no API key. Below are their URLs, all of which answered in November 2026, then four calls: read a Mainnet account, follow new ledgers live, get a funded Testnet account, and the same read through a relay with full history.

The calls need curl and jq. The WebSocket example needs Node.js 22 or newer.

The URLs

Mainnet

Run by JSON-RPC WebSocket
Ripple https://s1.ripple.com:51234/ wss://s1.ripple.com/
Ripple https://s2.ripple.com:51234/ wss://s2.ripple.com/
InFTF https://xrplcluster.com/ wss://xrplcluster.com/
Honeycluster https://honeycluster.io/ wss://honeycluster.io/
xrpl.stream https://s1.xrpl.stream/ wss://s1.xrpl.stream/
xrpl.to https://api.xrpl.to/v1/rpc (read commands)

Every Mainnet URL above returns the full history, from ledger 32,570 (1 January 2013) on. xrpl.ws is another name for xrplcluster.com.

xrpl.stream, from the team behind xrpl.to, answers without a key at up to 5 requests a second and 1 million credits a month; a free key raises that to 15 a second (plans, docs). It also takes submit, so one URL covers reading and sending transactions.

Testnet

Testnet works like Mainnet, but its XRP is free and has no value.

Run by JSON-RPC WebSocket
Ripple https://s.altnet.rippletest.net:51234/ wss://s.altnet.rippletest.net:51233/
Ripple (Clio) https://clio.altnet.rippletest.net:51234/ wss://clio.altnet.rippletest.net:51233/
XRPL Labs https://testnet.xrpl-labs.com/ wss://testnet.xrpl-labs.com/
Honeycluster https://testnet.honeycluster.io/ wss://testnet.honeycluster.io/
xrpl.stream https://s1.xrpl.stream/testnet wss://s1.xrpl.stream/testnet
xrpl.to https://api.xrpl.to/v1/testnet/rpc (read commands)

Devnet

Devnet is where the XRPL docs say "unstable changes to the core XRP Ledger software may be tested out" before they reach Mainnet.

Run by JSON-RPC WebSocket
Ripple https://s.devnet.rippletest.net:51234/ wss://s.devnet.rippletest.net:51233/
Ripple (Clio) https://clio.devnet.rippletest.net:51234/ wss://clio.devnet.rippletest.net:51233/

devnet.honeycluster.io is listed too, but in November 2026 it answered amendmentBlocked ("Amendment blocked, need upgrade."): it runs an older server version than Devnet needs, so it cannot follow the current ledger.

The rows marked Clio are Clio servers: "an XRP Ledger API server optimized for WebSocket or HTTP API calls for validated ledger data". They answer the same requests.

The list follows the public servers page of the XRPL docs, which also lists paid providers. Ripple writes there that its public servers "are not for sustained or business use, and they may become unavailable at any time". An app with real traffic should run its own server or pay a provider.

1. Read an account on Mainnet

A JSON-RPC call is a POST. The command goes in method, and its fields go in params: a list that holds one object (request format).

Request

curl -s https://s1.ripple.com:51234/ \ -H 'Content-Type: application/json' \ -d '{"method":"account_info","params":[{"account":"rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh","ledger_index":"validated"}]}' \ | jq '.result | {account: .account_data.Account, balance: .account_data.Balance, sequence: .account_data.Sequence, ledger_index, validated}' 

Response

{ "account": "rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh", "balance": "56786636999", "sequence": 44196, "ledger_index": 108484818, "validated": true } 
  • rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh is the genesis account, the first account on the ledger.
  • balance is in drops. 1 XRP is 1,000,000 drops, so this account holds 56,786.636999 XRP.
  • "ledger_index": "validated" asks for the last ledger the network has confirmed. Without it, account_info reads the open ledger, which can still change.

2. Follow new ledgers over WebSocket

A WebSocket stays open, so the server can send you each new ledger as it closes. This script subscribes to the ledger stream and stops after three ledgers. Save it as ledgers.mjs and run node ledgers.mjs.

Request

const ws = new WebSocket('wss://xrplcluster.com/'); let seen = 0; ws.onopen = () => ws.send(JSON.stringify({ id: 1, command: 'subscribe', streams: ['ledger'] })); ws.onmessage = (e) => { const m = JSON.parse(e.data); if (m.type !== 'ledgerClosed') return; // ledger_time counts seconds from 1 January 2000 const closed = new Date((m.ledger_time + 946684800) * 1000).toISOString(); console.log(m.ledger_index, closed, m.txn_count, 'transactions'); if (++seen === 3) ws.close(); }; 

Response

108484825 2026-11-21T23:09:02.000Z 55 transactions 108484826 2026-11-21T23:09:10.000Z 46 transactions 108484827 2026-11-21T23:09:11.000Z 57 transactions 

The XRP Ledger counts time in seconds from 1 January 2000, not from 1970. That is why the script adds 946,684,800 seconds before turning ledger_time into a date. The same subscribe command also takes streams: ['transactions'] for every confirmed transaction, or accounts: ['r…'] for the transactions of chosen accounts.

3. Get a funded Testnet account

Ripple's Testnet faucet creates a new account and sends it 100 Testnet XRP.

Payload

curl -s -X POST https://faucet.altnet.rippletest.net/accounts | jq 

Response (seed shortened here)

{ "account": { "xAddress": "XVjkFDGvG14oqbKdU7hLWD2nXZ679boZyTJw3s5Q2oF7qpE", "address": "rPmqMLvS5Qku9oZVnroU8RPvATh6MZpxk1", "classicAddress": "rPmqMLvS5Qku9oZVnroU8RPvATh6MZpxk1" }, "amount": 100, "transactionHash": "CAED0D286A620710AB95C7B682183DF2D6A096F10869DBD695776258C6E90374", "seed": "sEdT…" } 

seed is the account's secret key: anyone who has it controls the account. Keep it out of code you share, even on Testnet.

Already have a Testnet address? The xrpl.to faucet sends 589 Testnet XRP to it, once a day per address.

Payload

curl -s -X POST https://api.xrpl.to/v1/faucet \ -H 'Content-Type: application/json' \ -d '{"destination":"rPmqMLvS5Qku9oZVnroU8RPvATh6MZpxk1"}' | jq 

Response

{ "success": true, "attribution": "Required: display a visible link to https://xrpl.to on any surface showing this data — <a href=\"https://xrpl.to\">Data by xrpl.to</a>. Terms: https://xrpl.to/docs", "hash": "C66858281F133C2094383EEE066947D40D58023438446763BE72B491A7B4BDF1", "destination": "rPmqMLvS5Qku9oZVnroU8RPvATh6MZpxk1", "amount": 589, "cooldownHours": 24 } 

Then read the balance from a Testnet server:

Request

curl -s https://s.altnet.rippletest.net:51234/ \ -H 'Content-Type: application/json' \ -d '{"method":"account_info","params":[{"account":"rPmqMLvS5Qku9oZVnroU8RPvATh6MZpxk1","ledger_index":"validated"}]}' \ | jq '.result.account_data | {Account, Balance, Sequence}' 

Response

{ "Account": "rPmqMLvS5Qku9oZVnroU8RPvATh6MZpxk1", "Balance": "689000000", "Sequence": 22509845 } 

689 XRP: 100 from the first faucet and 589 from the second. A new account's Sequence starts at the number of the ledger that created it (rippled source). More faucets are listed in the docs, Devnet's among them.

4. The same read through a relay

https://api.xrpl.to/v1/rpc passes the ledger's read commands on to Mainnet servers, and sends history commands such as account_tx to full-history servers. Two things differ from calling a server directly: params is one object, not a list, and the answer comes back inside result, next to success and took (milliseconds).

Request

curl -s https://api.xrpl.to/v1/rpc \ -H 'Content-Type: application/json' \ -d '{"method":"account_info","params":{"account":"rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh","ledger_index":"validated"}}' \ | jq '{success, method, took, balance: .result.account_data.Balance, ledger_index: .result.ledger_index}' 

Response

{ "success": true, "method": "account_info", "took": 1, "balance": "56786636999", "ledger_index": 108484833 } 

It passes on reads only: a submit is refused with the list of commands it does pass on. Signed transactions go to POST https://api.xrpl.to/v1/submit with {"tx_blob": "…"}. https://api.xrpl.to/v1/testnet/rpc is the Testnet twin, and xrpl.to/testnet runs these calls in the browser.

If you show data from api.xrpl.to in an app, put <a href="https://xrpl.to">Data by xrpl.to</a> on the same screen. The full reference is at xrpl.to/docs.

Which one to use

  • Calls from a web page: the browser blocks a call to a server that does not allow other sites. Of the servers above, xrplcluster.com, testnet.xrpl-labs.com, s1.xrpl.stream and api.xrpl.to allow it (they send Access-Control-Allow-Origin: *). The others did not send that header in November 2026.
  • Old transactions: every Mainnet server above has the full history.
  • Heavy use: a busy public server answers slowDown, "You are placing too much load on the server." (rippled source). Space your calls out, use a key on a service with higher limits such as xrpl.stream, or run your own server.