Scoped credentials
API keys can be given an expiry date and a budget ceiling so one credential cannot spend beyond its intended boundary.
Platform security
Designed to make API usage visible and controllable.
Quantel's product surface is built around least-surprise observability: scoped API keys, spend limits, request metadata, redacted error details and clear account controls.
Request-level diagnostics
Track endpoint, model, status, latency, input tokens, output tokens, total tokens, request size and charge in the console.
Metadata first
The console experience is designed around request metadata and redacted failure explanations rather than exposing payloads by default.
Operational notes
Use the controls that match your risk model.
Keep production and development keys separate, set a hard budget for each credential, rotate keys when ownership changes and review logs for unexpected status codes such as 429 or 502.
This page describes current product intent and is not a legal, compliance or security certification statement. Contact security@quntel.dev for security questions.