API Key Usage

See what your Talus API key has been doing — request counts, error rate, and rate-limit pressure.

Paste your key below to see its own usage. The key is sent from your browser straight to the API and is never stored by this page, and the API only ever returns usage for the key that authenticated the request — one key cannot read another's.

Counters are hourly rollups written by a background flusher, so a call made moments ago may take up to a minute to appear.

Your usage#

Network The key works on the network that issues it. Your API key Sent straight from your browser to the API and never stored by this page. The response only ever covers the key you paste.

Group by Window

Reading the numbers#

Errors counts everything that was not a success, including 403 (calling an endpoint your key lacks the scope for) and 429 (rate limited).
Rate limited is broken out separately because it is the one number that tells you to slow down or ask for a wider limit, rather than to fix your request.
Avg ms is the mean server-side duration. Rollups store a sum and a count, so percentiles are not recoverable from this view.

Doing this yourself#

The page is a thin wrapper over one endpoint:

curl -H "x-api-key: $TALUS_API_KEY" \
  "$TALUS_API_URL/tokens/usage?granularity=day&group_by=route"

granularity is hour, day or total; group_by is scope or route. from and to take RFC 3339 timestamps and default to the last seven days. The same key is valid on testnet and mainnet, so pick the base URL for the network whose usage you want to see.