Inkling is an open-weight, multimodal flagship model from Thinking Machines Lab that accepts text, image, and audio input and supports a context window of roughly 1M tokens.
| Provider | Input / 1M | Output / 1M | Cached / 1M |
|---|---|---|---|
| $0.950 | $4.05 | $0.160 | |
| $1.00 | $4.05 | - | |
| $1.00 | $4.05 | - | |
| $1.00 | $4.05 | $0.170 | |
| $1.00 | $4.05 | $0.170 |
Prices updated daily. Last check: Sep 5, 2026
Input, output, and batch rates, plus alternatives, for one provider at a time.
Benchmarks measured Sep 2026. Scores are independent evaluations, not vendor-reported.
Inkling suits workloads that need a large working context and more than one input modality at once: summarizing or querying across very large document collections, analyzing long audio recordings alongside their transcripts, extracting structured data from mixed image-and-text sources, and building agents that call external tools over long-running sessions. Its flagship positioning within the Inkling family makes it the choice for tasks where reasoning quality matters more than per-token cost, while its roughly 2-second time to first token makes it a better fit for batch and background jobs than for latency-critical interactive chat. Because the weights are open, teams with data-residency or on-premise requirements can also evaluate it for self-hosted deployment rather than API-only use.
Pricing varies by inference provider and by pricing type — per-token serverless rates, dedicated capacity, and self-hosted GPU costs all behave differently, and because Inkling is open-weight, multiple providers may host it at different rates. Check the pricing table on this page for current per-provider figures.
Long-context and multimodal work: querying large document sets, processing long audio alongside text, extracting information from images and text together, and driving tool-calling agents. Its ~1M-token context and support for text, image, and audio input are the main reasons to pick it over a smaller model.
Yes — Inkling is released with open weights, so it can be self-hosted in addition to being consumed through hosted APIs. As a flagship-tier model it is compute-intensive, so plan GPU capacity accordingly; our GPU pricing pages can help estimate that side of the cost.
Artificial Analysis measurements put Inkling at roughly 80 output tokens per second with a time to first token of about 2,086 ms. The throughput is workable for streaming long responses, but the two-second first-token delay is noticeable in interactive chat, so latency-sensitive front ends may prefer a lighter model.
Yes. Inkling supports tool/function calling, which allows it to be integrated into agent frameworks, retrieval pipelines, and workflows that require calling external APIs. Exact schema and parallel-call behavior depend on the provider's API implementation.