Prices retain their published currencies and billing units below.
Published billing units · original currency · observed 14 Oct 2026
Category
Usage
Rate
Unit
Historical text inference
Input1
CN¥20.00
1M tokens
Historical text inference
Output1
CN¥20.00
1M tokens
Rate conditions
Price in the December 5, 2024 archive, charged on input plus output tokens; conversation history is billable input. Not the final pre-shutdown price and not a current offer. No currency conversion.
International homepage announces API suspension starting August 25 and directs users to the China site. The year is not stated; no exact suspension date is invented. The China alternative is now shut down.
Regions
Host-specific historical service; no current availability or residency guarantee inferred.
Example values such as 1,000 or 1,024 are not advertised maximum output limits.
Prices retain their published currencies and billing units below.
Published billing units · original currency · observed 14 Oct 2026
Category
Usage
Rate
Unit
Historical text inference
Input1
$3.00
1M tokens
Historical text inference
Output1
$3.00
1M tokens
Rate conditions
International documentation still displays this price, but the homepage announces service suspension. Historical reference only, not a current purchasable rate. Input and output are separately priced at the same listed amount.
Retention, training use, regional processing and enterprise terms have not been summarized for this endpoint.
Caching
Caching can reuse earlier input processing. Availability, lifetime and billing depend on the endpoint. A cache hit still generates a new response.
01 / INITIAL INPUTProcess & retain
The system processes eligible input and retains reusable state.
02 / LATER REQUESTCheck available state
Reuse depends on matching input, session state and the cache policy.
03 / CACHE HITReuse & generate
Reusing state can reduce repeated work. Any charges follow the billing rules below.
01.AI China API (historical)
yi-large-fc
Not verified
No model-specific API prompt-cache contract verified.
How it works
Not collected
No model-specific API prompt-cache contract verified.
Minimum reusable input
Not collected
No model-specific API prompt-cache contract verified.
Lifetime & refresh
Not collected
No model-specific API prompt-cache contract verified.
How to enable it
Not collected
No model-specific API prompt-cache contract verified.
Usage fields
Not collected
No model-specific API prompt-cache contract verified.
Billing rules
Not collected
No model-specific API prompt-cache contract verified.
Limits & data boundaries
Not collected
No model-specific API prompt-cache contract verified.
No verified cache rate for this endpoint. An empty rate is not a zero charge.
01.AI international API (suspended)
yi-large-fc
Not verified
No model-specific API prompt-cache contract verified.
How it works
Not collected
No model-specific API prompt-cache contract verified.
Minimum reusable input
Not collected
No model-specific API prompt-cache contract verified.
Lifetime & refresh
Not collected
No model-specific API prompt-cache contract verified.
How to enable it
Not collected
No model-specific API prompt-cache contract verified.
Usage fields
Not collected
No model-specific API prompt-cache contract verified.
Billing rules
Not collected
No model-specific API prompt-cache contract verified.
Limits & data boundaries
Not collected
No model-specific API prompt-cache contract verified.
No verified cache rate for this endpoint. An empty rate is not a zero charge.
What the measurements say
No benchmark observations have been added for this model. We do not turn a vendor description into a performance score.
Latency and throughput depend on the host, request size, reasoning settings and load. There is no measured speed or global usage figure in this record.
The record behind the model
Why it is included
Inferred for this named proprietary API/research variant from the developer’s release description and public weight inventory. Exact weights for this variant were not found. Public Yi, Yi-1.5, Yi-Coder and Yi-VL checkpoints remain excluded; API naming alone does not prove an independently trained base.