Customer Registration, API Key, and API Delivery

This article walks through the registration, obtaining an API Key, calling, viewing usage records, and deactivating credentials for a brand new customer, completing the final acceptance before the API Platform goes live.

¶ Completion Effect

Customers can register at platform.zhishuyun.com and obtain independent credentials, calling the API through xapi.zhishuyun.com; the webmaster can view usage and billing, and deactivate the credentials when necessary.

¶ Preparation Before Starting

A test customer who has never registered before;
Verified page domain and API domain;
A low-cost test API has been selected;
The quota, support range, and deactivation conditions for the customer have been clarified;
The webmaster's main API Key is not used to deliver to the customer.

¶ Step 1: Register with a New Customer

Open a brand new incognito window;
Visit https://platform.zhishuyun.com;
Click on register;
Complete registration using the test customer's email or phone number;
After confirmation, return to the Zhishuyun page domain;
Record the test customer account and registration time.

¶ Step 2: Create an Independent API Key

Log in to the console with the test customer;
Open application or API Key management;
Create an application specifically for acceptance;
Create an independent API Key;
If the interface supports it, set quotas or limits;
Save it only in a secure location, do not place it in public documents or frontend code.

Each customer, project, or environment should use an independent Key. Do not allow unrelated customers to share the webmaster's main Key for an extended period.

¶ Step 3: Execute Minimal Call

Provide the customer with four items:

Base URL: https://xapi.zhishuyun.com
API Key: Created by the customer or delivered separately
Service/Model: Currently allowed services and models
Docs: https://platform.zhishuyun.com/documents/...

Initiate a call using the real minimal example from the documentation. Do not create high-resolution, long videos, or large batch tasks directly for acceptance.

¶ Step 4: Check Usage Records and Billing

Return to the test customer console;
Find the previous request;
Verify the time, service, status code, and consumption;
Check for changes in balance or quota;
The webmaster side checks customer attribution and compliant transaction records.

¶ Step 5: Validate Three Delivery Methods Separately

Method	What the Customer Needs	Acceptance Focus
Native API	Base URL, Key, API documentation	Path, parameters, asynchronous polling
OpenAI Compatible	`base_url`, Key, model name	Can the SDK return results directly
MCP	Installation method, environment variables, tool instructions	Tool discovery, quota, timeout handling

The three methods share underlying credentials and billing, not three separate ledgers.

¶ Step 6: Test Deactivation

Deactivate or delete the acceptance Key;
Resend the same request;
Confirm the request is denied;
When recreating the Key, confirm the old Key will not be restored;
Write the credential rotation and customer exit process into internal operation instructions.

¶ Success Indicators

The new customer registers from the Zhishuyun entrance and correctly redirects;
The customer successfully calls using an independent Key through a custom API domain;
Usage records, quotas, and billing are correct;
Documentation, model names, and Base URL are consistent;
After deactivating the Key, the old credentials cannot continue to call;
The customer knows the support channels, quotas, and deactivation rules.

¶ Frequently Asked Questions

¶ Copying Code Still Uses Default Domain

Return to the Site domain page to confirm the API domain has been verified, then force refresh the documentation. If writing examples by hand, be sure to update all language versions simultaneously.

¶ Call Successful but No Usage Record

Record the request time, path, status code, and publicly available request identifier, wait for a brief write-in period, and check again; if still missing, contact support. Do not provide the full API Key.

¶ Customer Key Can Call Undisplayed Services

Directory hiding is not permission isolation. Use application quotas, credential management, and clear customer contracts to control the usage scope.

¶ Next Article

Continue reading Customer Attribution, Markup, and Distribution Revenue to confirm that this test customer indeed belongs to you.