Key facts
| Model class | Open-weight GPT-OSS profile in the Plugsky catalogue |
| Best for | Open-model standardisation, reasoning, tool use and long-context tasks |
| Context class | 128K-class window; live limits are published per model |
| Capabilities | Reasoning, streaming, function calling, JSON mode and long-context |
| Pricing tier | Paid-plan model; free plan covers plugsky-micro and plugsky-lite |
| API | OpenAI-compatible /v1/chat/completions — no SDK changes |
| Availability | Served with a backup GPT-OSS upstream; live routing is shown at /models |
| Product status | Live |
TL;DR
- An open-weight GPT-OSS profile for teams with open-model requirements.
- Reasoning, tools and JSON mode on the standard OpenAI-compatible API.
- Routing may serve the profile from a different engine during upstream issues.
- Always read the live card at /models to see the engine currently in use.
- Automatic backup keeps the profile available through incidents.
How it works, step by step
- Check the live card at /models for the engine currently serving plugsky-gpt-oss.
- Confirm your plan can call the model and that its feature flags match your needs.
- Run your prompts through the OpenAI-compatible endpoint with your existing SDK.
- Test reasoning, tool calls and JSON output on representative tasks.
- Compare quality and latency against the open model you use today.
- Switch the model name and keep an alternative configured for critical paths.
- Monitor /models and /status so routing changes are visible to your team.
Try it yourself
What plugsky-gpt-oss is
plugsky-gpt-oss is the GPT-OSS family profile in the Plugsky catalogue. It exists for teams that want an open-weight model posture without running GPUs: same OpenAI-compatible API, same tooling, but the model family is one with publicly available weights. The profile supports reasoning, function calling, JSON mode and long-context inputs.
Platforms route models to the healthiest upstream, so the engine serving a profile can change. The live card at /models always shows the current upstream and should be your reference point when exact model identity matters to your compliance or evaluation process.
When to choose it
Choose plugsky-gpt-oss when an open-weight family is a requirement — procurement policies, portability planning, or a future move to self-hosting — and you want API-level convenience today. It is also a reasonable general model for reasoning and tool use where the benchmark team already standardised on GPT-OSS.
If you simply need a strong default, plugsky-pro or plugsky-plus are the platform workhorses. For long-context work with an open-model bias, compare it with plugsky-llama4 and pick on your own evals.
Routing, quality and cost trade-offs
The honest trade-off with a family profile is that continuous availability sometimes means serving from a same-profile alternative engine. That is good for uptime and bad for strict reproducibility, so measure rather than assume.
- Record the model name and response metadata with eval results so routing changes are detectable.
- Keep a small regression suite and run it after catalogue updates.
- Use JSON mode and schema validation for structured workloads.
- Self-serve plans are flat monthly with fair-use usage — see the live pricing page for current plans.
How to switch to plugsky-gpt-oss
Switching is a model-name change: {"model": "plugsky-gpt-oss", "messages": [{"role": "user", "content": "Plan the migration steps for this module."}], "stream": true} posted to the OpenAI-compatible endpoint.
Run it in shadow mode against your current open-weight deployment, compare on the same prompts, then cut over. Keep the previous model configured as a fallback for critical paths until you are confident in the results.
Honest comparison
| Dimension | plugsky-gpt-oss | Self-hosted GPT-OSS | Proprietary model API |
|---|---|---|---|
| Best fit | Open-weight posture with API convenience | Full control and offline deployment | Maximum managed simplicity |
| Portability | Open family, API-served | You hold the weights and hardware | Weights usually not portable |
| Ops overhead | None | GPU capacity, updates, scaling | None |
| Tools and JSON mode | Supported | You build the serving stack | Varies |
| Model identity | Live upstream shown at /models | Exactly the build you deployed | May change without notice |
| Failover | Automatic backup upstream | You design redundancy | Vendor-dependent |
Frequently asked questions
Is plugsky-gpt-oss free?
No — it is a paid-plan model. The free plan includes two free models, plugsky-micro and plugsky-lite. A 14-day full-access trial is available for paid tiers.
Is it actually open weights?
It is the GPT-OSS family profile, so the model family has publicly available weights. The live /models card shows which engine is currently serving the profile.
Why does the upstream sometimes change?
Continuous availability is maintained by routing to a healthy same-profile engine during upstream issues. The catalogue page shows the current routing.
Does it support function calling?
Yes — reasoning, streaming, function calling and JSON mode are part of the shared OpenAI-compatible surface.
What context window does it have?
It is 128K-class today. The exact live window and output limit are published per model at /models.
Can I move to self-hosting later?
The open-weight family makes that option realistic. Plan for GPU capacity, serving stack and evaluation work if you take that path.
How do I keep results reproducible if routing changes?
Pin your evaluation suite, record model metadata in responses, and re-run the suite after catalogue updates. Treat exact model identity as observable, not assumed.
How is pricing structured?
Self-serve plans are flat monthly with fair-use usage and no per-token billing. See the live pricing page for current plans.