Skip to main content
Enterprise organizations can configure an API hostname such as ai.example.com. Your applications use that host with their existing Aixy project keys. The domain changes the API address; the key still determines the organization, project, and permissions.

​
Configure the hostname

  1. As an Owner or Org admin, open Custom domains from the account menu.
  2. Add an exact subdomain you control, such as ai.example.com.
  3. Copy the routing CNAME and certificate-validation CNAME shown in the dashboard to your DNS provider, using the exact names and values.
  4. Keep the routing record in DNS-only mode when your DNS provider offers proxying.
  5. Wait until the domain is Active, then test a model-list request through the new hostname.
One hostname is configured per organization. Use a subdomain rather than an apex or wildcard. Provisioning is asynchronous; the presence of DNS records alone does not establish that the certificate and routing are ready. Keep the validation CNAME for certificate renewal.

​
Update clients

For an OpenAI-compatible client, set its API base to https://ai.example.com/v1. For a client that appends its own versioned path, use the hostname format described in its integration guide. Verify inference and request IDs before switching application traffic.

​
Maintain or remove the domain

Review the dashboard status after DNS changes. Leave certificate-validation records intact. Before removing a domain, move its clients to another working API host. Domain removal can remain in progress while certificate cleanup completes; monitor its final status in the dashboard.