Application name from /abci_info.
Application version from ABCI.
Last app block height from ABCI.
How to use this boundary
Start with the readable pages, then open raw endpoints only when you need exact JSON for tooling or debugging.
Use Status, Blocks, Ledger, Network, and Validators pages for quick checks without parsing raw responses.
Endpoint links expose public Core responses for tools, mirrors, and wallet compatibility checks.
Public clients should use https://core.uquad.org for readable pages and https://core.uquad.org/rpc for JSON-RPC tooling. Node-local listeners and operator paths are not public surfaces.
GET is the canonical public-read method for JSON health checks. HEAD is optional and a 405 response on gateway-backed JSON paths is not, by itself, an outage.
Public Core boundary
Live CometBFT reads, wallet REST/LCD, the Core-owned static index, relayer JSON-RPC, WebSocket events, and raw transaction broadcast are separately bounded. Website root JSON-RPC POST remains blocked.
/status, /health, /net_info, /block, /block_results, /validators, /abci_query, /abci_info, /tx, /genesis, /commit, and /blockchain.
/api is the Cosmos REST/LCD boundary for Keplr and compatible wallet tooling. Most custom Core module queries are not mapped to HTTP; use the observatory's /index/*.json feeds for browser-readable Core state.
/index/*.json is produced server-side from Core query surfaces and carries freshness, evidence class, and boundary labels. It is a projection, not a second authority.
/rpc, /rpc/status, and /rpc/websocket mirror the Bridgechain public RPC shape for JSON-RPC clients and relayer tooling.
/broadcast_tx_sync, /broadcast_tx_async, and /broadcast_tx_commit are open for raw Core transaction submission with gateway rate limits.
The node-local CometBFT RPC listener remains behind nginx. Public clients should use the listed gateway paths only.
ABCI endpoint response
Developer-surface JSON from /abci_info. It is public Core data, not a wallet or claim path.
Awaiting endpoint response
