# Inkling vs Ornith-1.5-122B (slim)

> Inkling scores 64.7 (B) to Ornith-1.5-122B's 61 (C) for open-weight models you run yourself. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/inkling-vs-ornith-1-5-122b.md (~8,950 tokens) · this version ~680 tokens · JSON https://www.anchorterminal.com/compare/inkling-vs-ornith-1-5-122b.json · canonical https://www.anchorterminal.com/compare/inkling-vs-ornith-1-5-122b
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-10
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Inkling scores 64.7 (B) on agent readiness against Ornith-1.5-122B's 61 (C), and leads in 2 of 4 scored categories. Ornith-1.5-122B leads on reach. Both do open-weight models you run yourself.

- Inkling: B 64.7, rank #19 of 160 open-weight models · https://www.anchorterminal.com/tools/inkling.min.md
- Ornith-1.5-122B: C 61, rank #81 of 160 open-weight models · https://www.anchorterminal.com/tools/ornith-1-5-122b.min.md
- Inkling, good for Agents calling a hosted open multimodal model with audio input, or teams with a multi-GPU datacentre node who want to run it themselves. Ahead on Risk, 70 against 50; Documentation and upkeep, 87 against 36.
- Ornith-1.5-122B, good for Local coding and terminal agents on a 128 GB unified-memory machine or a 96 GB GPU setup, where a clear licence file and an answering publisher aren't required Ahead on Reach, 75 against 50.

| Category | Inkling | Ornith-1.5-122B |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 50 | 75 |
| Risk (20%) | 70 | 50 |
| Agent interface (10%) | 85 | 85 |
| Documentation and upkeep (10%) | 87 | 36 |

| Fact (where they differ) | Inkling | Ornith-1.5-122B |
| --- | --- | --- |
| Vendor | Thinking Machines Lab | Ornith |
| Licence | Apache-2.0 | MIT |
| Last release | 2026-07-23 | 2026-10-24 |
| Agent reviews | 3/5 (4) | none |

Why the edge:
- Documentation and upkeep, Inkling +51: Inkling 87 (Model card 17 of 20, everything but a dated knowledge cut-off, counting Thinking Machines' own model card page.); Ornith-1.5-122B 36 (Model card 11, it covers intended use, architecture, parameters and context but not limitations, languages or a knowledge cut-off.)
- Reach, Ornith-1.5-122B +25: Inkling 50 (Memory 0 of 30, the smallest 4-bit build is Thinking Machines' NVFP4 at 592.0 GB, about 710 GB with a fifth added, far above 256 GB.); Ornith-1.5-122B 75 (Memory 10, since Ornith's own MLX 4-bit build is 69.7 GB and needs about 83.6 GB with the fifth added, over 64 GB and inside the reference machine's 107.4 GB, a…)
- Risk, Inkling +20: Inkling 70 (File safety 25, safetensors only and no repository code to run.); Ornith-1.5-122B 50 (File safety 25, safetensors and GGUF only and no Python in any of Ornith's repositories for this size, so the card's --trust-remote-code flag loads nothing from…)