Beginner reading order, balance, client, and functional boundaries. Includes complete inspection steps, practical verification, and error handling.

Common Issues and Access Sequence

New users look at where first

Read in orderRegistration and login、Create an API Key、Let's get started, then select the corresponding client tutorial; Check before you start shoppingDK explainsAndWallet。

Do you need to purchase a subscription to this site?

Currently, you are spending based on your wallet balance; there is no need to purchase a membership subscription from this site. Upstream subscription, client subscription, and the site wallet are different services; Purchasing one does not automatically grant the other services.

Why do you still need an email and password after quick login?

First-time or incomplete accounts must be linked to email, complete verification codes, and set this site login password to facilitate account recovery and native security verification. Successful authorization does not necessarily mean the information is complete.

Can it generate images?

Currently, you cannot assume that a drawing entry or model tag appears on the page to have available image creation services. Previously, this site had not yet configured usable raw image channels or models; The tutorial does not promise image, audio, or video generation. New services should be subject to the actual model, billing instructions, and successful returns.

Can it be used on all clients?

Custom base URLs, model protocols, and permissions must match. Ordinary OpenAI chat and Codex compatibility have integration instructions; Subscriptions, completion, tools, or multimodal functions on other clients must be checked according to version and cannot be fully universal.

Where to view the page and request questions

Let's take a look firstStatus pageGive meTroubleshooting。 The community has itDetailed tutorial directory, suitable for first-time configuration, misunderstanding, and fee verification.

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: narrow down the scope of the problem in order

First, confirm that the account is complete, the key is valid, and the DK balance is sufficient, then verify the protocol, address, and model. Make a minimum text request using the same key; Only after it succeeds does it restore attachments, tools, or automatically retry each item. After saving the client configuration, reopen the session to avoid using the previous vendor in the old session.

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.