White Label API Platform: Establishing a Developer-Focused Proprietary Brand API Site

The White Label API Platform is a product form of the White Label platform aimed at developers and enterprises. You can showcase services, pricing, and development documentation under your own brand, allowing customers to call unified AI capabilities through your API domain.

1. Create an API Platform Subsite

Create a subsite in the Platform's Site console. The subsite will initially receive a platform subdomain and inherit the shared service directory; you can then adjust the displayed content according to your business needs.

The Site console currently includes:

  • Basic information;
  • Domain name;
  • Pricing;
  • Services;
  • Documentation;
  • Banner;
  • Brand and customer service;
  • Advanced settings.

2. Configure Basic Branding

First, set the following uniformly:

  • Site name and description;
  • Logo and Favicon;
  • Company and copyright information;
  • Customer service channels;
  • Links to documentation, terms of service, and privacy policy;
  • Whether to hide the platform brand logo and API code entry.

This information will affect the homepage, footer, support page, and documentation content. It is recommended to determine the brand name and customer commitments before configuring services.

3. Set Service Directory and Pricing

In "Pricing," set the default markup for the entire site, and in "Services," configure for specific services:

  • Whether to display;
  • Independent markup ratio;
  • Display title;
  • Display summary;
  • Sorting.

Service-specific markups take precedence over the default value for the entire site. Hiding services mainly affects directory visibility and should not be understood as interface-level access control; customer credentials' permissions and quotas need to be managed separately.

4. Customize Development Documentation

In "Documentation," you can:

  • Hide non-sold documentation or entire subdirectories;
  • Modify the display title and summary of documentation in navigation;
  • Adjust sorting;
  • Retain tutorials and examples consistent with the current service directory.

When rendering documentation on the site, the name will be processed according to the Site brand, and when a verified API domain exists, the API Host copied for customers will be displayed as your domain name.

Banners can be used to showcase:

  • Brand positioning;
  • Featured services;
  • New models or activities;
  • Links to documentation, registration, or support pages.

Supports visibility status, sorting, time range, and multilingual titles. Do not carry over platform activities unrelated to your brand on the white label site.

6. Bind Platform Page Domain Name

The page domain name is used to host the homepage, service directory, pricing, and development documentation:

  1. Add the domain name in the "Page Domain" section of the domain tab;
  2. Add CNAME as prompted;
  3. Wait for DNS to take effect and verify;
  4. Open the homepage and documentation using HTTPS.

The page domain name and API request domain name serve different purposes and are recommended to be used separately, for example:

developers.example.com   # Platform page and documentation
api.example.com          # API requests

7. Bind API Request Domain Name

The API request domain name is used for the Base URL in customer code:

  1. Add api.example.com in the "API Domain" section;
  2. CNAME it to the API Proxy address provided by the console;
  3. Wait for DNS to take effect and click verify;
  4. After successful verification, copy the call example generated by the console.

The custom domain name for the API adopts a "doorplate change" model:

  • Customers can call through your domain;
  • TLS, routing, authentication, and billing are still handled by the unified gateway;
  • It will not automatically limit the token to a specific Site;
  • Do not promote it as an independent gateway or tenant-level token isolation.

8. Deliver API to Customers

Choose based on the customer's tech stack:

  • Allocate customer credentials and set quotas;
  • Provide OpenAI compatible Base URL and examples;
  • Integrate Agent, IDE, or proprietary products through MCP.

See Delivering API to Customers for details.

9. Launch Acceptance Checklist

  • [ ] The page domain displays your brand, customer service, and legal information;
  • [ ] The service directory only shows services ready for sale;
  • [ ] Pricing for the entire site and per service is correct;
  • [ ] Documentation directory, titles, and examples are consistent with services;
  • [ ] API request domain is accessible via HTTPS;
  • [ ] Copy code uses your API Host;
  • [ ] Complete a non-destructive call using test customer credentials;
  • [ ] Usage records and billing are correct;
  • [ ] Customers are clear about quotas, support scope, and boundaries of the API domain name.

The White Label API Platform addresses product and delivery; customer acquisition should be continuously achieved through technical articles, case studies, GitHub, developer communities, and Connectors.