# Kyma API

Source: https://sonpiaz.com/projects/kyma

Gives agent builders one key for a hundred models, with uptime measured rather than claimed.

Status: Live
Started: 2026-04
Updated: 2026-09-12
Tier: main

## The problem

Anyone building on models hits the same wall twice. Availability comes first: one vendor having a bad hour takes your product down with it, and the uptime number on the page is a marketing claim nobody computed. Billing comes second: every model arrives with its own key, its own invoice and its own subscription to remember.

## The approach

One key and one OpenAI compatible endpoint, with failover that retries the same model on another route before it gives up. The uptime number is computed from Kyma's own served requests, not from a vendor's status page, and it is published per model next to the price. The trade is honest: one vendor bought direct will usually list cheaper than Kyma.

## Where it is now

Live since 2026-04-04 with 102 models on one endpoint, a hosted MCP server, and SDKs on npm and PyPI. The last month went into reliability rather than catalogue size: an audio contract that refuses a bad request before anyone is billed, and routing that demotes a route which cannot serve instead of letting it become primary. Revenue is real and small, and the binding constraint is that almost none of it is attributable to a channel yet.

## What happens if this works

One key should cover the tools an agent needs, not just the models: research, enrichment and voice behind the same endpoint and the same bill. And if buyers really choose on reliability, every gateway will publish per model uptime within three years, at which point an unmeasured 99.9 percent reads the way a missing status page reads today.

## Evidence

- An internal audit on 2026-09-08 found one model advertising 99.6 percent uptime against 74.0 percent measured, and 32 of 70 published prices wrong. Both were corrected from served request logs
- [102 models on one endpoint, each carrying a measured 30 day uptime rather than a claimed one](https://kymaapi.com/models)
- [Every chat model probed every 6 hours under one uptime definition, published on the status page](https://kymaapi.com/status)
- [3.19 billion tokens across 257,882 requests from 2,927 developers since 2026-04-05](https://kymaapi.com/rankings)
- 18,637 requests hit an upstream failure and still returned an answer; lifetime success 97.58 percent
- 68 paying customers since launch, 8 of them in the trailing 30 days

## Notes

Kyma started from a boring failure. A coding agent running against a single provider would stop
mid task because that provider was rate limiting, or down, or had quietly renamed a model. The fix
each time was the same shape: add another account, add another key, add another branch of retry
code. After the third one it stopped being a fix and started being the product.

So the routing came first and the catalogue came second. A request for a model tries that model on
another route before it tries a different model, and it tells the caller what happened in the
response headers. Over the lifetime of the service that has turned 18,637 failed upstream calls
into answers the caller never had to know about.

The part that is harder to copy is the measurement. Every gateway in this category advertises
99.9 percent uptime and none of them say how they counted it. Kyma counts a success only when the
model that was asked for is the model that answered, and puts the resulting number on the public
page next to the price.

That check is worth something only because it keeps catching Kyma itself. In September it found a
model whose page claimed 99.6 percent while the logs said 74.0, and 32 of 70 prices that were
simply wrong. A number that has never embarrassed the person publishing it is not being measured.

What it has not solved is attribution. The service is reliable and the economics work per request,
but not one of the paying customers has a recorded signup source, which means there is no way yet
to tell which channel is worth spending on. That is the honest state as of September 2026.

## Links

- [site](https://kymaapi.com)
- [docs](https://docs.kymaapi.com)