Key facts
| Agent stack | Chat completions, function calling and embeddings are live |
| Use cases | Player support, live-ops drafts, moderation triage, telemetry summaries |
| Moderation | Classify via chat completions; the dedicated moderation endpoint is coming soon |
| Human review | Enforcement and account decisions stay with the trust and safety team |
| Models | 30+ models; small aliases for classification, stronger ones for writing |
| Deployment | Plugsky cloud, your VPC, on-prem and air-gapped options |
| Pricing model | Flat monthly self-serve plans with unlimited fair-use usage |
| Free tier | plugsky-micro and plugsky-lite on the free plan, no card required |
TL;DR
- Deflect routine support questions with grounded, cited answers.
- Draft live-ops copy and patch summaries for the team to edit.
- Triage the moderation queue and leave enforcement to humans.
- Protect launch-day economics with routing and rate controls.
- Measure deflection, queue time and appeal rate together.
How it works, step by step
- Choose one queue such as player support or moderation triage.
- Index patch notes, policies and help content so answers cite the source.
- Classify and prioritise moderation items with a strict output schema.
- Route enforcement, bans and account decisions to the trust and safety team.
- Add rate controls and model routing to survive launch-day spikes.
- Log tool calls and model versions, then measure deflection and queue time.
Try it yourself
Gaming workflows suited to agents
Live games generate constant player and content work:
- Player support: answer account, purchase and gameplay questions from policies and patch notes.
- Live-ops drafting: write event copy, patch summaries and store descriptions for the team to edit.
- Moderation triage: classify reports by severity and policy category, and rank the queue.
- Telemetry summaries: turn dashboards and incidents into plain-language updates for the live team.
Enforcement and account actions remain with people, and appeals need a real review path.
Architecture and player safety
Build the loop to be fast, safe and observable:
- Retriever: embeddings over patch notes, policies and help articles for grounded answers.
- Classifier: strict schema for report category, severity and confidence.
- Read-only tools: account status, purchase history and ticket lookup.
- Action caps: routine refunds or unlocks only within limits, with approval above them.
- Human gate: trust and safety decides enforcement and account outcomes.
Log tool calls, model versions and reviewer identity for appeals and audits.
Launch spikes, cost and deployment
Launch weeks and live events produce sharp spikes. Route simple classification to small models, cache stable answers, queue non-urgent work and set per-channel rate limits. Self-serve plans are flat monthly with fair-use usage, so spikes do not create variable billing. Choose the processing region to match your players' privacy expectations, and keep player personal data out of prompts where a reference will do. Where a publisher or platform requires isolation, deploy in a VPC or on-prem using the same compatible API; the moderation endpoint itself is coming soon, so classify with chat completions today.
Pilot and evaluation
Prototype on plugsky-micro or plugsky-lite on one support queue, then use the 14-day full-access trial to test a stronger model on complex tickets and live-ops writing. Measure deflection rate, queue time, misclassification rate, appeal rate and player satisfaction, and review escalated cases weekly. Roll out channel by channel with versioned prompts, keep a kill switch for events, and re-test whenever policies or game content change.
Honest comparison
| Capability | Plugsky | Typical agent framework | Building in-house |
|---|---|---|---|
| Tool calling | Live function calling over account and ticket APIs | Framework-specific adapters | You build and maintain |
| Moderation | Classify with chat completions; moderation endpoint coming soon | Varies | You build and host |
| Deployment | Cloud, VPC, on-prem and air-gapped | Usually cloud-only | You operate GPUs and serving |
| Pricing | Flat monthly self-serve, fair-use usage | Varies by framework and model | GPU plus operations cost |
| Model choice | 30+ models behind one API | Varies by provider | You host every model |
Frequently asked questions
Can the agent ban players?
No. It triages and recommends; the trust and safety team makes enforcement and account decisions, and appeals should be reviewed by people.
Which endpoints do gaming agents use?
Chat completions, function calling, JSON mode and embeddings are live. The moderation, batch and assistants endpoints are coming soon.
How do we survive launch spikes?
Route simple tasks to small models, cache stable answers, queue non-urgent work and set per-channel rate limits before the event.
Is there a free plan?
Yes. The free plan includes plugsky-micro and plugsky-lite with no credit card, enough to prototype player support and moderation triage.
How does pricing work?
Self-serve plans are flat monthly with unlimited fair-use usage, which suits live events. See the live pricing page for current plans.
Can we isolate player data?
Yes. Use scoped keys and separate projects or deployments per title or region, including VPC or on-prem where a platform requires it.
How should we measure it?
Track deflection, queue time, misclassification rate, appeal rate and player satisfaction together rather than ticket volume alone.