Logicc
Logicc
Docs
  • Docs
  • Changelog
  • Support portal
    • Logicc API Documentation
    • 1. Access and Quickstart
    • 2. Models and Pricing
    • 3. Usage, Quota and Security
    • 4. Interfaces and Authentication
    • 5. Endpoints and SDK Examples
    • 6. Troubleshooting and Support

3. Usage, Quota and Security

Quota monitoring, rate limits, and secure data handling.

Version: August 18, 2026

13. Usage, quota, and rate limits

curl "https://api.logicc.cloud/api/governance/virtual-keys/quota" \
  -H "Authorization: Bearer $LOGICC_API_KEY"

The read-only endpoint returns the current usage and technical limit configuration associated with the authenticated key. Relevant values can include current usage, configured limits, reset timestamps, request counters, and token counters. The quota response is an operational status view, not an invoice.

Usage limits and technical rate limits are separate controls. A 429 response can occur even when the account usage limit has not been reached. Applications should use bounded retries with exponential backoff and jitter.

Bifrost quota reference: https://docs.getbifrost.ai/api-reference/governance/get-virtual-key-quota

15. Security and data handling

Logicc stores customer account data in Germany. API traffic is encrypted in transit, and stored data is strongly encrypted. Customer prompts, uploaded files, model outputs, and workflow content sent through the API are not used to train the connected models. Provider routes use Zero Data Retention where available.

Do not include API keys in support requests. Send request timestamps, endpoint, model ID, HTTP status, and the complete error body with secrets removed.

Logicc Help Center: https://help.logicc.com/docs

Operational recommendation

Poll the quota endpoint at an interval appropriate for the workload and alert before the configured limit is reached. Treat usage limits and technical rate limits as separate controls.

Prev2. Models and Pricing
Next4. Interfaces and Authentication
Was this helpful?