What the Page Shows
One table, with no filters, lists each request’s:- When
- Project
- Key
- Method
- Endpoint - for MCP calls, the tool name with an MCP badge
- Status
- Scope
- Latency
- Error - the error code, or the rate-limit state
Common Workflows
Debugging an integration
- Open API Activity
- Scan the Endpoint and Project columns for the failing calls
- Check Status, Scope and Error: a 403 with the wrong scope means the key needs that scope
- Check the Key column to confirm the expected key made the call
Retiring a key
A key missing from the latest 200 requests may still be in use. Check Last used on API Keys before you revoke it.Reviewing agent behavior
- Confirm agents or automations call only the expected endpoints and MCP tools
- Check response status and latency
- Check that each key’s scopes match the access it needs
Permissions
API Activity is available on plans that include API access.Best Practices
- Use distinct API keys for distinct integrations so the log stays attributable
- Check API Activity after changing scopes or rotating secrets
- Review rate-limited or error-heavy endpoints before widening access
Next Steps
- API Keys - Create, scope, or revoke keys
- Authentication - Review how keys and scopes work
- Webhooks - Pair outbound event delivery with inbound API usage