Thinking Machines: Inkling Performance
Try Inkling on us. Starter credit covers your first requests, then one key reaches all 3 provider routes with automatic failover.
thinkingmachines/inkling
Measured performance
Continuously sampled p50/p95 time-to-first-token (TTFT), effective throughput, and success rate for Thinking Machines: Inkling. Effective throughput uses provider-reported output tokens over complete request time. Unsupported route and probe-configuration rows are separated from provider downtime, and no prompt or output content is stored.
| Provider | p50 TTFT | p95 TTFT | Effective throughput | Uptime | Config excluded | Availability samples |
|---|---|---|---|---|---|---|
| thinkingmachines | 1474 ms | 2221 ms | — | 100.00% | 1 provider_error |
9 |
| together | 1788 ms | 1788 ms | — | 11.11% | 14 provider_error |
9 |
| databricks | 3293 ms | 3293 ms | — | 100.00% | 3 unsupported_route |
1 |
Full provider & model leaderboard.
3 routes.
More routes give the auto router more room to fail over around provider 429 and 5xx responses.
Gateway overhead is measured separately.
Public status separates TLS/health overhead from full model latency so slow LLMs do not inflate the router metric.
Metadata rollups.
Status samples store latency, outcome, provider, model, route, cost, and region metadata only.
View public status or inspect provider routes.