Create call keys, isolate purposes, limit models, and revoke leaked keys. Includes complete inspection steps, practical verification, and error handling.

Create and secure API Keys

First, complete the account

ExistRegistration and loginComplete the email verification code, login password, and account information. QQ / Alipay authorized accounts with imperfect must complete these steps before calling the model and making deposits.

Create a call key

1. OpenKey management, choose to create key.
2. The name clearly states the purpose, such as "Personal Cherry Studio" or "Project Development Environment."
3. Set validity periods, available limits, and model restrictions based on the actual options on the page; When using default grouping, there is no need to manually find hidden routes.
4. After saving, copy the key to your own password manager or client. Do not use web login passwords or backend management tokens instead.
5. UseLet's get startedA brief request for validation. The actual consumption balance is generated.

Each use has a separate key

Keys are created separately for computer clients, server projects, and temporary experiments, making it easy to distinguish uses in logs and to revoke them individually. Model limitations are only within the callable range and do not increase account balances; Both the key limit and the remaining account balance should be sufficient.

When the key is leaked

Immediately revoke the old key in key management, create a new key, update the client, and check recent consumption records. Deleting only public screenshots or Git files does not revoke already leaked keys. Do not send the full key to customer service; Provide error codes, times, and desensitized request information.

Address verification

The base URL is https://api.baiyun.si/v1。 The full Chat address is https://api.baiyun.si/v1/chat/completions； The full Responses address is https://api.baiyun.si/v1/responses。 Which one to fill in depends on the meaning of the client-side field; do not spell it out /v1/v1。

Checklist before practical use

1. Prepare your own account and access keys, and do not use others' shared credentials.
2. Records client versions, systems, and models to be used for easy reproduction during troubleshooting.
3. Save the original configuration or screenshot, hide keys, verification codes, and private content.
4. Confirm that testing may consume a small amount of DK, starting with a single sentence and a single request.
5. Review the current model plaza and status page before deciding whether to enable more features.

Detailed investigation: Which vouchers should not be mixed

The login password is only used for account login, and the model call key is only for /v1 model requests. Backend management PAT/Dashboard sessions have management permissions and cannot be integrated into regular clients. Sharing the same key among multiple people can confuse logs and quotas, prioritizing the creation of a unique key for each device or project.

How to confirm that this section has been learned

Don't just check the "Configuration saved successfully" prompt. You should be able to clearly state the current Base URL, key usage, chosen model, and request protocol, and be able to verify your operation results on the corresponding console. The client-side tutorial uses a single actual plain text response and corresponding logs as the initial completion standard; Account tutorials are based on comprehensive security information; The billing tutorial uses the correspondence between principal, channel fees, and DK as the standard.

If an error occurs, record the occurrence time, HTTP status, content of the anonymized error, and the actual expected result. Do not screenshot the entire page key, and do not give the password or verification code to others. For 401, authentication should be resolved first; for 400, parameters should be resolved first; for 429, intensive retries should be stopped; for 404, request paths and upstream verification should be verified; recharging cannot resolve all errors.

A small task suitable for practice

Complete the minimum steps in this section in your own testing environment, recording in text "how you originally set it, which item you modified, and what results you saw." Do not treat production data, real payments, or irrecoverable commands as exercises. If you encounter features beyond what this section offers, first check the corresponding protocol tutorial before considering adding features; Changing only one configuration at a time makes it easy to judge which step leads to errors.

The next step is the boundary of the version

Return to the full learning map · Streamlined API site configuration · Real-time status of this site。

The tutorial was compiled on October 9, 2026. The specific interface and capabilities may vary depending on the client and upstream versions; The configuration guidelines do not mean that all client versions have passed the test. For balance payments, QQ / Alipay login, and open channels, please refer to the actual page page; Compression interfaces: Previously, upstream 404 and raw image channels were not available, so don't assume configuration files can be automatically removed.