When you get stuck

One small id and one page clear most problems in a minute.

3 minLesson 9 of 90 of 2 steps

Good news: most problems have three simple causes. Know where to look and it usually takes under a minute.

Check these three first

  1. [Service status](site:status): is this affecting everyone? If a model is unavailable right now, it shows here.
  2. [Usage & logs](/app/usage): did the request arrive at all? Open a row to see why it failed. The status filter separates your-side errors from our-side errors.
  3. [Wallet](/app/wallet): is the available balance enough? Has the key hit its cap?

Opening a ticket

If that doesn't settle it, open a ticket from Support. If it's about a request, copy its id from the log into the ticket. With it we find the exact request; without it we can only guess.

A good ticket says three things: what you did, what you expected, and what happened.

Support's reply appears on the same page, and a marker shows beside Support in the sidebar.

More to read

  • [Docs](site:docs): the complete API reference and tool guides.
  • [Blog](site:blog): guides and model comparisons.
  • The chat: ask a model too. Send it the error and ask for a plain explanation.

Learn the way to a ticket0 of 2 steps

  1. Go to Support and see where a new ticket starts.
  2. No need to send one. Just know where it is when you need it.

What you learned

  • Status first, then the request's log, then the balance.
  • Put the request id in your ticket.
  • That's the beginner level. To learn keys and the API, Intermediate is next.
API keys: making, keeping and limiting themA key isn't just a secret; it's the best tool you have for keeping spend under control.Done, next lesson