SKTTECH · REGISTER 001 · SIGNAL OPERATIONS FOR AI TRAFFIC
- Sthe switch — every request picks its track in <3ms.
- Kthe key — one credential, one invoice, every provider.
- Tthe table — ranks written by traffic, not marketing.
Every model.
One endpoint.
ONE API · 400+ MODELS · 60+ PROVIDERS · ROUTED IN <3MS
Six levers, all interlocked
route
price, latency, throughput — name the axis, we solve for it.
"model": "qwen/qwen3-max:nitro" "model": "deepseek/deepseek-v3.2:floor"
APPEND A SUFFIX — THE ROUTER HONORS IT ON EVERY CALL
move
the exit is part of the architecture.
"model": "openai/gpt-5.1""model": "deepseek/deepseek-v3.2"
LEAVING IS THE SAME ONE-LINE DIFF THAT BROUGHT YOU IN
agree
one schema, one invoice, four hundred vocabularies.
base_url = "https://api.skttech.io/v1" # the entire migration
YOUR SDK ALREADY SPEAKS THIS DIALECT — SO DO THE FRAMEWORKS
observe
every request leaves an itemized trail.
"cost_usd": 0.000264, "p50_ms": 187, "tokens": 36
THE DASHBOARD ANSWERS “WHAT DID THAT COST?” FIRST
orchestrate
plan B is compiled in, not paged in.
"models": ["anthropic/claude-sonnet-5", "deepseek/deepseek-v3.2", "qwen/qwen3-max"]
AN OUTAGE BECOMES A LOG LINE, NOT AN INCIDENT CHANNEL
forget
the most careful storage is none at all.
ZERO RETENTION IS THE DEFAULT, NOT AN ENTERPRISE UPGRADE
also in the contract — SSE streaming · tool calling · structured outputs · multimodal · prompt caching · provider preferences · team quotas & audit logs
One line changes. Nothing else does.
from openai import OpenAI client = OpenAI( - base_url="https://api.openai.com/v1", + base_url="https://api.skttech.io/v1", api_key=os.environ["SKTTECH_API_KEY"], ) resp = client.chat.completions.create( model="anthropic/claude-sonnet-5", messages=[{"role": "user", "content": "Hello"}], extra_body={ # automatic failover, tried in order "models": ["anthropic/claude-sonnet-5", "openai/gpt-5.1", "deepseek/deepseek-v3.2"], # cheapest provider for the model "provider": {"sort": "price"}, }, )
import OpenAI from "openai"; const client = new OpenAI({ - baseURL: "https://api.openai.com/v1", + baseURL: "https://api.skttech.io/v1", apiKey: process.env.SKTTECH_API_KEY, }); // one SSE dialect across every model const stream = await client.chat.completions.create({ model: "deepseek/deepseek-v3.2", messages: [{ role: "user", content: "Two lines on junctions." }], stream: true, }); for await (const chunk of stream) { process.stdout.write(chunk.choices[0]?.delta?.content ?? ""); }
curl https://api.skttech.io/v1/chat/completions \ -H "Authorization: Bearer $SKTTECH_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "models": ["openai/gpt-5.1", "deepseek/deepseek-v3.2"], "messages": [{"role": "user", "content": "Hello"}] }'
Change one line, swap one key — nothing else in your codebase moves. LangChain, Vercel AI SDK, and LlamaIndex come along without being told.
Sign up
Takes an email, not a card. Your account arrives with $1 of routing credit already on it.
Top up
Credits, not subscriptions. Major international cards — wire transfer and invoicing for enterprises.
Get your key & go
Point base_url at api.skttech.io/v1, drop the key in, deploy. The diff above is the entire migration.
Watch a request make up its mind
A model going down should be a fact about the weather, not a fact about your product. The router treats it that way: noticed in milliseconds, rerouted in under fifty of them, billed only where it succeeded.
sample data · live metrics wire in at launch
The table your traffic writes
anthropic/claude-sonnet-5
7-day Δ +12.4% · coding
deepseek/deepseek-v3.2
7-day Δ +9.1% · reasoning
openai/gpt-5.1
7-day Δ +5.2% · general
| # | model | category | ctx | tokens/wk | blended $/M | p50 | 7-day |
|---|
The ledger and the config
LEDGERCredits, itemized
SEALEDRetention, set to zero
Does it work with the OpenAI SDK I already use?
Yes — full protocol compatibility, not “mostly.” Point base_url at https://api.skttech.io/v1, swap the key, and set model to a vendor/model id like anthropic/claude-sonnet-5. LangChain, Vercel AI SDK, and LlamaIndex run unchanged, because to them this is just an OpenAI-shaped server.
How does pricing work?
Transparent usage-based pricing. Your bill is calculated from the AI inference usage of your requests together with the platform services we provide — routing, high availability, monitoring, billing, and developer infrastructure. Every request is metered and itemized in the console, with no hidden fees. On BYOK traffic, where your vendor bills you directly, the platform charges a metered service fee.
How much latency does the gateway add?
Under 40ms end to end, and the routing decision itself takes under 3ms. For streaming, first-token latency matches going direct — we open the upstream stream and relay it; we do not buffer. Fleet-wide p50 is 187ms, and we publish it.
What are the rate limits?
There is no fixed RPM or TPM on your key. You draw on the platform's aggregated capacity across 60+ providers. When one provider throttles, the router reroutes automatically. Enterprise plans add priority lanes that hold capacity for your traffic.
If a request fails over to a second model, am I billed twice?
No. Only the attempt that returns your response is billed. A provider that errors or times out costs $0, however far into the stream it got. One request, one line item — that is the contract.
What payment methods and paperwork do you support?
Self-serve top-ups take major international cards, each with an e-receipt. Enterprises get wire transfer, proper invoices, and a signed DPA. Purchased credits never expire; there is no monthly minimum.
Who operates SKTTECH?
The SKTTECH platform (skttech.io) is operated by SKTTECH PTE. LTD., a company incorporated in Singapore. The platform is independent — not affiliated with or endorsed by any model provider; model names appear here only to identify routing targets. The paperwork lives at the usual addresses: Terms of Service and Privacy Policy.
Models are weather. The endpoint is climate — build on the part that holds still.
SKTTECH(1) · END OF ENTRY · SEE ALSO: ROUTE(2)