TokensClub documentation
API 接口与范例
协议要与所选模型及渠道相符。下方使用完整请求 URL;不要把控制台页面当作接口地址。
| 协议 | 完整端点 |
|---|---|
| Chat Completions | POST /v1/chat/completions |
| Responses | POST /v1/responses |
| Anthropic Messages | POST /v1/messages |
Chat Completions
curl https://tokensclub.top/v1/chat/completions \
-H "Authorization: Bearer $TOKENSCLUB_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"YOUR_ENABLED_MODEL","messages":[{"role":"user","content":"只回复 OK"}]}' Responses
curl https://tokensclub.top/v1/responses \
-H "Authorization: Bearer $TOKENSCLUB_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "YOUR_ENABLED_MODEL",
"input": "Hello, TokensClub."
}'JavaScript:服务端请求
const response = await fetch("https://tokensclub.top/v1/responses", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.TOKENSCLUB_API_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({ model: "YOUR_ENABLED_MODEL", input: "只回复 OK" })
});
if (!response.ok) throw new Error(`HTTP ${response.status}`);
console.log(await response.json());串流与重试
需要串流时,按对应协议传入 stream: true,并使用 SSE 解析器处理增量事件。断线或超时后,先核对使用记录;重试可能形成另一笔独立用量。
图片、工具调用、快取及长上下文的支援范围取决于模型和渠道,不能由基本文字成功推断。