Where the key goes
Keep it in an environment variable, as luv13.ai/docs does:
export LUV13_API_KEY=sk-luv13-...Then send it as a Bearer token:
curl https://api.luv13.ai/v1/chat/completions \
-H "Authorization: Bearer $LUV13_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "luv13/glm-5.3-flash", "messages": [{"role": "user", "content": "ping"}]}'In a tool or SDK, paste it into the API key setting and set the base URL to https://api.luv13.ai/v1.
A missing or wrong key returns HTTP 401 with "type": "invalid_auth". See Errors and Status Codes.
The account
| What | Detail |
|---|---|
| Sign-in | Google or email, at luv13.ai/dashboard |
| Billing | Prepaid credit in USD; top up any amount from $5 by card, through Stripe |
| Price | $0.33 per 1M tokens on every model, input the same as output |
| Charges | Usage draws down the balance; failed or empty calls aren't charged |
| Balance and usage | Shown in the dashboard |
Keep the key out of client-side code; anyone who reads it can spend your balance. See API Key Best Practices. How to authenticate is on Authentication, and prices on Pricing.
