Console
Usage and request logs
Every REST and MCP call made with your API keys is metered. Usage charts, quotas, request logs with request ids, retention and what is never recorded.
What is recorded
Every REST and MCP call made with an API key is recorded after the response is sent, so it never slows the request:
| Field | Example |
|---|---|
| Time | 2026-09-26T09:03:43Z |
| Key | its id and name |
| Method and route | POST /v1/projects/:id/design, or /mcp with the tool name |
| Status | 200, 402… |
| Duration | milliseconds |
| Request id | req_655570d3… |
| Client address | truncated to /24 (IPv4) or /48 (IPv6) |
| User agent | truncated |
Request and response bodies are never recorded, and neither are tokens.
Request ids
Every API response carries an x-request-id header. Quote it to support: it finds the exact call in your logs. Error pages show a reference too.
Usage
Platform → Usage shows requests per day by status class (2xx, 4xx, 5xx), latency (p50 and p95), top routes and tools, and your plan's quotas with a projection to the end of the month. Warnings appear at 80 % and 100 % of a quota.
Request logs
Platform → Request logs lists the calls with filters (key, status, route or tool, time range, request id). Open a call to see its timing, status, error code and a ready-made curl command with a placeholder key. Export the selection as CSV.
Retention
Individual calls are kept 30 days; daily aggregates per key, route and status 13 months.