Developers
The account's own API surface: traffic at a glance, the keys that unlock it, and every request it has answered.
Developers, opened from the account menu, is where the account's own use of the API lives: how much of it is being called, by which key, and the full log of individual requests. It is the same screen a project's own API tab renders, scoped to that one project instead of the whole account.
The three tabs
Overview
A time window (4h, 12h, 24h, or 1 week) picks what the tab is summarizing.
- The metric strip: total calls in the window, the split between REST and MCP, an error rate, and how many keys were active. A window that hit the server's own row cap is marked as partial, and the strip says so rather than quietly under-reporting.
- Top methods: the busiest method names in the window, each with its call count, an MCP badge when any of those calls came in over MCP, and an error count when any failed.
- API keys: the busiest keys in the window, each with its access level (Full or Custom), an MCP badge, an error count, and how long ago it was last used.
- Recent errors: the newest failed calls, with their status code, method, and channel.
- Two charts: successful versus failed requests over the window, and GET versus POST calls over the same window.
An account with no API or MCP traffic yet sees a plain empty state here instead of a wall of zeroes, with a shortcut into the Keys tab to create a first key.
Logs
The full request log, one row per call, with its own time window (4h, 12h, 24h, or 1 week, independent of Overview's).
A banner above the table says so when the window filled the server's row cap, since the log is otherwise silently the newest N rows rather than every one. Click a row to open that request in full: its body, its response, and its headers.
Opening Developers from inside a project shows that project's own requests, on the same three tabs, under the project's own API tab rather than the account menu.