The auto routing tier selection is interesting, curious how it handles the credential surface area as you add providers. Each provider in the rotation is anothe

The auto routing tier selection is interesting, curious how it handles the credential surface area as you add providers. Each provider in the rotation is another API key that needs to exist somewhere in the request path. With 7+ providers, the secrets management problem compounds: rotation schedules differ per provider, a compromised key at one provider doesn't invalidate the others, and CI/CD pipelines end up holding plaintext keys for all of them simultaneously. Does the router hold the provider keys server side, or does the client pass them per request? The architecture doc doesn't make this clear.