Health Checks

Reviewed by Proof · Updated

Definition

A luv13 health check is a quick request, usually GET /v1/models, that tells you whether the API is reachable before you debug your own code.

Key takeaways

  • GET https://api.luv13.ai/v1/models is the simplest check. On 2026-09-30 it answered HTTP 200 without a key and costs no tokens.
  • HTTP 200 with seven model ids means the API is reachable.
  • HTTP 522 means Cloudflare couldn't reach luv13's servers. It happened on the morning of 2026-09-30 and cleared by 10:36 PT. It's not a problem with your code or key.
  • A models check doesn't prove chat works. To test your key and a model end to end, send a one-token chat request.

Level 1: is the API up?

curl -s -m 20 -o /dev/null -w "%{http_code}\n" https://api.luv13.ai/v1/models
OutputMeaning
200Reachable
522luv13's servers are unreachable behind Cloudflare. Wait and retry.
000No response within 20 seconds, or a network or DNS problem on your side

Level 2: do my key and a model work?

curl -s -m 60 -w "\nHTTP %{http_code}\n" 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"}]}'

When the key works, this is billed like any request, a tiny fraction of a cent at $0.33 per 1M tokens. A 401 means the key is wrong; anything else, see Errors and Status Codes.

Monitoring

  • Use Level 1 for frequent automated checks. It's free.
  • Run Level 2 rarely, because it draws on your balance.
  • Alert on repeated failures, not one. luv13 runs on single-provider capacity, and brief failures under load are expected; see Retrying Requests.
  • Check that the response still lists the model id your app uses. If it's gone, switch ids. See Listing Models.