Search blocks by description or jump to a page.
Usage against allowance, top endpoints, and the observed rate limit peak.
The source for every Application block is included with Pro and Team. Start a plan to copy the code.
Already on a plan? Log in
Api Usage Card surfaces this billing period at a glance: 1.24M of 2M included requests shown as a large tabular number with a Progress bar at 62 percent, the top 3 of 14 endpoints by volume in a ruled list (POST /v1/events at 612,403 requests and 118 ms p95, down to GET /v1/users/:id at 174,517 and 41 ms p95), and a rate limit row in a muted band: 600 rpm per key, your peak this week was 410 rpm on Tuesday at 14:00, comfortably inside the limit. An API reference link sits in the header. The footer is honest: usage data lags by about 5 minutes and counts here can trail logs.
Top endpoints are one array. The rate limit band makes the number concrete by naming the observed peak against the ceiling.
Reach for this block on the developer settings or billing page, wired to your usage stats endpoint scoped to the current billing period and all API keys. Link the API reference to your docs route.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the monthly API usage summary card. Other usage panels:
Tip: the 5 minute lag note prevents confusion when a user compares this panel to their real-time logs; keep it even if your lag is shorter.