Request and response plugins that transform, enrich, or repair data as it flows through the gateway.
Plugins are gateway-level middleware that augment a request as it flows through OpenDunes.
Available now: Web Search. Enable it at Settings → Plugins (/dashboard/settings/plugins) to make it the default for new chats, or toggle it per message from the chat composer's Tools menu. When on, fresh real-time web results are appended to your prompt before the model answers. More plugins are on the way.
Server tools give the model new capabilities it can invoke autonomously. Plugins are transparent to the model — they transform data before it arrives or after it leaves, without the model knowing they ran.
| Server tools | Plugins | |
|---|---|---|
| Model aware | Yes (tool calls) | No (transparent) |
| Runs when | Model decides | Every request |
| Typical use | Capability extension | Data transformation, safety, reliability |
Plugins are enabled per-request via the plugins array:
Multiple plugins run in the order listed. Request plugins run before the model; response plugins run after.
| Plugin | Phase | Description |
|---|---|---|
| Web Search | Request | Inject search results into the prompt automatically |
| Response Healing | Response | Detect and repair malformed or truncated outputs |
When multiple plugins apply to the same phase, they run in array order. A request plugin that modifies the prompt will affect all subsequent request plugins and the model itself.
Each plugin that performs a billable operation (e.g., a search call, an additional model invocation) adds to the per-request cost. Plugins that only transform data in memory (e.g., format validation) have no additional charge. Plugin costs are itemized in your usage breakdown alongside token costs.