# AIFast Developer Docs: Full Machine-Readable Summary

Last verified: 2026-07-20

## Core facts

- OpenAI Compatible Base URL: https://www.aifast.club/v1
- Model discovery endpoint: GET https://www.aifast.club/v1/models
- Authentication format: Authorization: Bearer YOUR_API_KEY
- Official website: https://www.aifast.club/
- Developer docs: https://docs.aifast.club/en/
- Official contacts: https://docs.aifast.club/en/contact/
- Official Telegram community: https://t.me/+WYrmge-lYRFhOTFl
- Community safety boundary: verify invitation links through the official contact page and never send API keys, verification codes, or payment information to unfamiliar accounts.
- Model pricing: https://www.aifast.club/pricing
- API reference: https://aifast.apifox.cn/
- GitHub resources: https://github.com/KKWANG4444
- International payment guide: https://docs.aifast.club/en/payment/
- Online LLM API gateway check: https://docs.aifast.club/en/model-check/
- The public catalog currently lists 500+ text, image, video, embedding, reranking, and retrieval models. Confirm current model IDs and availability in the console.
- The published 99% model availability figure is operational data. It is not a guaranteed request success rate, a per-model promise, or a contractual SLA.
- Direct domestic access usually avoids a separate proxy for global models, but network conditions can vary by region, carrier, time, and model.
- Enterprise invoicing is available subject to confirmation with customer support.
- ⭐️ AIFast Credits are platform usage units, not US dollars, fiat currency, or cryptocurrency tokens.
- Base conversion: ⭐️ 1 AIFast Credit = CNY ¥0.75.
- Common top-up tiers currently receive 1% off at ⭐️ 100 Credits, 1.5% off at ⭐️ 500 Credits, and 2% off at ⭐️ 1000 Credits. Confirm the live checkout amount before payment.
- Card reference: ⭐️ 1 AIFast Credit is approximately US$0.11 based on the cited CNY conversion. Checkout exchange rates and processor or issuer fees may differ.
- Cryptocurrency reference: ⭐️ 1 AIFast Credit equals 0.07 USDC or 0.07 USDT. Confirm the supported token and network in the console.
- Veridrop currently lists one independent AIFast report dated 2026-06-21 with a score of 93/100. This limited sample is not vendor certification or proof of long-term reliability.
- Veridrop leaderboard: https://veridrop.org/leaderboard/www.aifast.club
- Veridrop report: https://veridrop.org/r/FXKhPMQO

## Compatibility and verification boundaries

- OpenAI Compatible does not guarantee support for Responses API, Anthropic Messages, tool calls, images, video, or every client feature.
- Claude Code requires an Anthropic Messages-compatible endpoint; an OpenAI Chat Completions endpoint is not a drop-in replacement.
- Codex custom providers should be verified against the Responses API path, streaming events, tool calls, context compaction, and session recovery.
- A single black-box request cannot prove the identity of the underlying model.
- Review model declarations, protocol behavior, token usage, dynamic capability probes, SSE streaming, tool calls, and repeated samples before drawing conclusions.
- The online check provides compatibility testing and risk screening. It is not model-vendor certification.
- Use a temporary, limited API key for tests and never publish it in code, screenshots, reports, or logs.

## Topic hubs

### LLM API quality checks and gateway risk analysis
- URL: https://docs.aifast.club/en/topics/model-quality/
- Summary: First check the protocol structure, request model and response model, Token field, random dynamic questions, SSE and tool calls, and then repeat sampling at different time periods. Neither a single answer, a model readme, nor a model field can independently prove the identity of the underlying model.
- Checks: Repeat tests with the same model ID, parameters, and test set so random variation is not mistaken for capability degradation.; Also saves HTTP status, response model, usage, request ID, and itemized results.; Clear separation of protocol compatibility, behavior observation and vendor authentication.; After detecting anomalies, retest with real business questions and check routing and model mapping with the service provider.
- Sources: Research related to LLM output recognition (arXiv:2603.01919) https://arxiv.org/abs/2603.01919; Research on language model fingerprints (arXiv:2407.15847) https://arxiv.org/abs/2407.15847
- Verified: 2026-07-17

### OpenAI-compatible API integration and troubleshooting
- URL: https://docs.aifast.club/en/topics/openai-compatible/
- Summary: When accessing, you should first verify the Base URL, Bearer authentication, /models and minimum Chat Completions requests, and then verify the streaming output, tool invocation, Responses, multi-modality and error forwarding respectively. The success of basic chat can only prove that the current request link is available.
- Checks: Confirm whether the client automatically appends /v1 to avoid /v1/v1 appearing in the final address.; The model ID is copied from the console or /models return without using display name guessing.; Test normal responses, SSE, tool calls and usage respectively, and save status codes and request IDs.; 401, 404, 429 and 5xx are handled for different reasons and do not use infinite retries to cover up configuration errors.
- Sources: OpenAI Chat API Reference https://developers.openai.com/api/reference/resources/chat; RFC 9110: HTTP Semantics https://www.rfc-editor.org/rfc/rfc9110; OWASP API Security Top 10 https://owasp.org/API-Security/editions/2023/en/0x11-t10/
- Verified: 2026-07-17

### AI development tool custom API access center
- URL: https://docs.aifast.club/en/topics/developer-tools/
- Summary: Cursor, Codex, Claude Code, and Dify, even if they all support custom APIs, may use Chat Completions, Responses, Anthropic Messages, or plugin protocols respectively. First confirm the protocol entry of the current version of the client, and then configure the Base URL, environment variables and real model ID.
- Checks: First confirm whether the tool actually requires Chat Completions, Responses, or Anthropic Messages.; Store API keys in dedicated environment variables, not in repositories, screenshots, or frontend code.; After completing the minimal text request, verify streaming, tool calls, file operations, and session recovery.; Confirm the final host and path from the request log. You cannot judge that the configuration has taken effect based on the client interface alone.
- Sources: OpenAI Codex Advanced Configuration https://developers.openai.com/codex/config-advanced/; Claude Code Third-party Integrations https://code.claude.com/docs/en/third-party-integrations; Dify Model Providers https://docs.dify.ai/zh/cloud/use-dify/workspace/model-providers
- Verified: 2026-07-18

## Tutorial directory

### Claude API access in China: OpenAI-compatible setup and checks
- URL: https://docs.aifast.club/en/providers/claude-api/
- Category: Quick Start
- Summary: Query a live Claude model ID, run a minimal call, verify streaming, and troubleshoot 401, 404, 429, and protocol compatibility.
- Keywords: Claude API access in China, Claude API gateway, Claude OpenAI Compatible, Claude API Key
- Verified: 2026-07-16

### OpenAI API access in China: SDK migration and troubleshooting
- URL: https://docs.aifast.club/en/providers/openai-api/
- Category: Quick Start
- Summary: Replace the OpenAI SDK Base URL, query the real model ID, and handle /v1/v1, 401, 429 and API compatibility issues.
- Keywords: OpenAI API access in China, OpenAI API gateway, OpenAI Base URL, OpenAI SDK
- Verified: 2026-07-16

### Gemini API access in China: OpenAI-compatible calls and checks
- URL: https://docs.aifast.club/en/providers/gemini-api/
- Category: Quick Start
- Summary: Query real Gemini model IDs, complete text calls, and verify multimodality, streaming output, and stability on a case-by-case basis.
- Keywords: Gemini API access in China, Gemini API gateway, Gemini OpenAI Compatible, Gemini API Key
- Verified: 2026-07-16

### OpenAI Compatible Base URL Online Checker
- URL: https://docs.aifast.club/en/tools/base-url-checker/
- Category: Troubleshooting
- Summary: Check HTTPS, duplicate /v1 segments, complete endpoints, and final request paths to identify /v1/v1 and 404 errors quickly.
- Keywords: Base URL checker, /v1/v1, OpenAI Compatible 404, chat/completions
- Verified: 2026-07-16

### LLM API Token Cost Calculator
- URL: https://docs.aifast.club/en/tools/api-cost-calculator/
- Category: Models and Cost
- Summary: Estimate total API cost from current model prices, input and output tokens, task volume, and the failed-retry rate.
- Keywords: API cost calculator, Token cost, Million Token Price, Failure retry cost
- Verified: 2026-07-16

### OpenAI-compatible API quick start
- URL: https://docs.aifast.club/en/guides/openai-compatible-api/
- Category: Quick Start
- Summary: Use curl, Python and Node.js to complete the first call and troubleshoot 401, model not found and /v1/v1.
- Keywords: OpenAI Compatible, Base URL, API Key, Python, Node.js
- Verified: 2026-07-18

### AIFast 3-minute quick start
- URL: https://docs.aifast.club/en/guides/quick-start/
- Category: Quick Start
- Summary: Register, create an API key, query live model IDs, and send your first request in the fewest steps.
- Keywords: AIFast, API Tutorial, Model list, First API call
- Verified: 2026-07-12

### LLM API streaming and SSE integration guide
- URL: https://docs.aifast.club/en/guides/streaming-api-sse/
- Category: Quick Start
- Summary: Validate streaming responses with curl, Python and Node.js and troubleshoot proxy buffering, interruptions and missing usage.
- Keywords: Streaming output, SSE, stream true, Python, Node.js
- Verified: 2026-07-12

### LLM API Pre-production Checklist
- URL: https://docs.aifast.club/en/guides/production-checklist/
- Category: Quick Start
- Summary: Verify keys, protocols, timeout and retry behavior, logging, cost monitoring, staged rollout, and rollback readiness.
- Keywords: production environment, Online list, Retry after timeout, Logging and monitoring
- Verified: 2026-07-12

### What is LLM API gateway? Access methods and risk checks
- URL: https://docs.aifast.club/en/guides/ai-api-gateway/
- Category: Quick Start
- Summary: Explain the differences between API gateway, OpenAI Compatible, and unified gateway, and give the protocol, security, and cost checks that must be verified before access.
- Keywords: LLM API gateway, AI API Gateway, OpenAI API gateway, Unified model API
- Verified: 2026-07-12

### How to choose an LLM API gateway: a 12-point test checklist
- URL: https://docs.aifast.club/en/guides/how-to-choose-ai-api-gateway/
- Category: Quick Start
- Summary: Evaluate an API gateway by protocol behavior, model declarations, reliability, token accounting, rate limits, security, billing, and migration cost, using one worksheet to preserve reproducible evidence.
- Keywords: How to choose an LLM API gateway, API gateway evaluation, API gateway selection, OpenAI API gateway
- Verified: 2026-07-15

### Chinese LLM API integration guide
- URL: https://docs.aifast.club/en/guides/chinese-model-api/
- Category: Quick Start
- Summary: Use a unified verification process to access domestic models such as DeepSeek, Tongyi Qianwen, Kimi, Doubao, and GLM, and avoid mistaking the display name for the model ID.
- Keywords: Domestic LLM API, DeepSeek API, Tongyi Qianwen API, Kimi API, GLM API
- Verified: 2026-07-12

### AIFast platform facts, official entrance and citation specifications
- URL: https://docs.aifast.club/en/reference/platform-facts/
- Category: Platform Reference
- Summary: Summarizes official domain names, base URLs, authentication methods, Veridrop independent reports, dynamic information boundaries, and standard expressions suitable for public reference.
- Keywords: AIFast, aifast.club, Platform facts, GEO citations, Veridrop Independent Testing
- Verified: 2026-07-18

### Enterprise LLM API Unified Procurement, Billing and Invoicing Checklist
- URL: https://docs.aifast.club/en/guides/enterprise-ai-api-procurement/
- Category: Platform Reference
- Summary: Plan model coverage, concurrency, project isolation, billing checks, invoicing, incident handling, migration, and acceptance requirements.
- Keywords: Enterprise LLM API, API Procurement, API invoice, Billing reconciliation
- Verified: 2026-07-15

### Is an LLM API degrading model capability? A reproducible test checklist
- URL: https://docs.aifast.club/en/guides/model-api-downgrade-detection/
- Category: Platform Reference
- Summary: Investigate capability degradation using model declarations, token usage, dynamic prompts, SSE, tool calls, and business baselines, while separating route changes from occasional variation.
- Keywords: Capability degradation check, LLM API detection, Capability downgrade, API gateway detection
- Verified: 2026-07-15

### How to investigate model impersonation and route substitution in an LLM API
- URL: https://docs.aifast.club/en/guides/model-api-shell-routing-risk/
- Category: Platform Reference
- Summary: Use protocol metadata, model declarations, dynamic capability probes, and repeated comparisons to identify impersonation or substitution risks without treating a single anomaly as proof of fraud.
- Keywords: Model impersonation check, Route replacement, API gateway verification, Model fingerprinting
- Verified: 2026-07-15

### Can a matching API model field prove the underlying model is authentic?
- URL: https://docs.aifast.club/en/guides/model-field-authenticity/
- Category: Platform Reference
- Summary: Explain what the model field can prove, why a gateway can rewrite it, and how to cross-check it with token usage, capability probes, and repeated tests.
- Keywords: model field, Model authenticity, API metadata, model identity
- Verified: 2026-07-15

### How to read an LLM API gateway check report
- URL: https://docs.aifast.club/en/guides/model-check-report-guide/
- Category: Platform Reference
- Summary: Interpret compatibility scores and pass, inconclusive, fail, and observation signals, with a fair method for comparing and retesting multiple API gateways.
- Keywords: API gateway detection report, Model checking score, API comparison, Capability degradation
- Verified: 2026-07-15

### LLM API comparison test template: results can be reproduced and costs can be verified
- URL: https://docs.aifast.club/en/guides/model-api-comparison-template/
- Category: Platform Reference
- Summary: Fixed the model, parameters, question set and sampling period, and compared the success rate, delay, capability, token and complete task cost of multiple API entries.
- Keywords: LLM API comparison, API gateway evaluation, Model benchmarking, API gateway speed test
- Verified: 2026-07-15

### LLM API Compatibility Matrix
- URL: https://docs.aifast.club/en/reference/api-compatibility/
- Category: Platform Reference
- Summary: Compare Chat Completions, Responses, Anthropic Messages, streaming, tool calls, and multimodal capabilities.
- Keywords: API compatibility, Responses API, Anthropic Messages, Tool Calls
- Verified: 2026-07-13

### Cursor custom API configuration and compatibility check
- URL: https://docs.aifast.club/en/tools/cursor/
- Category: Tool Integration
- Summary: Configure a custom API key, Base URL, and live model ID, then verify the capability boundaries of standard chat and Agent mode.
- Keywords: Cursor, Custom API, OpenAI Compatible
- Verified: 2026-07-18

### Cursor2API common error reports, risk checks and standard API migration
- URL: https://docs.aifast.club/en/tools/cursor2api/
- Category: Tool Integration
- Summary: Differentiate Cursor2API from official custom APIs, troubleshoot output truncation, tool calls and upstream changes, and migrate to standard APIs according to the acceptance form.
- Keywords: Cursor2API, Cursor2API error reporting, Cursor2API migration, Cursor custom API
- Verified: 2026-07-18

### Claude Code custom API configuration tutorial
- URL: https://docs.aifast.club/en/tools/claude-code/
- Category: Tool Integration
- Summary: Understand Claude Code's environment variables, compatibility boundaries, and security configuration methods.
- Keywords: Claude Code, API Key, environment variables
- Verified: 2026-07-15

### Claude Code gateway API acceptance and troubleshooting
- URL: https://docs.aifast.club/en/troubleshooting/claude-code-gateway-checklist/
- Category: Troubleshooting
- Summary: Use a 20-minute checklist to verify Anthropic Messages paths, streaming, tool calls, context, caching, and common 403, 429, and 502 errors.
- Keywords: Claude Code gateway API, Claude Code 502, Claude Code streaming, ANTHROPIC_BASE_URL
- Verified: 2026-07-15

### Codex API gateway configuration tutorial: Custom Provider and Responses API
- URL: https://docs.aifast.club/en/tools/codex/
- Category: Tool Integration
- Summary: Configure a Codex custom provider for the Responses API, set environment variables and model IDs, then verify tool calls with a minimal file-editing task.
- Keywords: Codex API configuration, Codex API gateway, Custom Provider, Responses API
- Verified: 2026-07-18

### Codex gateway API acceptance and troubleshooting
- URL: https://docs.aifast.club/en/troubleshooting/codex-gateway-checklist/
- Category: Troubleshooting
- Summary: Use a 20-minute checklist to verify configuration priority, API keys, Responses paths, streaming, tool calls, context compaction, and 401, 404, 429, and 5xx errors.
- Keywords: Codex gateway API, Codex custom provider, Codex Responses API, Codex 401
- Verified: 2026-07-15

### Configure AIFast in OpenClaw
- URL: https://docs.aifast.club/en/tools/openclaw/
- Category: Tool Integration
- Summary: Add a standalone custom provider, configure API adapter, Base URL, model ID and security authentication.
- Keywords: OpenClaw, custom model, openai-completions, Base URL
- Verified: 2026-07-12

### Configure AIFast in Hermes Agent
- URL: https://docs.aifast.club/en/tools/hermes-agent/
- Category: Tool Integration
- Summary: Configure Base URL, API Key and real model ID using hermes model and custom endpoint.
- Keywords: Hermes Agent, Custom endpoint, config.yaml, Base URL
- Verified: 2026-07-12

### Configure the AIFast API in Dify
- URL: https://docs.aifast.club/en/tools/dify/
- Category: Tool Integration
- Summary: Configure the Base URL, API Key, model type and real model ID, and verify the workflow and knowledge base nodes.
- Keywords: Dify, OpenAI Compatible, custom model, Workflow
- Verified: 2026-07-13

### Embedding, Rerank API and Dify knowledge base access
- URL: https://docs.aifast.club/en/models/embedding-rerank-dify/
- Category: Tool Integration
- Summary: Distinguish chat, embedding, and reranking models, configure a Dify knowledge base, and validate retrieval quality with real questions.
- Keywords: Embedding API, Rerank API, Dify knowledge base, RAG
- Verified: 2026-07-15

### Configure AIFast in OpenWebUI
- URL: https://docs.aifast.club/en/tools/openwebui/
- Category: Tool Integration
- Summary: Add an OpenAI Compatible connection, load a list of models, and troubleshoot address, container network, and streaming output issues.
- Keywords: OpenWebUI, OpenAI API Connection, Custom API
- Verified: 2026-07-13

### Chatbox and Cherry Studio integration guide
- URL: https://docs.aifast.club/en/tools/chatbox-cherry-studio/
- Category: Tool Integration
- Summary: Add an OpenAI-compatible provider and configure its API endpoint, API key, and live model ID.
- Keywords: Chatbox, Cherry Studio, custom supplier, API configuration
- Verified: 2026-07-15

### 401, 429, 502 API error troubleshooting
- URL: https://docs.aifast.club/en/troubleshooting/api-errors/
- Category: Troubleshooting
- Summary: Use HTTP status codes to identify API key, quota, rate-limit, gateway, and upstream model problems.
- Keywords: 401, 429, 502, API errors
- Verified: 2026-07-18

### 401 invalid_api_key and API Key invalid troubleshooting
- URL: https://docs.aifast.club/en/troubleshooting/401-invalid-api-key/
- Category: Troubleshooting
- Summary: Troubleshoot 401 errors by checking request headers, environment variables, the Base URL, the key provider, and configuration overrides. Avoid ineffective retries and key exposure.
- Keywords: invalid_api_key, 401 Unauthorized, OpenAI API Key is invalid, Incorrect API key provided
- Verified: 2026-07-18

### 429 Too Many Requests and API rate limiting troubleshooting
- URL: https://docs.aifast.club/en/troubleshooting/429-rate-limit/
- Category: Troubleshooting
- Summary: Distinguish between frequency, token, concurrency, quota and retry amplification, and use Retry-After, exponential backoff and queue recovery calls.
- Keywords: 429 Too Many Requests, rate_limit_exceeded, OpenAI API 429, API rate limiting
- Verified: 2026-07-18

### 502 Bad Gateway, stream disconnected and SSE disconnection troubleshooting
- URL: https://docs.aifast.club/en/troubleshooting/502-stream-disconnected/
- Category: Troubleshooting
- Summary: Locate 502s, upstream errors, and streaming interruptions with short requests, non-streaming comparisons, SSE events, and layered timeouts.
- Keywords: 502 Bad Gateway, stream disconnected, upstream connect error, SSE cutoff
- Verified: 2026-07-18

### Model not found and /v1/v1 troubleshooting
- URL: https://docs.aifast.club/en/troubleshooting/model-not-found/
- Category: Troubleshooting
- Summary: Identify model ID, 404, and duplicate-version path errors using /v1/models, account permissions, and the full request URL.
- Keywords: model not found, /v1/v1, 404, Model ID
- Verified: 2026-07-18

### API Key Security Usage Checklist
- URL: https://docs.aifast.club/en/troubleshooting/api-key-security/
- Category: Troubleshooting
- Summary: Keep API keys out of repositories, frontend code, screenshots, and logs to reduce leakage risk.
- Keywords: API Key Security, environment variables, Key leak
- Verified: 2026-07-12

### How to choose text, image, video, and retrieval models
- URL: https://docs.aifast.club/en/models/model-selection/
- Category: Models and Cost
- Summary: Select models based on input and output types, latency, cost, and task verifiability.
- Keywords: Model selection, image model, video model, Retrieve model
- Verified: 2026-07-12

### Image generation API integration: requests, results, and quality checks
- URL: https://docs.aifast.club/en/models/image-generation-api/
- Category: Models and Cost
- Summary: Verify image endpoints and output formats, download results safely, compare quality with fixed prompts, and track retries and total cost.
- Keywords: Image generation API, Image generation API, Text-to-image, Picture editing
- Verified: 2026-07-15

### Video generation API: asynchronous tasks, polling and result acceptance
- URL: https://docs.aifast.club/en/models/video-generation-api/
- Category: Models and Cost
- Summary: Build an idempotent task state machine with bounded polling, download results safely, and track quality, failures, and total cost.
- Keywords: Video generation API, Text-to-video, Image-to-video, Asynchronous tasks
- Verified: 2026-07-15

### LLM API cost estimation and usage control
- URL: https://docs.aifast.club/en/models/api-cost-control/
- Category: Models and Cost
- Summary: Estimate end-to-end task costs from token usage, failed retries, long contexts, and tool loops, then set budget safeguards.
- Keywords: API cost, Token usage, cost optimization, Budget control
- Verified: 2026-07-16

## API glossary

### Base URL
The base address used by clients when sending API requests. AIFast's OpenAI Compatible Base URL is https://www.aifast.club/v1; if the client automatically appends /v1, it needs to be adjusted according to the final request address.
- Related guide: https://docs.aifast.club/en/troubleshooting/model-not-found/
### Endpoint
The path after the Base URL to perform the specific action, such as /models, /chat/completions, or /responses. The request body and return structure may be different for different endpoints.
### API Key
A secret used to identify an account and authorize requests. Store it in server-side environment variables or a secrets manager, never in frontend code, public repositories, screenshots, or public logs.
- Related guide: https://docs.aifast.club/en/troubleshooting/api-key-security/
### Bearer Authentication
Common HTTP authentication methods. The request header is usually written as Authorization: Bearer YOUR_API_KEY; adding Bearer repeatedly or missing spaces may result in 401.
### Model ID
The machine-readable identifier that needs to be filled in the model field in the API request is not necessarily equal to the Chinese name or model series name on the web page. The real values ​​available for the current account should be obtained through the console or /v1/models.
- Related guide: https://docs.aifast.club/en/troubleshooting/model-not-found/
### OpenAI Compatible
Indicates that the API is compatible with part of the OpenAI SDK's capabilities in terms of address, authentication, or request structure. This does not mean that all models, endpoints, tool calls, and multi-modal functions are completely consistent.
- Related guide: https://docs.aifast.club/en/guides/openai-compatible-api/
### Chat Completions API
A common text generation API that organizes conversation content in messages arrays. Before accessing, you still need to confirm whether the target model supports extended capabilities such as streaming output, tool calling, and image input.
### Responses API
Use input, output, and event streams to organize the API form of requests and responses. Clients such as Codex may rely on this API, and full compatibility cannot be judged just by the successful call of Chat Completions.
- Related guide: https://docs.aifast.club/en/tools/codex/
### Server-Sent Events
A mechanism by which the server sends events in segments over a persistent HTTP connection. LLM streaming output often uses SSE, and the client needs to parse the data field block by block and handle connection interruptions.
- Related guide: https://docs.aifast.club/en/guides/streaming-api-sse/
### Tool Calling
The model returns structured parameters, and it is up to the application to decide whether to execute a function, search, file, or other external tool. The success of ordinary text does not mean that the tool call link is necessarily compatible.
### Token
The unit of measurement used by the model when processing text. Input, output, cache and inference tokens may be counted in different ways. The actual usage should be based on the response usage, console bill and price page.
- Related guide: https://docs.aifast.club/en/models/api-cost-control/
### Context Window
The total capacity boundary for input, history messages, and output that can be processed by a single request. Exceeding model or compatibility layer limits may return 400, truncate content, or cause significant increases in latency.
### Rate Limit
Limits set by the service on request frequency, concurrency, or usage. After receiving a 429, you should first check quota and concurrency before performing a capped exponential backoff.
- Related guide: https://docs.aifast.club/en/troubleshooting/api-errors/
### Timeout
The request exceeded client allowed time during the connect, read, or total task phase. Streaming generation and Agent tool tasks usually require separate read timeout and total task duration settings.
### Exponential Backoff
A strategy that gradually increases the retry interval, such as waiting for 1, 2, 4 seconds and setting a maximum number of times. Suitable for some 429, 5xx and transient network errors, not suitable for authentication or parameter errors.
### Request ID
An identifier used to locate a single request. When debugging, the request ID, time, model ID, status code, and desensitized error text should also be recorded.
## Frequently asked questions

### Where is the official AIFast Telegram community?
The current official AIFast Telegram community is https://t.me/+WYrmge-lYRFhOTFl. Verify the link again at docs.aifast.club/contact/ or the official GitHub profile. Never send API keys, verification codes, or payment information to unfamiliar accounts.

### What is AIFast's OpenAI Compatible Base URL?
Clients that require the OpenAI Compatible Base URL usually fill in https://www.aifast.club/v1. If the client automatically appends /v1, the root domain name should be filled in based on the actual request log to avoid /v1/v1.

### How to confirm that the API Key, domain name and authentication link are available?
First carry Bearer Token to request /v1/models. When successful, a model list response containing a data array is usually returned, indicating that the basic authentication link is normal; returning 401 should check the Key and request header; returning HTML usually indicates that the address has not entered the API route.

### Where should the model name be copied from?
Use the real model ID returned by the console or /v1/models. Do not use the web page title, Chinese alias or manufacturer name directly as the model parameter. Model supply and open status will change and are subject to real-time results.

### Does being compatible with the OpenAI API mean that all features are compatible?
Doesn't mean. Chat Completions, Responses API, Streaming Events, Tool Calls, Image and Video APIs are different capabilities. A successful basic chat can only prove that the current request is available, but cannot prove that the Agent or multi-modal functions are fully available.

### Can Claude Code use OpenAI Compatible addresses directly?
It cannot be directly inferred. Claude Code uses Anthropic Messages semantics and requires the service to explicitly provide Anthropic-compatible entries and configure ANTHROPIC_BASE_URL and authentication variables according to official requirements.

### What capabilities are required for Codex to access third-party APIs?
The current Codex custom provider configuration uses the Responses API. In addition to base_url, env_key, and model ID, compatibility services also need to properly handle Responses API and tool call events; Chat Completions alone are usually not enough.

### After the Cursor fills in the custom API Key, will all functions use this API?
uncertain. Cursor official description says that custom keys are mainly used for standard chat models, and some special functions may continue to use Cursor’s own models. Settings may also vary by version and provider.

### How should I fill in the Base URL when Dify connects to AIFast?
Vendors supporting OpenAI Compatible custom endpoints usually fill in https://www.aifast.club/v1. If the plug-in used will automatically append /v1, the root domain name should be filled in according to the final request log to avoid /v1/v1. Model IDs should be copied from /v1/models returned results.

### What should I do if OpenWebUI is configured successfully but the model list is empty?
First request /v1/models in the server or container where OpenWebUI is located, check the API Key, DNS, certificate and network connectivity; then check whether /v1 is repeatedly appended to the connection address. Just because the host is accessible does not mean that it is also accessible inside the container.

### Chatbox or Cherry Studio connection test is successful, why can’t I still chat?
Connection tests may only verify domain names, certifications, or model lists. You should also confirm that the model selected in the session is consistent with the added model, that the model ID comes from /v1/models, that the final request goes to /v1/chat/completions, and that capabilities such as images and tool calls should be independently verified.

### What should I check first for 401, 429 and 502?
401 first checks Key, Bearer request headers and environment variables; 429 checks concurrency, frequency, balance and model busyness; 502 first uses short requests, turns off streaming output, and distinguishes upstream exceptions, timeouts and protocol incompatibilities.

### Why does model not found appear?
Common reasons are that the model ID is misspelled, a display name is used, the model is not open to accounts, the API type does not match, or the client replaces the custom model name. Query /v1/models first and then check the request log.

### How should API Key be saved?
Use environment variables or key management services, and don't write front-end code, Git repositories, screenshots, and public logs. Different devices, projects and environments use independent keys to facilitate statistics, quotas and revocation.

### Will the models and prices in the documentation remain the same?
No. Model offerings, names, prices, context, and API capabilities are all subject to change. The tutorial only explains the verification method. The final information will be subject to the real-time return of the AIFast console, model price page and API.

### What are the minimum tests required before production goes online?
At a minimum, test short requests, streaming output, timeouts, 429 backoffs, error logs, real model IDs, usage statistics, and key revocation. When Agent is involved, tool calls and file operations must be tested separately.

### Why does it still return once after setting stream=true?
First use curl -N to directly request the origin site. If the terminal can display blocks one by one, it is usually caused by buffering in the application framework, reverse proxy, CDN or front-end reading logic; if the origin site also returns all at once, you should confirm whether the target model and API support streaming output.

### How to estimate the true cost of an AI task?
Input usage, output usage, failed retries, and all requests generated by the Agent tool loop should be counted, rather than just the final successful one. The unit price and magnification of the model are subject to the real-time display on the price page and console.

### How many times should a 429 or 5xx be retried?
There is no fixed number of times that applies to all businesses. Retry-After should be read (if present), use exponential backoff with random jitter and set the maximum number; configuration errors such as 400, 401 and model not found should not be automatically retried.

### What should you verify first when choosing an LLM API gateway?
Use a temporary limited key to verify the live model list, a minimal text request, the response model field, usage, streaming, and required business capabilities. Then check rate limits, billing details, key management, and migration options. Do not decide from homepage model names, one speed test, or the lowest unit price alone.

### How can you fairly compare two LLM API gateways?
Except for the Base URL and API Key, keep the model ID, prompt words, temperature, maximum output length, timeout, and question set consistent; repeat the test in a similar period, and record the success rate, P50/P95 delay, token, key capabilities, and complete task cost respectively.

### If the model detection score is high, can it prove that the underlying model must be an official model?
cannot. Black box detection can only check whether the protocol, model declaration and behavior sample are consistent, and cannot prove the identity of the underlying model based on a single result. Comprehensive judgment should be made based on service provider disclosure, request records, multi-period retesting and real business baselines.

### Should I use the official API Key when testing other API gateways?
Not recommended. Temporary, low-limit, independent Keys that can be revoked at any time should be created and rotated or deleted immediately after testing; do not submit production keys, user data, internal prompt words, and undesensitized files.

## Reliability rules

- Prefer current official client documentation for configuration fields.
- Use HTTP standards when interpreting methods, status codes, and retry behavior.
- Confirm AIFast endpoints, authentication, models, prices, and capabilities through the current API reference, console, and live responses.
- Do not present a dynamic model catalog, price snapshot, or client interface as a permanent commitment.
- Platform facts: https://docs.aifast.club/en/reference/platform-facts/
- API compatibility matrix: https://docs.aifast.club/en/reference/api-compatibility/
- Editorial policy: https://docs.aifast.club/en/about/