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.
Rota Nacional · Published · Reviewed
Change access while preserving the contract
An application that already uses a provider may depend on parameters absent from a generic chat API. RN's native /v1/providers/{provider}/ gateway accepts the original API path. The model retains the format expected by the provider.
The application authenticates with an RN organization key. The external secret stays in the server connection. The gateway preserves the body, parameters, response and provider HTTP error. It does not substitute a rejected parameter or change the model to obtain an answer.
Check three conditions before switching
- The connection must belong to the organization or an explicitly authorized supplier.
- The application's path and contract must be supported by the gateway. Check files, streaming and asynchronous results as well as chat.
- Native transmission requires consent and does not apply the content barrier. A privacy requirement from the organization or supplying pool refuses the request.
Migrate one workflow at a time
Register the connection, check the financial contract and select the inference domain. Update the application's endpoint and credential. Validate a representative request, expected errors and resources read later by the workflow. A working chat does not prove batch or upload support.
Without X-RN-Connection-Id, selection takes place within the authorized pool. This header identifies a connection; it is not an access credential. Existing resources retain their original connection. The gateway does not automatically repeat a submitted call: check its state before trying again.
Frequently asked questions
Does the application need the provider key?
The application uses its RN organization key. The provider secret stays encrypted in the server connection.
Does the native gateway anonymize requests?
No. It preserves the original body. Use protected chat for the barrier; when the barrier is mandatory, native requests return 403.
Keep reading
Require privacy across your organization's API keys
An organization can require the RN privacy barrier. Understand native API blocking, the 403 error and the protected chat path.
Manage multiple AI keys with organization isolation
Organize provider connections by company. Learn how pause, weights, consent and file ownership keep customer usage separate.
Track inference costs, limits and receipts
Distinguish reservations, measured usage and charges. Read RN receipts, interpret pending states and avoid repeating paid calls.