What is Wanmo Test, and why we built it
Outages every other week. Premium models silently swapped for cheap clones. We snapped, shipped our own router, and made it paranoid about both. Here is the launch story.
The cheap AI API market has two problems. Providers go down a lot, and some of them quietly forward your request to a weaker model while still charging you for the flagship. Wanmo Test is built to fix both.
Stay online when providers don't
Cheap upstreams are cheap for a reason. They rate-limit, throttle, and drop connections under load. When one degrades, Wanmo Test routes the same request to another healthy provider serving the same model, automatically. Your application doesn't see the outage. You don't rewrite your code. You just keep shipping.
Every model is the real model
Not every gateway serves what it advertises. Some forward premium model names to cheaper substitutes and hope you don't notice. Wanmo Test validates authenticity on every model we list: we probe identity and behavior end to end, and if a provider lies, we cut them. When you call Claude, you get Claude. When you call GPT, you get GPT.
Works in the terminals you actually use
A model is only useful if it works in your tools. We test every model end to end for HTTP completion, streaming, and tool calling. Those three capabilities are what AI terminal harnesses depend on. If a model is in our catalog, it works in Claude Code, Codex CLI, Gemini CLI, and any OpenAI-compatible client. No surprise 'streaming not supported' failures mid-session.
What's next
We ship weekly. Expect more models, tighter health signals driving smarter fallbacks, richer cost and latency dashboards, and deeper integrations with the terminals and IDEs you already live in.
Ready to try it? Grab an API key or browse the model catalog.
Trending models this week
Cheap Claude is often another model wearing Claude's name. Why asking the model proves nothing, why the knowledge cutoff is a guess, and the checks that actually catch a fake.
ai-model-verifier is the engine behind our model tester, published on npm under AGPL-3.0. Give it a base URL, a key and a model and it tells you whether the endpoint serves what it sells, now with thinking-signature and token-billing checks.
Every model page now shows where each provider is based and flags countries without EU data protection safeguards. Here is what the labels mean, how to choose your route, and what else changed.
Comments
Loading comments