Help & Support

Support Center

Frequently asked questions, quick-start guides, troubleshooting manual, and technical assistance.

Quick Start & Support

Access quick integration guides or reach out via tickets and email for technical assistance

Ticket Support

Submit a ticket describing your issue with optional screenshots. Our engineers will reply promptly.

Submit & View Tickets

Email Support

Reach out to our official support team for technical help or business inquiries

support@ainfix.com

Frequently Asked Questions (FAQ)

Curated answers to the most common questions asked by developers

This platform is fully compatible with the standard OpenAI API specifications. In any OpenAI-supported SDK or client (such as NextChat, ChatBox, LangChain, Cursor, Dify), simply change the Base URL to:

https://api.ainfix.com/v1

* Note: Generate your secret key in "Console - API Keys" and use it as your Bearer Token / API Key.

HTTP Error Code Reference

Quickly identify and resolve issues when encountering API response errors

StatusError Type / MeaningCommon CausesTroubleshooting & Solutions
400
Malformed request payload
Bad Request
Malformed JSON, missing required parameters, non-existent model name, or prompt exceeded context limit.Validate JSON format, verify model name against Model Square catalog, or reduce prompt length.
401
Invalid API Key / Unauthorized
Unauthorized
Missing Authorization header, typo in API Key, or key expired/disabled.Check token status in Console and ensure header is `Authorization: Bearer sk-xxxx`.
403
Access Forbidden
Forbidden
Account banned, caller IP not in token whitelist, or key lacks permission for the requested model.Inspect token IP and model restrictions in Console, or contact support for account review.
429
Insufficient Quota or Rate Limit
Too Many Requests
Zero remaining balance, or request per minute (RPM) / token per minute (TPM) limits exceeded.Top up quota in Console wallet; add retry delay with exponential backoff for high concurrency.
500 / 502
Gateway or Upstream Channel Error
Internal / Upstream Error
Upstream provider outage or temporary network jitter. Gateway automatically fails over.Platform auto-retries across redundant channels. Retry in 1-2s; check probes if persists.
504
Upstream Generation Timeout
Gateway Timeout
Long generation prompt or heavy multimodal task exceeded HTTP socket timeout.Enable `stream: true` for streaming output and increase your client HTTP timeout setting.