Auriko
One OpenAI-compatible endpoint in front of a dozen providers, routing each request to whichever is cheapest.
Highlights
- One OpenAI-compatible endpoint across 12-plus model providers as a drop-in replacement
- Cost-aware routing that weighs price, cache behavior, latency, and reliability per request
- Zero markup on provider prices, with pass-through billing
- Bring-your-own-key support for using your own provider accounts
- Real-time observability plus per-workspace and per-key budgets and spend alerts
- Automatic failover and redundancy across a global edge network
- Broad agent-framework support including the OpenAI and Claude agent SDKs, LangChain, and CrewAI
- A sandbox playground and full API reference for quick evaluation
External link — opens auriko.ai in a new tab. Auriko is a third-party product; we are not affiliated with it.
About Auriko
What it is
Auriko is an LLM gateway: a single OpenAI-compatible endpoint sitting in front of more than a dozen model providers, routing each request by price, cache behaviour, latency and reliability. Because it is drop-in compatible with the OpenAI SDK, an existing integration points at it with a changed base URL. It adds observability, budgets and spend controls, and passes provider pricing through without a markup.
Why it's different
Two things matter here. Drop-in compatibility means adoption is a configuration change rather than a migration, which is the difference between a gateway you try and one you intend to try. Zero markup is a clearer business model than the percentage most gateways take, which quietly misaligns their routing incentives with your bill. The considerations are the ones every gateway carries: every prompt and response passes through a third party, which is a real data-handling decision, and the gateway becomes a single point of failure in front of providers that were already redundant.
How people use it
It is adopted by teams whose model spend has become noticeable and who want routing and budgets without building them. The routine is pointing existing code at it, watching where the requests actually go, and setting per-project budgets so a runaway loop does not produce a surprising invoice. The observability is often what people keep it for, since knowing which feature costs what is hard to reconstruct from a provider's own billing.
Written by the n3os team. We are not affiliated with Auriko.
This listing was written from public information, without Auriko’s involvement. If you own it and something here is wrong — or you would rather not be listed at all — email us and we will correct or remove it.
Get the ones worth knowing about
We write one of these for every tool worth the trouble. Get the new ones, plus what we have found genuinely useful lately.
Your address goes to Buttondown, who send the emails on our behalf. One click unsubscribes, and the list is never sold or shared.