home
Model and API documentation
Direct answerThis center contains human-reviewed provider positioning, model-family capabilities, protocol semantics, limits, and official sources; live IDs and prices remain in the marketplace.
Updated · Reviewed
What this documentation answers
This site does not duplicate marketplace IDs, prices, or availability. It answers four durable questions: who provides a capability, what a model family officially supports, how a protocol behaves, and how a workload should be designed. Every capability is derived from the official developer sources listed on the page and is technically paraphrased in Chinese and English.
How the four page types work together
Provider pages distinguish model originators, cloud hosts, and local runtimes so third-party models are not attributed to a channel. Model-family pages explain official product lines, modalities, selection, and migration risk. Protocol pages separate gateway calls from upstream-native semantics. Use-case pages cover architecture, evaluation, and safety.
Boundary with the model marketplace
Exact model IDs, current availability, price, and enabled endpoints are runtime state and belong in the model marketplace. Editorial pages never generate quality claims from SKU names and do not remove durable knowledge merely because a model is temporarily unavailable.
How accuracy is reviewed
Every page records publication, substantive update, review date, and official sources. Changing facts such as versions, context, regions, price, and retirement are included only when verifiable and are placed on a review schedule. If an official source cannot be checked reliably, the limitation is stated rather than filled with speculation.
Recommended reading path
Beginners should start with the gateway beginner guide to sign in, select a model, fund the account, create a key, make a first call, and inspect its log. Continue to the AI API quickstart when writing a request. For status codes, interrupted streams, or retry behavior, use the API troubleshooting guide. Then read the relevant model-family and protocol pages, and finish in the model marketplace to confirm the exact IDs, prices, and endpoints currently callable on this site. Production still requires evaluation on your own data, latency budget, safety rules, and failure cases.
Learning path
From first request to production governance
Usage guides
Start with the job to be done
API protocols
Choose the protocol contract
Model families
Compare stable model families
By model provider
Compare providers and platforms
FAQ
What is the difference between the documentation center and the model marketplace?
The documentation center explains providers, model families, API protocols, capability boundaries, and usage. The marketplace shows exact model IDs, prices, and endpoints currently callable on this site. Read the guide first, then confirm live state in the marketplace.
Where should a complete beginner start?
Start with the gateway beginner guide and follow account access, marketplace selection, funding, API-key creation, first call, and log lookup in order. Continue to the AI API quickstart when you are ready to write a request.
Why are model IDs and prices not hard-coded in these guides?
Exact IDs, channel availability, prices, and endpoints change with runtime configuration and would become stale quickly. The marketplace owns those dynamic facts, while the documentation preserves more durable protocol and capability knowledge.
How can I tell whether a documentation page is outdated?
Check its substantive update date, review date, official sources, and stated boundaries, then verify the current model ID and endpoint in the marketplace. When upstream or runtime state has changed, use the latest official page and marketplace state.
兔子API