An AI API on your organization's own domain
Understand RN white label inference domains: branding, domain checks, HTTPS and binding to organization keys.
Rota Nacional · Published · Reviewed
The endpoint is part of an integration
A company can give its applications an inference endpoint under its own brand. RN binds the virtual domain to the organization. The endpoint keeps the API contract while its name and visual identity come from authorized settings.
This binding does not create shared customer access. One organization's domain refuses another organization's key. Branding does not transfer provider secrets to the browser or to public application code.
From configuration to activation
The process includes registering the domain, checking its DNS destination, binding it to the correct organization and enabling HTTPS. Configure the specified records and wait for validation. Do not replace an application's endpoint until the domain is active and its certificate works.
The organization manages its brand name, logo and legal information. Email delivery has separate settings. Enabling a brand does not prove that its sender is authorized to deliver email; check that state separately.
Keep policies when changing the address
A call through a custom domain still follows organization permissions, allowed networks, quotas and the financial contract. Native access still requires consent. When the organization requires the barrier, changing the hostname does not unlock /v1/providers/*.
Before switching, validate the correct key, the application's API path and access to existing resources. Keep a rollback path to the previous endpoint. Do not publish customer names, domains or credentials in marketing material without authorization.
Frequently asked questions
Does a custom domain accept another company's key?
No. The domain is bound to the organization and authentication must match it.
Does an active brand mean email is also active?
No. Branding and sender configuration have separate states. Delivery depends on email configuration and sender authorization.
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.
Manage multiple AI keys with organization isolation
Organize provider connections by company. Learn how pause, weights, consent and file ownership keep customer usage separate.