> ## Documentation Index
> Fetch the complete documentation index at: https://docs.remapdb.com/llms.txt
> Use this file to discover all available pages before exploring further.

# API usage and monitoring

> Monitor API requests, HTTP errors and response times across your named keys.

Open **API → API Keys & Usage → [Usage](https://app.remapdb.com/api/usage)** to see activity for your account. Viewing this page does not consume API requests or lookup credits.

## Filter your activity

Choose the last 24 hours, 7 days, 30 days or 90 days. Choose **All keys** or one named key, including revoked keys. Click **Refresh** for current results. Times use the timezone saved in your account settings, including daylight-saving changes. If no valid timezone is saved, the page uses your browser’s timezone. Chart labels show the start of each interval; the first and last intervals may be partial.

The page shows:

* **Requests:** completed, recorded HTTP requests in the selected period.
* **HTTP error rate:** the percentage returning a 4xx or 5xx status.
* **Average response time:** mean API response time, in milliseconds, for requests with recorded timing.
* **Rate limited (429):** HTTP 429 responses. Legacy v1 may return 401 for rate limits, so those are included in HTTP errors instead.
* **Requests and errors:** total requests alongside client errors (4xx) and server errors (5xx).
* **Response time:** average response time for each hourly or daily interval. Intervals without measurements have no latency point.
* **Most used endpoints:** the top 20 endpoint/method combinations, including MCP operation names.
* **Recent requests:** the latest 50 requests, with time, key name, endpoint, status and duration.

Request IDs and path values are replaced by placeholders. Credential values, query strings, request bodies, firmware and registration numbers are not displayed.

## Understand what the charts measure

These charts cover requests handled by the API. Proxy or network failures before a request reaches the API are not included. These are HTTP activity charts, not a billing ledger. A request may use no lookup credits, and a cached response still counts as an HTTP request. All keys share the same subscription allowances.

An ECU submission returning HTTP 202 means the job was accepted. Its eventual result and processing duration belong to the job endpoints; background work does not appear as another API request. Likewise, an MCP tool can report a tool error within HTTP 200, which is not counted as an HTTP error here.

## Key changes and history

Renaming a key updates its label in the dashboard. Rotating it keeps its recorded activity under the same key name. Revoked keys remain selectable for historical activity. Requests using an unknown or already-rotated token cannot always be attributed and are excluded from your dashboard.

Some older activity may be unavailable. The dashboard only shows requests associated with your account.

## Retention

You can view up to 90 days of available request history. Expired history is no longer available.

## Troubleshooting

* **No recorded requests:** check the selected key and period, then make a request and refresh. Older unassigned history is not shown.
* **Many 4xx responses:** check credentials, permissions, input validation and request limits.
* **Many 5xx responses:** retry cautiously and contact support if errors persist.
* **Higher response times:** compare the affected endpoint and time period; ECU background processing is measured separately.

See [Credentials and authentication](https://docs.remapdb.com/api/credentials-and-authentication.md) and [Usage limits](https://docs.remapdb.com/api/usage-limits.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.