Usage and logs

The Aikey365 console includes usage and logging views for investigating requests, costs, and errors.

Useful diagnostic fields

Keep track of:

• request time
• API key name
• model ID
• endpoint or client type
• HTTP status
• error message
• streaming mode
• retry count

Visible fields and retention depend on current platform configuration.

Protect sensitive data

Avoid logging:

• full API keys
• passwords
• user private data
• unnecessary full prompts or responses
• sensitive payment information

If your business stores request content, apply your own access controls, redaction, and retention policy.

Investigating unexpected usage

1. Narrow the time range.
2. Filter by key and model.
3. Check automatic client retries.
4. Verify whether multiple environments share one key.
5. Compare current pricing with actual billing records.

Production monitoring

Your own systems should monitor success rate, P95/P99 latency, 429/5xx rates, cost trends, and key usage. Platform logs and application observability serve different purposes and should complement each other.