Key facts
| Fast free tier | plugsky-lite — the speed-focused free model |
| Free reasoning tier | plugsky-micro — adds reasoning on the free plan |
| Fast paid tiers | minimax, tiny and coder-fast for high-volume turns |
| Vision | plugsky-vision-fast for quick image and screenshot triage |
| Metrics to watch | Time to first token for streaming, plus total completion time |
| Context class | 128K-class windows on current models; live limits are published per model |
| Free plan | plugsky-micro and plugsky-lite, no card required |
| Product status | Live |
TL;DR
- plugsky-lite is the free speed pick; plugsky-micro trades some speed for reasoning.
- minimax, tiny and coder-fast are the paid high-volume fast tiers.
- Measure time to first token, not just total request time.
- Stream responses so users see progress while the model finishes.
- Route slow, complex requests away from the fast path instead of upgrading everything.
How it works, step by step
- Define a latency budget per surface: chat, autocomplete and agent step.
- Measure time to first token and total completion time for each candidate model.
- Test with your real prompt lengths — short prompts hide slow paths.
- Pin the fastest model that passes quality per surface and keep a stronger default for complex requests.
- Stream responses so the interface feels immediate.
- Re-test after model or routing changes, and check the status page during incidents.
Try it yourself
What actually makes a response fast
Model size is only one factor. Time to first token is driven by prompt processing and queueing; total completion time also depends on how many tokens the model generates and whether it streams. Routing, region and current load matter too, which is why vendor latency tables rarely match production.
Three levers produce most of the speed users perceive:
- Shorter prompts: retrieve and trim context instead of sending everything.
- Streaming: render tokens as they arrive so the interface responds immediately.
- Right-sized models: keep routine traffic on fast tiers and escalate only when needed.
Choosing from the fast tiers
On the free plan, plugsky-lite is the natural default for short chat, classification and extraction, while plugsky-micro gives you more reasoning when the extra time is acceptable. In the paid catalogue, minimax, tiny and coder-fast are the high-volume fast tiers, and coder-fast keeps agent edit loops moving.
For visual work, plugsky-vision-fast targets quick image and screenshot triage rather than deep visual reasoning. Feature flags, context windows and the engine serving each model are listed on the live model card at /models.
How to measure latency honestly
Run your own test with production-shaped prompts and report distributions, not a single average. Record time to first token and total completion time separately, and repeat at realistic concurrency — a model that looks fast in isolation can queue badly under load.
Use the API latency tester for a quick baseline, then track latency in production dashboards alongside quality and cost. If a fast tier fails quality checks, move that task to a stronger model instead of increasing retries, which would multiply both latency and cost.
Honest comparison
| Surface | Free speed tier (lite) | Fast paid tier (minimax, tiny) | Workhorse (pro) |
|---|---|---|---|
| Simple chat and FAQ | Best fit | Strong | Fine |
| Streaming user experience | Fast first tokens | Fast | Good |
| Agent edit loops | Good for short steps | Best cost per step | Use after failures |
| Classification at volume | Best fit | Strong | Overkill |
| Complex requests | May need escalation | May need escalation | Best fit |
Frequently asked questions
Which Plugsky model is fastest?
plugsky-lite is the speed-focused free model, with plugsky-micro close behind when you want more reasoning. On paid plans, minimax, tiny and coder-fast target high-volume fast turns. Measure on your own prompts before deciding.
Does streaming reduce latency?
Streaming does not shorten total generation time, but it sharply improves perceived latency because the first tokens arrive while the rest are still being generated.
Can I use a fast model for free?
Yes. The free plan includes plugsky-micro and plugsky-lite with no card required, so you can benchmark both against your real prompts at no cost.
How do I measure time to first token?
Send a production-shaped request with streaming enabled and timestamp the arrival of the first content chunk. Compare that with total completion time across several runs and concurrency levels.
When should I use a slower, stronger model?
When the fast tier fails your quality check: multi-step reasoning, long documents or high-stakes answers. Route those tasks to a stronger model instead of retrying the fast one.
Is there a vision option on the fast path?
Yes — plugsky-vision-fast is built for quick image and screenshot triage. Check the model catalogue for current vision capability flags.
How is pricing structured?
Self-serve plans are flat monthly with fair-use usage rather than per-token billing, so fast-tier traffic stays predictable. See the live pricing page for current plans.
Is there a trial for the paid tiers?
Yes — a 14-day full-access trial lets you test paid fast tiers on your own workload before committing.