Trust
MetisRouter Security
Security guidance for teams using MetisRouter API keys, request logs, billing controls, and production workflows.
Last verified: 2026-06-05
Security practices
MetisRouter users should keep API keys scoped, rotated, and separated by app or workflow when practical.
- Store API keys in server-side secrets, not public clients.
- Use separate API keys for customers, environments, or workflows.
- Share request IDs, not API keys, when contacting support.
Operational visibility
Usage Logs provide request IDs, model IDs, endpoint types, latency, usage, and charged amount for debugging and audit workflows.
- Review failed requests before retrying.
- Use bounded output limits to control spend.
- Email [email protected] for security-sensitive support issues.
FAQ
Where should support requests go?
Email [email protected] with request IDs and account context.
Where should high-volume usage requests go?
Email [email protected] for high-volume usage and commercial account questions.