Key facts
| API compatibility | OpenAI-compatible /v1/chat/completions (change the base URL) |
| Models | 30+ models from free to frontier tiers behind one API |
| Agent primitives | Function calling, JSON mode and streaming are live |
| Retrieval | Embeddings and RAG over your own corpus |
| Deployment | Plugsky cloud, VPC, on-prem or air-gapped |
| Pricing | Flat monthly self-serve plans with fair-use usage; see the live pricing page |
| Event triggers | Agents can run on events from your TMS or tracking feeds |
| Multilingual | Multilingual models for carrier and customer messaging |
TL;DR
- Keep your OpenAI SDK — change the base URL and model name.
- 30+ models behind one API, from free chat models to frontier reasoning.
- Deployment options from hosted cloud to VPC, on-prem and air-gapped.
- Pilot on one lane before any global rollout.
- Agents draft and route; planners commit.
How it works, step by step
- Define the job, the permitted data sources and where a human must approve.
- Pick one lane and instrument exception misroutes.
- Create a Plugsky account and generate an API key (free plan, no card required).
- Point your OpenAI SDK at the Plugsky base URL and map your model names.
- Index the approved corpus with embeddings and keep retrieval role-scoped.
- Keep bookings and rate changes under human approval.
- Measure quality on your own samples, then scale with usage monitoring.
Try it yourself
Where AI agents pay off in logistics
Logistics teams do not lack ideas for agents; they lack a safe path from demo to production. The pattern below targets repetitive, document-heavy work where a human can check the output, which is where agents earn their place first. Treat the agent as a new team member with a narrow brief, explicit permissions and a probation period, and rollout becomes an operations exercise rather than a leap of faith.
- Exception triage — classify delays, damage and customs holds and route them
- Status updates — draft customer and carrier messages from live shipment data
- Documentation checks — verify commercial invoice and declaration completeness
- Warehouse Q&A — answer slotting, packing and returns questions from SOPs
A reference architecture for logistics agents
A monitoring agent detects an exception and enriches it with tracking data through tools, while a communications agent drafts the update and routes it for approval. Operational changes stay with planners.
- Event-driven triggers from TMS or tracking feeds
- Retrieval over SOPs, trade guidance and customer rules
- Read-first tools into TMS, WMS and carrier APIs
- Approval rules for anything with cost or commitment impact
Data governance and human oversight
Shipment data includes customer and commercial detail. Scope access by lane or account, log every message, and keep change authority with planners so an agent cannot commit capacity or cost.
- Account or lane scoped retrieval
- Audit logs for generated communications
- No autonomous booking or pricing changes
- Retention rules for trade documentation
From pilot to production
Pilot exception triage on one lane or one customer. Measure misroute rate and update quality before broadening to documentation checks.
Keep the rollout reversible: run the agent in shadow mode alongside the current process, compare outputs on your own samples, and move it into the workflow only when the evidence holds. Document what you measured so expanding to the next team is a decision, not a hope.
Honest comparison
| Capability | Plugsky | Typical cloud AI API | Building in-house |
|---|---|---|---|
| API compatibility | Drop-in base URL change | Usually compatible | Full rewrite |
| Model access | 30+ models behind one API | Vendor's own catalogue | You host each model |
| Pricing | Flat monthly self-serve plans; see live pricing | Often per-token | GPU + ops cost |
| Deployment | Cloud, VPC, on-prem or air-gapped | Usually vendor cloud regions | You own the stack |
| Operational systems | Agents read TMS/WMS through tools | Varies | You build the tools |
| Cost commitments | Human-approved by default | Varies | You enforce it |
Frequently asked questions
Do we have to rewrite our application?
No. The chat completions API is OpenAI-compatible, so you change the base URL and model name and keep your existing SDK.
Is there a free plan?
Yes — the free plan includes two free AI models, plugsky-micro and plugsky-lite, with no credit card required.
How is pricing structured?
Self-serve plans are flat monthly with fair-use usage and no per-token charges; see the live pricing page for current plans.
Which endpoints are live today?
Chat, streaming, JSON mode, function calling, embeddings, RAG and agents are live. Audio, images, moderation, files, batch, fine-tuning, assistants and responses endpoints are coming soon — check the docs before planning around them.
Can agents book or rebook shipments?
They can prepare recommendations and drafts; booking and cost commitments should stay with planners or your automation under approval rules.
Can it read customs paperwork?
You pass document text as context; the files endpoint is coming soon. Validate accuracy on samples before relying on it for declarations.
Does it handle multiple languages?
Yes — multilingual models are available; ground trade terminology in your own glossary to keep translations consistent.