Product limits and lifecycle

Understand current console limits and deletion behavior before connecting production clients.

Current limits

Limits can vary by site or later release. Remove unused resources or contact the service operator after reaching a limit.

Balance and model source

• Connected models do not consume the Lumoswitch account balance and are not blocked by a low Lumoswitch balance.
• Connected models still follow the upstream provider's permissions, quota, rate limits, and billing.
• Platform models follow Lumoswitch balance, credit, and platform model billing policies.

Configuration and key lifecycle

• Creating an API configuration creates its initial access key.
• The full key is shown once.
• Editing a configuration keeps the existing key.
• Disabling a configuration blocks all of its active keys.
• Deleting a configuration revokes all active keys and immediately affects clients.

Disabling an access key is reversible. Replacement rotation keeps the old value usable only until the selected grace deadline, then blocks and removes it from the runtime. Session revocation does not revoke API keys.

Upstreams and models

Disabling an upstream removes it from new routing. Deleting a credential can leave an upstream without usable access, while deleting an upstream can affect every configuration that references its model resources.

Discovery creates or updates model resources. Models that disappear upstream can become unavailable, and stale health can return to unknown until rediscovery. Remove a model from configurations before deleting the resource.

Safe removal

1. Create a replacement resource or configuration.
2. Validate it with a minimal request.
3. Update every client.
4. Disable the old resource and check impact.
5. Delete it only after migration is complete.