Requesty
Sign in

identity

open weights
th

inklingThinking Machines

from /1M in$1.87thinking machines
context66K33K out
providers11 region
endpoints11 region
endpoints
1
regions
1
api
chat
released
July 2026

capabilities 4/8

visionreasoningtoolscachingweb searchjson schemacomputer useimage gen

endpoints

1 / 1 region
Providers serving inkling, with pricing and measured performance. Best value in each column is coloured.
#flags
1Thinking MachinesGlobal66K$1.87$4.68$0.37no-train
provider price, no markupper 1M tokensblank where no qualifying sample

measured

through Nov 2

no measured traffic for this model yet. the endpoints table above carries provider pricing

benchmarks

artificial analysis
Benchmark scores, each normalised to 100
evalScore as a share of 100/100
GPQA Diamond87.2
SciCode47.0
Humanity's Last Exam31.9
Intelligence Index12.5
4 evalsmean44.6

Scores from Artificial Analysis and public leaderboards, normalised to 100. Bar colour is the band, not the rank: green 80 and up, blue 55 and up, amber 30 and up. Benchmarks measure narrow skills, so test on your own workload before committing. Released 2026-07-15.

call it

model=
inkling

requesty routes this id across every provider serving inkling, picking on price and health and failing over automatically. the id stays valid when a provider changes underneath it

Base url is https://router.requesty.ai/v1 for every id here. One key reaches the whole catalog.

quickstart

openai compatible
main.py
from openai import OpenAI client = OpenAI(    api_key="YOUR_REQUESTY_API_KEY",    base_url="https://router.requesty.ai/v1",) response = client.chat.completions.create(    model="inkling",    messages=[        {"role": "user", "content": "Explain quantum computing in one paragraph."},    ],) print(response.choices[0].message.content)

Change the base url, use your Requesty key, set the model to any id in the call pane. Existing OpenAI SDK code needs no other edit, and the same key reaches every other model in the catalog, so switching later is a one-parameter change. Browse all models

notes

reference

Inkling is a large MoE hybrid reasoning model from Thinking Machines with audio and vision input support and a 64K context window.

questions 6

Which providers serve inkling?
inkling is available from 1 provider through Requesty: Thinking Machines. All endpoints share one OpenAI-compatible API and one key, and Requesty fails over between them automatically.
How much does inkling cost?
Pricing starts at $1.87 per million input tokens and $4.68 per million output tokens on the cheapest provider. Prices vary by provider and region; the table above shows every endpoint. Requesty charges exactly what the upstream provider charges, with no markup.
Is inkling open weights?
Yes. inkling is an open-weights model from Thinking Machines, which is why multiple inference providers can host it. Provider choice affects price, latency, and data-privacy terms, all compared above.
What is the context window of inkling?
inkling supports up to 66K tokens of context, with up to 33K output tokens per response. Some providers expose a smaller window; check the per-endpoint context column above.
How do I use inkling with the OpenAI SDK?
Install the OpenAI SDK, set base_url to "https://router.requesty.ai/v1", set your API key to your Requesty key, and set the model to "inkling" or any endpoint id from the table above. The quickstart section shows Python, JavaScript and cURL snippets.
Should I call inkling by its managed id or a provider id?
Use the managed id, "inkling". Requesty picks which of the 1 provider serves each request based on price and health, and fails over when one degrades, so the id keeps working while the routing changes underneath it. Send a provider id like "thinkingmachines/inkling" only when you need one specific deployment and want no failover.

more from thinking machines 1

Other Thinking Machines models
modelcontextfrom /Mproviders
inkling-256k262K$1.871

route inkling through one endpoint

One key for 1 provider on this model and 600+ others. No markup on provider prices, automatic failover, caching built in. Weekly aggregates in the measured pane come from production traffic routed through Requesty, one line per provider on a shared axis. Methodology

inkling1 provider1 endpointsfrom $1.87 /1M inctx 66Kupdated Nov 2