# Debugging requests

In addition to error codes in responses, inspect HTTP response headers to trace requests and understand rate limiting. Below is a concise list of headers Aitronos returns with Freddy API responses.

## API meta information

- `aitronos-organization` — Organization associated with the request
- `freddy-processing-ms` — Server processing time (milliseconds)
- `freddy-api-version` — API version used for this request (for example: `2025-01-01`)
- `x-request-id` — Unique request identifier (use for troubleshooting)


## Rate limiting information

- `x-ratelimit-limit-requests`
- `x-ratelimit-remaining-requests`
- `x-ratelimit-reset-requests`
- `x-ratelimit-limit-tokens`
- `x-ratelimit-remaining-tokens`
- `x-ratelimit-reset-tokens`


## Recommended practices

- Log `x-request-id` in production for faster support triage
- Capture processing time (`freddy-processing-ms`) for performance monitoring
- Surface remaining limits in logs/dashboards to anticipate throttling


## Quick checks

Verbose curl example:


```bash
curl -v https://api.freddy.aitronos.com/v1/models \\
  -H "Authorization: Bearer $FREDDY_API_KEY"
```

SDKs expose the request ID on top-level responses where available; include it in bug reports to Aitronos support.