Thinking Machines: Inkling Small (free)
Inkling Small is an open-weight multimodal mixture-of-experts model from Thinking Machines Lab, with 12B active parameters out of 276B total. It is positioned as the smaller, more efficient member of...
Anyone in the Project can @-mention Thinking Machines: Inkling Small (free) with the team's shared context - pooled credits, one chat, one memory.
Starter is free forever - 1 Project, 100 credits/month, 1 MCP. No card.
Verdict
Best for
- Budget-constrained multimodal prototyping
- High-volume audio transcription experiments
- Long-document analysis without API costs
- Testing workflows before committing to paid models
- Educational projects requiring image and text
Strengths
Zero-cost pricing removes financial friction for experimentation and high-throughput use cases. The 1M-token context window matches premium models like Gemini 1.5 Pro, enabling full-document ingestion or multi-turn conversations without chunking. Multimodal support across text, image, and audio in a free tier is uncommon — most free models cap at text-only or charge per modality.
Trade-offs
No public benchmarks means accuracy is unverified against peers like GPT-4o or Claude. Free models often throttle requests or deprioritize inference speed during peak hours. Proprietary licensing limits transparency into training data and bias mitigation. Without published MMLU or HumanEval scores, you'll need to run your own evals before trusting it in production workflows where correctness matters.
Specifications
- Provider
- thinkingmachines
- Category
- llm
- Context length
- 1,048,576 tokens
- Max output
- 262,144 tokens
- Modalities
- text, image, audio
- License
- proprietary
- Released
- 2026-07-30
Pricing
- Input
- $0.00/Mtok
- Output
- $0.00/Mtok
- Model ID
thinkingmachines/inkling-small:free
Per-token prices show what the model costs upstream. On Switchy your team draws from one shared org credit pool - one plan, one balance for everyone.
Team cost calculator
5 seats · 80 msgs/day
Switchy meters this against your org's shared credit pool - one plan, one balance for everyone.
Providers
| Provider | Context | Input | Output | P50 latency | Throughput | 30d uptime |
|---|---|---|---|---|---|---|
| thinkingmachines | 1049k | $0.00/Mtok | $0.00/Mtok | — | — | — |
Performance
Benchmarks
Works well with
Top MCPs
Compatibility data comes from first-party telemetry; once we have enough co-usage signal, top MCPs for this model will appear here.
How Switchy teams use it
Starter prompts
Summarize Long PDF
Summarize the key findings, methodology, and conclusions from this document. Highlight any novel contributions and note limitations the authors mention.
Transcribe Audio Meeting
Transcribe this audio file and format the output as meeting minutes with speaker labels, action items, and key decisions.
Analyze Screenshot UI
Describe the UI elements in this screenshot. Identify usability issues and suggest three specific improvements for mobile responsiveness.
Compare Two Documents
Compare these two versions and list all substantive changes. Flag any clauses that were removed, added, or modified in meaning.
Generate Test Data
Generate 50 realistic customer support tickets for an e-commerce platform. Vary tone, issue type, and urgency. Output as JSON.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
Review this Python function for potential edge cases. It's supposed to parse ISO date strings but users report crashes on certain inputs.
This function would produce a structured analysis identifying that the parser fails on dates with timezone offsets (like '2024-01-15T10:30:00+05:30'), doesn't handle leap seconds, and raises unhandled exceptions for malformed strings instead of returning None or a default. The model would suggest adding try-except blocks, validating format before parsing, and testing against a suite of edge cases including empty strings, partial dates, and various timezone formats.
With a 1M+ token context window, this model can review entire codebases for patterns rather than isolated functions. The free tier makes it accessible for exploratory debugging sessions, though the absence of public benchmarks means code quality claims remain unverified through independent testing.
I have 40 pages of customer interview transcripts. Extract the top 5 recurring pain points mentioned across all interviews, with supporting quotes.
The model would produce a hierarchical summary listing pain points like 'onboarding confusion' (mentioned in 23/40 interviews) with 2-3 direct quotes per theme, preserving speaker context. It would identify patterns across the full document set, noting frequency and sentiment shifts between early and late interviews. The output would be formatted as a structured list with quote attribution and page references.
The massive context window handles long documents that would require chunking in smaller models. Multimodal support means you could include scanned notes or audio recordings alongside text transcripts. Zero cost removes budget friction for exploratory research work, though synthesis quality depends on the model's reasoning depth.
Generate three variations of this product hero section: one optimistic, one urgent, one technical. Keep the core message but shift tone and vocabulary.
The model would produce three distinct rewrites of the provided copy, each maintaining factual claims while adjusting emotional register. The optimistic version would use aspirational language and future-focused framing. The urgent version would emphasize time-sensitivity and competitive pressure. The technical version would replace metaphors with specifications and add precision qualifiers. Each would be 50-80 words matching the original's structure.
Free access makes this useful for rapid A/B testing ideation without metering anxiety. The model handles image inputs, so you could include mockups for context-aware copywriting. Without benchmark data, it's unclear how this compares to established writing models on nuance and brand voice consistency.
Use-case deep-dives
Free tier for testing conversational flows before production spend
A 4-person product team building a customer support chatbot needs to validate 200+ conversation branches without burning budget on API calls. Inkling Small handles this at zero cost with a 1M token context window—enough to load entire conversation trees, sample tickets, and brand guidelines in a single session. The free tier lets you iterate on prompt engineering and flow logic until you've proven the concept. Once you hit production traffic or need faster response times, migrate to a paid model with known benchmark performance. Use this for proof-of-concept work where cost matters more than cutting-edge accuracy, then graduate to a benchmarked alternative when you're ready to scale.
Zero-cost sandbox for students learning prompt engineering fundamentals
A university instructor teaching 30 students how to build AI workflows needs a model that won't rack up charges during trial-and-error learning. Inkling Small's free pricing and multimodal support (text, image, audio) let students experiment with different input types and prompt structures without budget anxiety. The 1M token context window supports document analysis exercises and multi-turn conversation assignments. No benchmarks means you're trading performance certainty for accessibility—fine when the goal is learning the mechanics, not production output quality. This works until students need to compare model performance or build portfolio projects that require cited benchmark results. For pedagogy at zero cost, it's the right call.
Free model for low-stakes knowledge base queries in small teams
A 7-person startup wants to let employees ask questions about internal wikis and onboarding docs without paying per query. Inkling Small's free tier and large context window handle this: load 500KB of Notion pages and let the team query it throughout the day. The lack of public benchmarks means you can't predict accuracy on complex reasoning, but for straightforward lookup tasks—"What's our PTO policy?" or "Where's the staging server URL?"—free is hard to beat. If you notice wrong answers on nuanced questions or need audit trails for compliance, switch to a paid model with documented performance. For internal-only, low-risk Q&A where budget is tight, this covers the basics.
Frequently asked
Is Thinking Machines Inkling Small good for general text tasks?
Yes, for basic work. With a 1M token context window and zero cost, it handles document summarization, simple Q&A, and draft generation without burning budget. Expect lower accuracy than paid models on complex reasoning or specialized domains. Good for prototyping or high-volume low-stakes tasks where cost matters more than precision.
Why is Inkling Small free when other models charge per token?
Thinking Machines likely subsidizes it to drive adoption or gather training data. Free models typically trade performance for accessibility—expect slower responses, lower benchmark scores, and possible rate limits. If you need guaranteed uptime or production-grade output, budget for a paid alternative like GPT-4o-mini or Claude Haiku.
Can Inkling Small process images and audio reliably?
It supports image and audio inputs, but without public benchmarks we can't verify quality. Free multimodal models often struggle with OCR accuracy, image reasoning, or audio transcription compared to paid options. Test it on your actual use case before committing—if results disappoint, switch to Gemini 2.0 Flash or GPT-4o.
How does Inkling Small compare to other free models like Gemini Flash?
Gemini 2.0 Flash offers proven benchmarks and Google's infrastructure; Inkling Small has no public performance data yet. Both are free, but Flash has documented strengths in coding and reasoning. Choose Inkling if you need the 1M context window specifically, otherwise default to Flash for reliability.
Should I use Inkling Small for customer-facing chatbots?
Only for low-risk interactions. Free models lack the consistency and safety tuning of paid alternatives. If a wrong answer damages trust or costs money, pay for Claude Haiku or GPT-4o-mini instead. Use Inkling Small for internal tools, content drafts, or MVPs where occasional errors are acceptable.
Compare with
More language models
- TypeSafe: Jev Routertypesafe
- Upstage: Solar Mini 4upstage
- Upstage: Solar Pro 3upstage
- Upstage: Solar Pro 4upstage
- Venice: Uncensoredcognitivecomputations
- WizardLM-2 8x22Bmicrosoft
- Writer: Palmyra X5writer
- xAI: Grok 3x-ai
- xAI: Grok Latestx-ai
- Xiaomi: MiMo-V2.5xiaomi
- Xiaomi: MiMo-V2.5-Proxiaomi
- Xiaomi: MiMo-V2.6-Flashxiaomi