What happens if your key gets banned — insurance
A shared API key can be banned, disrupting access. An insurance pool, funded by a small one-time stake, provides a payout if that happens. Health checks monitor key status to catch bans early. This article explains the mechanics conceptually.
The problem: key bans
When you use a shared API key to access multiple models, that key can be banned by a provider. Bans may occur due to policy violations, suspicious activity, or other reasons. A ban can immediately cut off your access, which is frustrating if you rely on the service.
The insurance pool
To mitigate this risk, many platforms maintain an insurance pool. The pool is funded by users who opt in by paying a small, one-time stake. This stake is not a recurring fee; it is a single contribution that activates coverage.
If a shared key you are using gets banned, you can file a claim. If approved, you receive a payout from the pool. The payout is designed to compensate for the disruption, though it may not cover all possible losses. The exact payout amount and conditions are defined by the platform.
Why a stake?
The stake serves two purposes:
- It discourages frivolous claims by requiring users to have some skin in the game.
- It builds a reserve that can be used to pay out legitimate claims.
The stake is typically small relative to the potential payout, making it an attractive form of insurance for heavy users.
Health checks
To detect bans early, platforms run regular health checks on shared keys. These checks send small test requests to the provider and verify that the key is still active. If a key fails a health check, it is marked as banned, and affected users are notified.
Health checks help in two ways:
- They reduce the time a banned key remains in rotation, limiting disruption.
- They provide evidence for insurance claims, confirming that a ban occurred.
How to file a claim
The claims process varies by platform, but typically involves:
- Reporting the ban through a support channel or dashboard.
- Providing details such as the key identifier and timestamps.
- Waiting for verification against health check logs.
- Receiving the payout if the claim is approved.
Limitations
Insurance does not prevent bans. It only provides financial compensation. Also, not all bans may be covered; for example, if a ban results from your own misuse, the claim may be denied. Always review the terms of the insurance program.
Summary
A one-time stake funds an insurance pool that pays out if a shared key gets banned. Health checks monitor key status to catch bans quickly. This system balances risk and encourages responsible use.