← Help Center· Cover-up plan
Any tool that supports Custom OpenAI Compatible Interfaces can reach us. The tool you use is not in the list above? Just follow these general instructions.
Look for these keywords in its settings, and if any one of them appears, it means that it can be picked up:
| Keyword | Description |
|---|---|
| Custom Interface/Custom Provider | You can create a new one of your own |
| OpenAI Compatible/OpenAI Compatible | Protocol Matching |
| Base URL/API Address/Interface Address | Changing the address is enough |
| Reverse proxy/proxy | Some tools use this as an entrance. |
No matter what the interface is called, the essence is these four items:
This is where things go wrong the most. Different tools have different expectations for "interface address". Depends onWill it make up the path itself?:
| Tool Behavior | You fill in | Examples |
|---|---|---|
It makes up for itself/v1/chat/completions |
Fill in the domain name only | https://sccclm.com |
It only replenishes/chat/completions |
Fill in to/v1 |
https://sccclm.com/v1 |
| It requires a full endpoint | Complete | https://sccclm.com/v1/chat/completions |
https://sccclm.com/v1; if 404 is reported, replace it withhttps://sccclm.com; If 404 is reported, fill in the complete endpoint.
You can definitely try it out within three times, no need to check the documentation.# Error - will become /v1/v1/...
https://sccclm.com/v1/v1
# Error - we only recognize our stall name
gpt-4o
claude-3-5-sonnet
deepseek-chat
# Correct
newcclm
newcclm-fast
newcclm-coding
newcclm-free
Some tools will let you choose "OpenAI format" or "Anthropic format". Always choose OpenAI - if you choose another one you won't be able to connect.
The key is only entered in the settings. Writing into conversations is both useless and revealing.
After matching, first use this to confirm that the service itself is working:
curl https://sccclm.com/v1/chat/completions \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"newcclm-fast","messages":[{"role":"user","content":"Hello"}]}'
| Results | Description |
|---|---|
| Returns JSON with content | No problem on the server side. → Next, check the tool settings. |
Invalid token | The key is incorrect, it has nothing to do with us |
model not found | Model name misspelled |
404 | The address hierarchy is wrong, see Section 3 |
| Unable to connect/Timeout | Network problems |
Tell us which tool you are using and we will add a dedicated configuration instructions. It is enough to provide the tool name and a screenshot of the settings page (encrypted key).