APIIntermediateClaude API
In multi-tenant setups, one API key per tenant
With a single shared key, when the org rate limit trips you see the spike but not who caused it, and every customer suffers.
Separating keys per tenant gives you attribution (who consumes what) and isolation (one tenant's excess does not take down the others). The course presents it as a requirement for any production multi-tenant deployment. Add it to your observability design from day one.
Example
Scheme: - tenant-a → key-a - tenant-b → key-b On your dashboard: usage and 429 errors per key.