Talero node software defines REST routes for controlled deployments, but the public RPC domain currently publishes only JSON-RPC at /rpc.
Do not construct URLs from the source catalog. A route classified as public-capable still needs an operator to publish it.
| Layer | What it says | What it does not say |
|---|---|---|
| Node route catalog | Routes implemented by the node and their policy classes | That every route is internet-accessible |
| Access profile | Routes a configured role may be permitted to use | That a particular host publishes that profile |
| Reverse proxy | The paths actually exposed by a deployment | That other software routes share the same host |
https://rpc.talero.info/rpc accepts JSON-RPC POST requests. The same host returns 404 for node REST probes such as /health, /ready and /api/v1/head. There is therefore no public node REST base URL to integrate against at this time.
If Talero publishes a node REST deployment later, its base URL, authentication, quotas and supported route subset must be announced as a separate contract.
The Explorer exposes a distinct read API under https://explorer.talero.info/api. Representative routes include /blocks, /txs, /address/:address, /search, /validators, /checkpoint/latest, /network/health and /metrics.
Those routes belong to the Explorer indexer and may have privacy, freshness, pagination and degraded-state semantics that differ from direct node reads.
The full node REST catalog remains useful as an operator-side contract. Publish only an explicitly reviewed subset behind authentication, request limits and monitoring. Do not reuse internal readiness, diagnostics or administration routes as a general public API.
