What is AnLink in the current release?
It is a unified access layer for a small set of Chinese models with one OpenAI-compatible request surface, console-issued API keys, trial credit, and usage visibility.
FAQ
Questions developers ask before and during first integration.
This page focuses on the current MVP. It is written to answer the practical questions that show up during registration, key issuance, model selection, and first request validation.
Answers
Common questions
How do I start using it?
Open https://console.anlinkai.com, register, create an API key, then call https://api.anlinkai.com/api/v1/chat/completions with a currently active model code.
Do I need to create separate upstream accounts for every provider?
No. The current product goal is to abstract that away behind one base URL and one access flow.
How does trial credit work?
New accounts currently start with trial credit for integration validation. Balance and recorded cost are visible in the console.
Can I recharge online right now?
Not in the current MVP. Self-service payment and recharge are explicitly outside the first release.
Which endpoint should I use first?
Use POST /chat/completions first. That is the primary path the MVP is designed around.
Should I expose the API key in frontend code?
No. Keep the key in server-side environment variables or backend secret storage.
Why does a model call fail even though my request shape looks correct?
Check three things first: whether the model is active, whether your account still has credit, and whether the key is still active.
Where can I inspect failures?
Use the Usage Logs page in the console and compare request status, token counts, and any recorded error code.
Does the current MVP support streaming?
The recommended validation path is still non-streaming chat completions. Keep the first integration simple.
Can model pricing change?
Yes. During MVP validation, pricing and enabled model exposure may change while routing and support are still being tuned.
Is this ready for enterprise team workflows?
Not yet. Org controls, advanced routing, broad catalog expansion, and public SLA are not part of the current release.