Inkling from Thinking Machines is now available on AI Gateway
By Dillip Chowdary • Jul 20, 2026 • Source: Vercel Blog
According to the Vercel Blog, Thinking Machines has released Inkling, which is now accessible via AI Gateway. Developers can connect to the model within their applications by setting the model parameter to thinkingmachines/inkling using the AI SDK.
Technically, Inkling is structured as a broad generalist model rather than a system specialized for a single domain. Its training covers seven distinct areas: agentic, reasoning, coding, instruction-following, factuality, vision, and audio tasks. Product mechanics also include controllable thinking effort, allowing users to programmatically adjust the model's reasoning intensity.
What shipped
A versioned cut is a contract with anyone who pinned the last one. Inkling from Thinking Machines is now available on AI Gateway should be read as a changelog first and a launch second. If you cannot find the changelog, you do not have enough to upgrade.
According to the Vercel Blog, Thinking Machines has released Inkling, which is now accessible via AI Gateway. Developers can connect to the model within their applications by setting the model parameter to thinkingmachines/inkling using the AI SDK.
What changed for builders
Builders should diff the release notes for APIs, defaults, and removed flags. That list is the migration. Anything not on it is a rumor until it shows up in a follow-up patch.
Technically, Inkling is structured as a broad generalist model rather than a system specialized for a single domain. Its training covers seven distinct areas: agentic, reasoning, coding, instruction-following, factuality, vision, and audio tasks.
How to install or upgrade
Install via the vendor's documented channel. Snapshot config, roll through staging, keep a one-command rollback. Time-box the canary. If the release has no documented rollback, that is the first risk you escalate.
Advertisement
Tech Pulse Daily
Developer Action Items
- ☐ Inventory whether Inkling Thinking Machines available runs in prod, CI, staging, or on laptops before you debate severity.
- ☐ Confirm the vendor's fixed build for Inkling Thinking Machines available from the official advisory, then schedule the patch window.
- ☐ If you cannot patch today, isolate the service, rotate tokens that sat on the affected surface, and raise the logging floor.
- ☐ Record the decision and residual risk so the next on-call does not re-litigate whether you are exposed.
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
Product mechanics also include controllable thinking effort, allowing users to programmatically adjust the model's reasoning intensity. A versioned cut is a contract with anyone who pinned the last one.
Gotchas and compatibility
Gotchas hide in transitive deps, license files, and anything that touches auth or storage. Read those sections twice. Then grep your own repo for the old flag names so you are not surprised in prod.
Inkling from Thinking Machines is now available on AI Gateway should be read as a changelog first and a launch second. If you cannot find the changelog, you do not have enough to upgrade.
What to watch next
Watch the first patch release. If it arrives inside a week, the original cut was not as boring as the announcement implied. Pin to the patch, not the day-zero tag, unless you have a reason.
Builders should diff the release notes for APIs, defaults, and removed flags. Anything not on it is a rumor until it shows up in a follow-up patch.
A 3–5 minute news post is a briefing, not a runbook. Keep Vercel Blog and the vendor's primary page in another tab, quote only what they printed, and write down the single decision this story forces (upgrade, wait, or ignore) before you Slack it to the rest of the team. If you need more than that decision, you want the primary docs or a later engineering deep-dive — not another recap of Inkling from Thinking Machines is now available on AI Gateway.
When you brief someone else on Inkling from Thinking Machines is now available on AI Gateway, lead with the surface that moved and the decision you need from them. Do not paste the whole thread. If you cannot name the surface — API, policy, model, hardware, or commercial terms — you are not ready to brief. Go back to Vercel Blog and the vendor page until you can. That extra ten minutes is cheaper than a wrong upgrade or a missed exposure.
Treat day-one coverage of Inkling from Thinking Machines is now available on AI Gateway as a pointer, not a specification. Vercel Blog is useful for names, dates, and the claim as stated; it is not a substitute for the changelog, the advisory, or the contract clause that actually binds you. If those artifacts are not public yet, wait. Acting on a paraphrase is how teams ship the wrong flag or miss the one dependency that was actually in scope.
Advertisement