Configuration steps, applicable prerequisites, and common compatibility issues. Includes complete inspection steps, practical verification, and error handling.

Chatbox Integration Guide

Preparation before use

ExistKey managementCreate a dedicated call key for this tool separately to confirm that the account is complete and the DK balance is sufficient. The client version affects the entry name; this page explains the configuration items; Please refer to the current version of the actual interface.

Configuration steps

Open the Model Vendor in Settings and choose Custom or OpenAI-compatible services. Fill in the site address and key, then specify the model; After saving, test with a new plain text session. If there is no custom address entry in the version, you should first check the official instructions for that version.

Minimal validation

First, turn off online search, images, attachments, knowledge bases, and auto-execution tools, then send a plain sentence. Verify that the client has indeed selected our supplier, and thenUsage logView this model and consumption. The client connectivity button may only check the model list and cannot replace a real chat.

Frequently Asked Questions

When an address requires a complete endpoint, the Chat address should be https://api.baiyun.si/v1/chat/completions； When requesting a base URL, use the address in the table. Appear /v1/v1 Or repeat /chat/completions At that time, the address was changed first. 401 Verify keys and effective suppliers; 429 Stop parallel testing and wait; 404 Check protocols and models; do not disguise unsupported protocols as another model.

Capabilities and data

This page provides configuration guidance and does not complete full-feature real-person testing for each client version. Custom models do not guarantee access to the client's official model completion, tools, or subscription features. Third-party clients may upload sessions or configure synchronized data; review their privacy settings before use; Do not publicly export configurations containing keys.

Official client profile · Site Agreement Description · Troubleshooting

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.