Manage multiple AI keys with organization isolation
Organize provider connections by company. Learn how pause, weights, consent and file ownership keep customer usage separate.
Rota Nacional · Published · Reviewed
A shared external account must not become shared access
When several applications use the same provider accounts, centralizing keys helps manage access. It does not authorize one company to read another's files, batches or responses. RN binds connections to the organization and records native resources in the space that created them.
The RN key authenticates the consumer. The external key belongs to the server connection. A connection identifier does not replace authentication or permit selection of another organization's key.
Manage the pool without changing secrets in projects
A pool can contain multiple keys for the same provider. Administration supports pausing connections and setting distribution weights among eligible keys. Selection respects the authorized scope; it does not grant access to any organization's balance.
A paused or revoked owned connection does not automatically permit another pool. Inheritance requires a relationship, a contract and the relevant native consents. A required privacy barrier takes priority over native consent.
Preserve asynchronous resource ownership
Files, batches and previous responses remain bound to their original connection. Later reads cannot randomly select another key. This matters when processing documents, tracking a batch or reading a task result.
Before revoking a connection, check pending work. When migrating an old resource, verify the organization, external account and original connection. Do not recreate paid work merely because its status lookup has not yet been integrated.
Frequently asked questions
Can I register multiple keys for one provider?
Yes. A pool supports multiple connections, pause and distribution weights. Connections must be eligible for the organization and contract.
Does changing a weight move existing files and batches?
No. Existing resources keep their original connection. Weights guide selection for new eligible calls.
Keep reading
An AI gateway that preserves your application's model
Centralize AI connections in RN without converting provider request bodies. Understand native endpoints, authorized pools and migration limits.
An AI API on your organization's own domain
Understand RN white label inference domains: branding, domain checks, HTTPS and binding to organization keys.
Track inference costs, limits and receipts
Distinguish reservations, measured usage and charges. Read RN receipts, interpret pending states and avoid repeating paid calls.