Bearer authentication#
Send Authorization: Bearer followed by your API key. Keys use a sk_weightsapi_ prefix. The console shows each secret only at creation. Store it in a secret manager.
Multiple keys#
Create separate keys for production, staging and each application. Optional spending caps are lifetime USD limits, calculated from recorded usage and outstanding reservations. An empty allowlist means all available models.
Rotation and revocation#
Create a replacement key, update your application, then revoke the old key. Revocation blocks new requests immediately. Requests already admitted settle normally.
Account sign-in and funding#
Sign in through the console to manage your account and API keys. AI access is associated with your account; anonymous access is not offered.
AI access requires sign-in, one confirmed top-up of at least USD 100, an authorized API key and enough available credit for the request. Each later top-up also has a USD 100 minimum; smaller remaining balances stay usable when they cover the request. Credit requires transaction verification. Check service status for model availability before sending traffic.
Request example
curl https://weightsapi.com/v1/chat/completions \
-H "Authorization: Bearer $WEIGHTSAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "Qwen/Qwen3-32B",
"messages": [
{
"role": "user",
"content": "Hello!"
}
],
"stream": true
}'