Route difference
The first layer is not brand size. It is user market, protocol entry, model-family coverage, and real call stability.
- Inception: global route, 3 Models
- Liquid: global route, 3 Models
Provider comparison
Inception vs Liquid
Start with the provider route, compare model coverage, then use read-only key checking to verify what is actually callable.
Region
global route / global route
global
Models
3 / 3
56 providers indexed
Inception
Mercury · Mercury 2 · Mercury Coder
Sample models
Liquid
LFM2-24B-A2B · LFM2.5-1.2B-Instruct (free) · LFM2.5-1.2B-Thinking (free)
Sample models
Left provider
Inception
inception
Regionglobal
Models3
Sample models
Mercury
Mercury 2
Mercury Coder
Right provider
Liquid
liquid
Regionglobal
Models3
Sample models
LFM2-24B-A2B
LFM2.5-1.2B-Instruct (free)
LFM2.5-1.2B-Thinking (free)
Comparison summary
How to judge first
Inception and Liquid are both on the global route, so compare protocol, model coverage, and key visibility.
When model coverage is close, move the decision to price, rate limits, interface compatibility, and stability.
In production, one key should reveal provider identity, callable models, balance or quota signals, limits, and risk notes.
Key checking value
A key may expose only part of the models, interfaces, or regions, so the final call must rely on detection results, not the catalog alone.
- Inception: Mercury · Mercury 2 · Mercury Coder
- Liquid: LFM2-24B-A2B · LFM2.5-1.2B-Instruct (free) · LFM2.5-1.2B-Thinking (free)
Procurement and distribution
For procurement, agency, and marketplace listing, provider comparison must end in supply stability, pricing, monitoring, and model updates.
- Do not treat catalog coverage as real sellability.
- Key checking and continuous monitoring are the final commercial loop.