Arxium

Endpoints and API keys

Where to send requests, and how to get the key they need.

The devnet is reached through one gateway with one key. The chain id is corechain-devnet.

Node RPC
https://retracer-api.arxium.network/rpc/corechain-devnet
API key
Indexer (Retracer REST)
https://retracer-api.arxium.network/v1/chains/corechain-devnet/…
API key, read-only
API keys and docs
retracer.arxium.network
GitHub sign-in
Console (signing key, faucet)
console.arxium.network
Sign-in
Browser verifier
arxium.network/verify
Open, runs locally
Gateway health
https://retracer-api.arxium.network/health
Open

Get an API key

Sign in at retracer.arxium.network with GitHub and create a key for corechain-devnet. The key starts with rk_ and is shown only once, so copy it when it appears. Send it as Authorization: Bearer rk_…. The same key works for the node RPC and the indexer.

  • Free keys allow 10 requests per second and one open event stream.
  • Over the limit you get 429 with Retry-After and X-RateLimit-* headers. Wait the number of seconds in Retry-After, which is at most 10, then retry.
  • Send a User-Agent that names your app. Some library defaults (Python's urllib, for one) are blocked at the edge with error code: 1010 before your key is ever checked.
  • The indexer is read-only. Writes, meaning signed actions, go to the node RPC.