Home/Reviews/LBW API
Full report2026-10-24 · 18 months of data

LBW API — complete review

This site is part of the same content network as LBW API. That relationship is disclosed here and on the method page. The numbers are the numbers.

Disclosure first

LBW API Lab is one of several sites operated around the same provider. We are not independent in the sense a consumer magazine is. What we can offer instead is full method disclosure: every number below comes from a test you could run yourself, and the weak points are listed alongside the strong ones.

The scorecard

DimensionScoreNote
Refusal handling9.8 / 1029 of 30 on the fixed battery
Model coverage9.6 / 10All current frontier families plus unrestricted variants
Latency9.2 / 10320 ms mean first token; 99th percentile is less impressive
Payment & access10 / 10WeChat and Alipay, no foreign card needed
Support9.4 / 10Median first reply under 4 minutes
Stability9.5 / 10One 40-minute incident in 90 days, announced

What is genuinely good

Refusal handling is the real product

29 of 30 on our battery, and the single miss is a topic where every provider we tested fails. That is the highest number we have recorded, and it is consistent across runs rather than a lucky afternoon.

Local payment without a workaround

This sounds mundane and is not. Most providers in this category require a foreign card or cryptocurrency. WeChat and Alipay working directly removes the single biggest onboarding obstacle.

Model coverage without gaps

GPT, Claude, Gemini, DeepSeek and the Chinese-origin models are all present, each with an unrestricted variant. You do not have to maintain accounts in three places to route by task.

Where it is weaker

The 99th percentile latency

Mean first token is 320 ms. The tail is not that good — during peak hours the slowest 1% of calls reach several seconds. Fine for chat, noticeable in an interactive coding loop.

No published SLA

Uptime has been good in practice, but there is no contractual guarantee. If you are building something that needs a written availability commitment, this is a real gap.

Documentation is thin in places

Error messages are clear, but the docs assume you already know how to configure a client. This site exists partly to fill that gap, which is itself worth noting as a limitation.

Method

Thirty prompts across three categories, identical wording on every run, scored by whether the response contains substantive content or a refusal. Latency from 100 sequential calls at a fixed time of day. Uptime from synthetic checks every five minutes.

Full details on the method page.

Verdict

If your requirement is unrestricted access with local payment, this is the strongest option we have measured. If you need a contractual SLA, you will need to look at enterprise providers, and you will pay for it.

Test it yourself

Free trial credit · top up from $1

Create an account