DEV Community

Germey
Germey

Posted on

Build an AI API Site You Can Monetize: Secure Customer Key Onboarding

A branded AI API portal is not just a landing page. To be useful, it must give a developer a repeatable path from registration to a verified API call—without asking them to share credentials with the portal operator.

This tutorial designs that onboarding path for an Ace Data Cloud white-label API Platform. It focuses on delivery rather than DNS setup: what the customer receives, how they create an independent key, and how both sides decide that onboarding is complete.

Disclosure: Ace Data Cloud provided the source material and commissioned this article. The article was reorganized and drafted with AI assistance, then checked against the public documentation. It describes a documented workflow, not personal revenue or customer results.

First, define the product boundary

Ace Data Cloud lets an operator configure a branded developer portal with a site name, logo, service catalog, pricing, documentation, support details, and an optional custom domain. The API Platform is intended for developers who connect applications with keys; the Studio product serves users who want browser-based creative tools.

A white-label API site should not be presented as a separately delivered gateway or an independent tenant identity system. Customers use a shared identity system, but each customer signs in with their own account and obtains their own API key. The operator should never distribute one “master” key to multiple customers.

This boundary changes the onboarding design. Your job is to make four values unambiguous:

Value Meaning Common onboarding mistake
Page URL Where the customer registers, signs in, and reads docs Using it as the request endpoint
API Base URL Where application requests are sent Confusing it with the docs website
API key A credential created in the customer's account Sharing the operator's key
Service/model name The public identifier required by the selected API Replacing it with a marketing label

Step 1: Prepare a minimal onboarding packet

Do not begin with every service in the catalog. Pick one service you can support, one corresponding documentation page, and one small request. Before inviting a customer, verify that the portal page is active and that the API Base URL shown in your own console is the one your instructions use.

A safe onboarding packet can look like this:

Portal: https://portal.example.com
API Base URL: https://api.example.com
Service/model: <PUBLIC_SERVICE_NAME>
Documentation: https://portal.example.com/docs/<SERVICE>
Support: support@example.com
Enter fullscreen mode Exit fullscreen mode

These domains and identifiers are placeholders. If you configure a custom domain later, obtain the required CNAME value from your own console rather than copying another site's DNS record.

The packet should also say: “Create and keep your key in your own account. Do not send the full key to support.” This single instruction prevents the operator from becoming an unnecessary credential custodian.

Step 2: Make registration return to the branded portal

Ask a first-time customer to begin at the page URL, not at a generic login page. After authentication, the browser should return to the branded site. Depending on the portal's login presentation setting, authentication may appear in a dialog or on a unified authentication page; neither is the API-key screen.

For attribution testing, use a genuinely new test account. Signing an existing shared-system account into a new white-label site does not make it a newly registered customer or rewrite its prior relationship.

That distinction matters commercially. Customer attribution and revenue are not inferred from traffic alone. According to the public rules, invitation relationships determine attribution, while qualifying orders and current distribution rules determine earnings. Registration or API usage by itself is not a commission event.

Step 3: Have the customer create a scoped key

After login, direct the customer to the portal console and then to the applications area. The documented routes are:

/console/applications
/console/credentials
Enter fullscreen mode Exit fullscreen mode

From the relevant application, the customer opens key management and creates a credential with a recognizable name such as onboarding-smoke-test. Where the UI offers them, set an expiration, a usage limit, and an allowed-API scope appropriate for the test.

Credential creation form showing a name, usage controls, expiration, and allowed APIs

Catalog visibility is not authorization. Hiding a service from the storefront does not necessarily prevent an otherwise valid key from calling it. If access must be constrained, configure and test the key's actual API permissions.

The customer should store the credential in a server-side secret manager or protected environment variable:

export AI_API_KEY="<CUSTOMER_API_KEY>"
export AI_API_BASE_URL="https://api.example.com"
Enter fullscreen mode Exit fullscreen mode

Never place the key in browser JavaScript, a public repository, a tutorial screenshot, or a support chat. A useful operating pattern is one key per customer project and environment, because it limits blast radius and makes rotation easier.

Step 4: Run one documented smoke test

API styles differ: a native endpoint, an OpenAI-compatible protocol, and an MCP integration are not interchangeable. Select only the method required by this customer and copy the smallest example from that service's documentation. Replace only the documented Base URL, credential, service name, and required parameters.

Do not invent a universal endpoint such as /v1/generate; use the actual path and payload from the chosen service documentation. Before submitting, show the customer the current price and avoid expensive batch, long-video, or high-volume tasks for the first test.

A submitted asynchronous job is not yet a completed result. If the API returns a task identifier, continue with the documented status flow until it reaches a terminal state.

Step 5: Define “onboarding complete” with evidence

A visually successful response is only half of the acceptance test. Open the customer's usage records and locate the matching entry by time. Verify:

  • the request completed successfully;
  • the expected service handled it;
  • the recorded consumption and balance change are understandable;
  • the customer can repeat the workflow without sending you their secret.

Use a simple completion rule: one successful minimal call plus one corresponding usage record.

If the request fails, collect the timestamp, path, status code, and any safe request or task identifier. Never ask for the entire authorization header. If the credential was created only for acceptance testing, the customer can disable or delete it afterward and confirm with a low-risk request that the old key is rejected.

Revenue is downstream of correct delivery

A white-label portal can support a branded service business, but monetization should be explained accurately. Operators can configure channel pricing, yet a displayed markup is not automatically the operator's earnings. Actual results depend on a qualifying completed purchase, customer attribution, the current distribution rules, and adjustments such as refunds or risk review.

API consumption and commission are separate records: usage proves product delivery; earnings arise from qualifying purchases, not a rebate on every API call. Avoid promises of fixed income or guaranteed profit. The practical growth loop is less dramatic: publish a clear catalog, acquire customers, help them complete a safe first call, and reconcile valid purchases against the distribution records.

Production checklist

Before promoting the portal, verify the following in a private acceptance pass:

  • Brand name, logo, support channel, terms, and privacy links are present.
  • Page URL and API Base URL are labeled separately.
  • Each promoted service has current pricing and usable documentation.
  • A new customer can register and return to the branded portal.
  • The customer can create a scoped key without operator access.
  • A minimal request maps to one usage record.
  • Attribution and qualifying purchase records are reviewed separately from usage.

For the implementation details, see Ace Data Cloud's white-label API Platform guide, customer registration and API key delivery documentation, and customer attribution and earnings rules. Operators can manage sites from the Site Management console.

A portal is ready to monetize only when the technical handoff is boring: customers know where to sign in, which URL their code calls, where their own key lives, and how to verify the first chargeable use without exposing secrets.

Top comments (0)