# Public endpoints

Redacted's core contributors run a THORNode with public, read-only endpoints. Anyone can use them to read THORChain, whether to try out a node, to check what the app shows or to build something of your own.

| Endpoint | Address | What it serves |
| --- | --- | --- |
| RPC | [rpc.redacted.money](https://rpc.redacted.money/status) | The chain's RPC with status, blocks, block results and search over transactions and blocks |
| API | [api.redacted.money](https://api.redacted.money/thorchain/lastblock) | The THORNode API, including reads at a chosen block height with the `x-cosmos-block-height` header |

A few examples to open in your browser:

- [rpc.redacted.money/status](https://rpc.redacted.money/status) shows the latest block and whether the node is in sync.
- [api.redacted.money/thorchain/inbound_addresses](https://api.redacted.money/thorchain/inbound_addresses) lists THORChain's inbound addresses.
- [api.redacted.money/thorchain/pools](https://api.redacted.money/thorchain/pools) lists the pools.

## Good to know

Both endpoints are read-only and keep no access logs, so nobody can tell from them who looked up what. Each address can make up to 10 requests a second to the RPC and 20 a second to the API, with up to 10 connections open at a time, which is plenty for trying things out and for a node's own reads. The history starts at block 28,080,001 in early October 2026, so a search for older blocks comes back empty.

When you run a node, your own THORNode keeps every lookup on your own servers, and these endpoints are one of the sources you can choose alongside it (see [Running a Node](https://redacted.gg/docs/node-network/running-a-node.md)).

---

Page: https://redacted.gg/docs/node-network/public-endpoints/