Where you
touch the
chain.
HyperPax is the public infrastructure layer for Paxeer: RPC endpoints, the Paxscan block explorer, and indexed chain data APIs operated by the same team that runs the validators.
Three ways in.
Public RPC
Full standard Ethereum JSON-RPC endpoints for Paxeer, chain ID 125. Point a wallet, a deploy script, or a node client at them and go. Rate-limited fair-use during preview; dedicated endpoints for teams on request.
Paxscan explorer
Blocks, transactions, contracts, verified source. When an agent's receipt references a transaction, Paxscan is where anyone, not just the owner, can look it up.
Chain data APIs
Indexed data over the raw chain: transfers, holders, token metadata, market history. The same APIs that power Sidiora and Kindle, available to your application.
The infrastructure and its operators are the same people.
Run by the people who run the validators
HyperPax is operated by the same team that runs Paxeer's validator set. The RPC you call and the explorer you read sit next to the machines producing the blocks, not three vendors away.
When something looks wrong, there's no ticket relay between the infrastructure and the people who can fix it.
Boring on purpose
Infrastructure earns trust by being uneventful. We will not quote you an uptime number we have not earned over years. Paxeer is young, and we would rather show you the explorer than a badge.
What we will say: the endpoints are the ones we depend on ourselves. Every Centra agent transaction goes through this layer.
Honest limits during preview
Public endpoints are rate-limited for fair use. If your team needs guaranteed throughput, ask for a dedicated endpoint and we'll discuss the current options.
Public endpoints are fair-use during preview. Teams building on Paxeer can request dedicated RPC and data access. Tell us what you need.