Connect OpenAI and Anthropic clients to RN
Choose protected catalog or native gateway before configuring an AI client or coding agent. Model, endpoint and key must match.
Rota Nacional · Published · Reviewed
Choose the contract first
RN provides OpenAI-format chat at /v1/chat/completions and Messages-format chat at /v1/messages. This catalog uses rota/* identifiers and applies the organization's personal data policy.
The native gateway is a different contract. It preserves the provider's model and format through /v1/providers/{provider}/. Do not switch paths by changing only the hostname: check support for the tools, files, media and response formats the client needs.
Configure endpoint, credential and model together
For an OpenAI-compatible client, the catalog base URL is the RN origin followed by /v1. Use an RN key and a model published by /v1/models. For an Anthropic-compatible client, follow the documented origin and Messages path.
The coding-agent page provides RN configuration examples for supported clients. Copy the example for your actual client. Do not expose secrets in repositories, screenshots, public commands or shared configurations. A connection identifier is not an RN key.
Validate failures too
Send a short request with fictional content. Then check the streaming, tools and limits your workflow actually uses. A 401 indicates a credential problem; a 403 may come from organization policy; a 402 requires balance or valid financial terms. The error body provides the specific code.
When the organization requires the barrier, the client must use a protected path. A coding agent does not gain permission to send raw content by selecting another provider. The application retains control of which files and information enter its context.
Frequently asked questions
Can I use any model name in the protected catalog?
Use identifiers published by /v1/models and enabled for the organization. Provider-native names belong to the native gateway contract.
Does chat compatibility cover the provider's entire API?
No. Check the paths and features your application uses. Files, media, tools and asynchronous operations have their own contracts.
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.
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.
n8n with AI and privacy: a customer service workflow
Use RN's n8n example to receive a message and return an answer. Check authentication, limits and responsibilities before connecting your channel.