Question 1

Do I have to change my code?

Accepted Answer

No. Kumo speaks the OpenAI API for the connected text endpoints. Point your existing SDK’s base URL at https://api.kumorouter.com/v1, swap in your Kumo key, and keep the rest of your chat/completions-style code

Question 2

How are you 30–50% cheaper — what’s the catch?

Accepted Answer

No catch, and no knockoff models: it’s the same GPT, Claude and Gemini, billed through Kumo. Kumo automatically optimizes what you pay per call — the kind of work most teams never get around to doing themselves — and passes the saving straight into your effective rate. Net effect is 30–50% off list, and you see the exact rate before you spend

Question 3

Which models are available?

Accepted Answer

A curated catalog spanning frontier, mid-size, and fast models — GPT-class, Claude-class, and Gemini-class — for chat, responses and Anthropic messages, all behind one endpoint with consistent request and response shapes

Question 4

How does billing work?

Accepted Answer

Pay-as-you-go, per token, from one prepaid balance — no plans, no seats, no minimums. Top up from $2; each call draws down at the rate shown for that model (30–50% below list). The dashboard shows consumption and remaining balance in real time, with spend alerts and hard caps. Spent tokens are not refunded; an unused balance can be refunded upon written request (Public Offer, Section 10)

Question 5

Is my data used for training?

Accepted Answer

Never. Prompts and completions are not used to train models, and we don’t log prompt content — only the usage metadata needed for billing

Question 6

What happens if a provider goes down?

Accepted Answer

Requests stay on the selected provider; transient upstream errors surface as a contract-shaped 502, so you retry or switch providers as needed

Question 7

Can I run production agents and automations on Kumo?

Accepted Answer

Yes — it’s built for it. Point every agent at one OpenAI-compatible endpoint, give each agent or module its own scoped key, and set hard daily and monthly caps so a retry loop can’t drain the balance. Agents and automations burn millions of tokens, so the 30–50% lower rate compounds — and you watch spend per key live in the dashboard

Question 8

How do I pay — do I need a VPN or a foreign card?

Accepted Answer

No VPN and no foreign card. Top up in rubles with a local card or SBP. The same balance then spends across every model behind one key, with the exact per-model rate shown before you spend

Question 9

Can my model get swapped for a cheaper one?

Accepted Answer

No. You ask for a model ID, you get that exact model — pin it and it’s guaranteed, no silent substitution. Responses are the provider’s, verbatim, and every call reports which model served it. The saving is in the rate, never in a quietly weaker model

Question 10

Isn’t a gateway in front of every call a single point of failure?

Accepted Answer

Kumo adds roughly 30–60ms p50 of overhead (under 120ms p99) on top of the model’s own latency; public status history will be connected after the telemetry feed. If Kumo can’t serve a request, it returns a contract-shaped 502, and you can always point your base URL straight back at the provider in one line

Question 11

How do top-ups work?

Accepted Answer

You top up one prepaid balance — manually or with auto-recharge (set a threshold and a cap). Every call draws from it at the per-model rate you see before you spend. Unused balance remains spendable while your account stays active — and can be refunded upon written request (Public Offer, Section 10)

Question 12

Refunds and support?

Accepted Answer

Spent tokens are not refunded; an unused balance is considered for refund upon written request under Section 10 of the Public Offer. Your tokens are not zeroed early: they remain spendable while your account stays active. Support is community plus email with next-business-day response, on a 99.9% uptime target; teams with committed volume get a dedicated contact

Question 13

What are the rate limits and concurrency?

Accepted Answer

Today your throughput is bounded by your balance and per-key quota rather than a fixed per-second limit, so there’s no separate rate-limit tier to manage. Need a guaranteed floor for a bursty workload? That’s exactly what the committed-volume / team plan is for — talk to sales

Question 14

Can your rates change? How much notice do I get?

Accepted Answer

Effective rates track the underlying provider list prices — when a lab cuts a price, yours drops too. If a rate ever has to rise we publish it in advance in the dashboard and by email, and committed-volume plans lock your rate for the term. You always see the exact per-model rate before you spend

Question 15

What happens to my prepaid balance if something goes wrong with Kumo?

Accepted Answer

Purchased tokens remain spendable while your account stays active and are not zeroed early; an unused balance can be refunded upon written request under Section 10 of the Public Offer. At larger volumes we agree the terms with you individually, in writing, before you pay

Question 16

Who’s behind Kumo? Is it a real company?

Accepted Answer

Kumo is built and run by a small, named team that answers directly — no reseller call centre in between. A full team page is coming; until then, reach us at sales@kumorouter.com or on Telegram and we’ll answer any due-diligence question, including who operates the gateway and how payments are handled

Question 17

What if something breaks at 3am?

Accepted Answer

If a provider error surfaces, you get a contract-shaped 502 and can switch providers directly. For Kumo-side issues, support is community plus email with a next-business-day target today; 24/7 paging and a status page with real history are landing in upcoming releases. Teams on committed volume get priority routing and a dedicated contact

Question 18

How many keys can I have?

Accepted Answer

As many as the work needs — one per project, one per agent, one per machine. Keys are issued and revoked in the console, and a revoked key stops being a credential the platform accepts

Questions, answered