Key facts
| Agent stack | Chat completions, function calling and embeddings are live |
| Use cases | Asset maintenance knowledge, outage communications, HSE documentation, reporting support |
| OT boundary | Keep agents on the IT side with no write path to control systems |
| Tools | Read-only access to maintenance, document and case systems |
| Deployment | Plugsky cloud, your VPC, on-prem and air-gapped options |
| Models | 30+ models; small aliases for retrieval, stronger ones for synthesis |
| Pricing model | Flat monthly self-serve plans with unlimited fair-use usage |
| Roadmap | Batch and assistants endpoints are coming soon |
TL;DR
- Summarise asset history and retrieve the right procedure for a work order.
- Draft outage and HSE communications for a duty officer to approve.
- Keep a hard IT/OT boundary with read-only tools only.
- Run air-gapped where policy forbids external traffic.
- Measure documentation time saved and revision correctness.
How it works, step by step
- Choose one workflow such as maintenance procedure retrieval or outage communications.
- Confirm the design has no write path to OT, SCADA or protection systems.
- Index approved procedures, HSE documents and asset history with revision metadata.
- Expose read-only tools for document, work-order and asset lookups.
- Require citations and route operational decisions through existing change control.
- Log tool calls and model versions, then measure accuracy and time saved per task.
Try it yourself
Open the LLM token calculator →
Energy workflows that suit agents
Energy operations produce constant documentation that people must read and act on:
- Asset knowledge: summarise maintenance history and surface the correct procedure for a work order.
- Outage communications: draft customer, regulator and media updates from incident facts for approval.
- HSE documentation: assemble incident reports and safety observations from structured notes.
- Reporting support: organise evidence and narrative for regulatory or sustainability reporting.
Every output goes to a named human owner before it is used.
Architecture and the OT boundary
Treat the boundary as non-negotiable:
- No write path: agents cannot issue commands or change control-system state, enforced in code and network policy.
- Read-only tools: document search, asset history and work-order lookup.
- Revision-aware index: store revision and effective date with each chunk and check freshness before answering.
- Composer: outputs with citations and stated assumptions.
- Authorisation gate: engineers and operators approve all operational actions.
Log tool calls and model versions for after-action and audit review.
Isolation, records and resilience
Some sites and programmes require air-gapped operation, and critical infrastructure policy may demand strict separation from operational networks. Plugsky supports cloud, VPC, on-prem and air-gapped deployment with the same compatible API, so the agent code, prompts and evaluations remain portable. Design for degraded operation: if the agent is unavailable, the underlying process must still work. Keep logs for the period your assurance framework requires, and treat safety or security discrepancies as escalations to a qualified person rather than answers.
Piloting and measurement
Prototype on plugsky-micro or plugsky-lite with one asset class and an approved document set, then use the 14-day full-access trial to test a stronger model on multi-document synthesis. Track retrieval accuracy, citation correctness, stale-revision rate and documentation minutes saved per work order. Self-serve plans are flat monthly with fair-use usage, so storm or peak-season volume stays predictable. Expand by site or asset class with versioned prompts and a re-run of the evaluation after each revision cycle.
Honest comparison
| Capability | Plugsky | Typical agent framework | Building in-house |
|---|---|---|---|
| OT separation | Agents stay on the IT side with read-only tools | Depends on your design | You design the boundary |
| Tool calling | Live function calling over internal document and asset APIs | Framework-specific adapters | You build and maintain |
| 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 operate equipment?
No. Keep agents on the IT side with read-only tools and no write path to control systems; authorised staff perform all operational actions.
Which endpoints do energy agents use?
Chat completions, function calling, JSON mode and embeddings are live. Batch and assistants endpoints are coming soon.
Can we deploy air-gapped?
Yes. Air-gapped deployment is available, and the same compatible API means no code changes are required.
Is there a free plan?
Yes. The free plan includes plugsky-micro and plugsky-lite with no credit card, enough to prototype procedure retrieval and documentation drafting.
How do we handle document revisions?
Store revision metadata with each indexed chunk, require citation of the revision and verify freshness before returning an answer.
How does pricing work?
Self-serve plans are flat monthly with unlimited fair-use usage. See the live pricing page for current plans and enterprise options.
How should we measure it?
Track retrieval accuracy, citation correctness, stale-revision rate and documentation minutes saved per work order.