Stability advice

If you want the service to feel reliable, the key is not writing “99.9%” somewhere. The key is that customers can actually use it without things falling apart. These practices are useful:

• Retries with backoff: useful for network fluctuations or 5xx errors, such as 1s -> 2s -> 4s.
• Timeouts: do not let requests hang forever. After timeout, retry or show a clear message to the user.
• Concurrency control: start with low concurrency until it is stable, then increase gradually.
• Record request IDs when available: when something goes wrong, this makes it easier to locate the issue instead of guessing.

Security advice

The most important rule: your API key belongs only to you.

• Do not write API keys into code repositories, especially public repositories.
• Use environment variables to inject keys in production.
• Do not print keys into logs. Many people accidentally expose keys while debugging.