Docs

One endpoint, one key

The gateway fronts both the indexer and node RPC, so an application needs one base URL and one credential rather than two of each.

Base URL

https://retracer-api.arxium.network

Create a key on your account page. Every request carries Authorization: Bearer rk_…. A key is issued for one chain; using it on another is refused. Full schema is served by Retracer itself at /docs.

Routes

GET	/v1/chains	Chains this key may reach.
GET	/v1/chains/{chain}/status	Indexed height against node tip.
GET	/v1/chains/{chain}/blocks	Indexed blocks, paginated.
GET	/v1/chains/{chain}/accounts/{address}/actions	One account's action history.
GET	/v1/chains/{chain}/actions/stream	Server-sent-event tail from a height.
ANY	/rpc/{chain}/*	Passthrough to the chain's node RPC — live state and submits.

Limits

Requests are budgeted per key over a 10-second window. Over budget returns 429 with Retry-After and X-RateLimit-Limit / -Remaining / -Reset; waiting Retry-After seconds always restores the budget.
SSE tails count against a separate concurrent-connection cap, because a stream is not a request.
Webhooks are not self-serve yet — they need proof you own the address being watched.