使用单个 Bearer 密钥将 Vortixy Chat 集成到你的项目中。配额与你的套餐一致。 在仪表盘 → 你的 API 中创建密钥
在 Authorization 标头中发送你的密钥。切勿在客户端代码或查询参数中暴露它。
curl https://www.vortixy.net/api/v1/chat \
-H "Authorization: Bearer vtx_live_abc123..." \
-H "Content-Type: application/json" \
-d '{"message":"Hello Vortixy"}'Scopes: chat, images, search, usage, models。密钥共享你套餐的配额。
Browser calls: responses only carry Access-Control-Allow-Origin when the request Origin is allowlisted on the key (Dashboard → Your API → Allowed origins). Keys without origins are same-origin/server-side only. Update a key's list with PATCH /api/v1/keys/:id {"allowed_origins": ["https://example.com"]} (https only, max 10, [] = Vortixy only).
# Keys are session-only (dashboard cookie) — Bearer keys can't manage keys
# List (max 5 active, key_prefix only, never raw)
curl https://www.vortixy.net/api/v1/keys -b "sb-auth-token=..."# Create (raw shown once — copy it now, stored hashed; 6th active → 429 apiKeyLimitReached)
curl -X POST https://www.vortixy.net/api/v1/keys \
-b "sb-auth-token=..." -H "Content-Type: application/json" \
-d '{"name":"My App","scopes":["chat","usage"]}'
# Quotas are shared web+API and reset daily at 00:00 UTC
# (GET /api/v1/usage → used.* + resetsAt; 429 → Retry-After + RateLimit-*)按月还是按年?
年付可节省 17%。