Auth and base URL errors
| Problem | Likely cause | Fix |
|---|---|---|
| 401 unauthorized | Wrong key, hidden spaces, or stale environment variables | Re-copy the key from the delivery package, restart the client, and re-test with a minimal request. |
| 404 or route not found | Wrong base URL shape | For OpenAI-compatible setups, use https://cheapai-netifly-app.up.railway.app/v1. |
| Connection timeout or generic network error | Temporary local network issue or client retry behavior | Retry once, then confirm the same request with curl to isolate whether the issue is the client or the network. |
Model and context issues
- Model not found: copy the slug directly from Supported Models.
- Request too large: shorten the prompt, split the task, or move large source material into smaller batches.
- Long-context cost surprise: review the note fields on the pricing table and model pages before sending oversized prompts.
Payment and quote issues
- Quote expired: return to checkout and generate a fresh quote. Old quote windows are time-limited on purpose.
- Wrong network: double-check the network label shown in checkout before sending funds. Asset name alone is not enough.
- Underpaid or overpaid: keep the transaction reference and contact support with the order number so the payment state can be reviewed safely.
Delivery and email issues
- Check spam and filtered inbox folders for the checkout email address you used.
- If you already have a claim link or account access, check the portal instead of waiting on email alone.
- A resend should reuse the same delivery package, not allocate a new one.
- If the order is paid and the access is still unclear, contact support with the order number.
When to contact support
Reach out when one of these is true:
- You confirmed the key, model, and base URL and still get blocked
- The order is paid but you cannot recover the delivery package by email or portal
- The payment appears unmatched, wrong-network, or otherwise operationally ambiguous