Get usage data
Returns customer-scoped usage aggregates. Supports filtering by time range, chain, API key, grouping, and granularity. By default returns summary and balance.
Authorizations
Management API key from the RouteMesh dashboard. Required for customer API endpoints (/api-keys, /usage). Each request also carries the customer's RPC API key in the URL path for the RPC endpoint.
Query Parameters
Start time (RFC3339). Defaults to 30 days ago.
End time (RFC3339). Defaults to now.
Comma-separated list of sections to include. Options: summary, balance, by_chain, by_api_key, by_api_key_chain, top_methods, time_series, by_scenario. Default: summary,balance.
"summary,balance,by_chain,by_api_key"
Group usage by a dimension. Options: chain, api_key, api_key,chain, method, day.
"chain"
Time bucket size. Options: day, hour. Default: day.
day, hour Filter by chain ID (e.g. 1, 137, 8453).
Filter by API key numeric ID (found in list response).
Maximum number of rows returned (default and max depend on config).
x >= 1Response
Usage data
Aggregate credits and request count.
Current credit balance.
Per-chain breakdown.
Per-API-key breakdown.
Per-API-key, per-chain breakdown.
Top RPC methods by spend.
Time-bucketed usage data.
Usage by routing outcome scenario.
Grouped results when group_by is specified.

