OpenAI compatible API · Attested · Public status
Thinking Machines: Inkling vs DeepSeek: R1 0528
Compare Thinking Machines: Inkling and DeepSeek: R1 0528 by providers, context, price, and TrustedRouter route support.
Onebase URL to migrate
100sof models and routes
Noneprompt logs by default
Compare routesProviders, price, context, and policy posture in one view.
Use auto when uptime mattersKeep a primary model and let fallback handle provider failures.
Same API shapeUse the OpenAI client and set the model you want.
Practical read
DeepSeek: R1 0528 has the lower cheapest prompt+completion route on TrustedRouter. Thinking Machines: Inkling has more provider fallback routes, while Thinking Machines: Inkling has the larger context window. Current TrustedRouter probes show DeepSeek: R1 0528 with the lower p50 TTFT.
$5.3025/1MThinking Machines: Inkling cheapest route
$2.7825/1MDeepSeek: R1 0528 cheapest route
5994 msThinking Machines: Inkling measured p50 TTFT
4269 msDeepSeek: R1 0528 measured p50 TTFT
Thinking Machines: InklingDeepSeek: R1 0528
Model id
thinkingmachines/inklingdeepseek/deepseek-r1-0528
PublisherTogetherDeepSeek
Context524,288 tokens163,840 tokens
Provider routes55
Cheapest route$5.3025/1M$2.7825/1M
Privacy posturehas ZDR routeprovider posture varies
Modes
chat
chat
Thinking Machines: Inkling routes
Production choice
Pick a default model. Keep fallback enabled.
TrustedRouter is useful when you know the model you want, but still need provider rollover, budget limits, usage records, and a prompt path you can verify.
OpenAI clientPython
client = OpenAI(
base_url="https://api.trustedrouter.com/v1",
api_key="sk-tr-v1-..."
)
response = client.chat.completions.create(
model="thinkingmachines/inkling",
messages=messages,
)