What is OpenClaw?
OpenClaw is an extensible AI gateway and agent runtime with plugins for model providers, tools, channels, and skills. It gives you a CLI, a gateway process, and a unified model picker so you can run assistants and workflows against different model backends without hard-coding one vendor into every setup.
The EUrouter OpenClaw plugin registers EUrouter as a native provider inside that workflow. You install the plugin, store `EUROUTER_API_KEY` in OpenClaw's secrets store, and then select models like `eurouter/gpt-4o` or `eurouter/claude-sonnet-4-6` the same way you would use any other provider. That is a cleaner fit than wiring a custom OpenAI-compatible base URL into each individual tool, and it keeps the OpenClaw UX intact.
Quick to integrate
A few lines of code is all it takes. Swap your base URL and you are routed through EUrouter.
1openclaw plugins install @eurouter/openclaw-eurouter
2openclaw gateway restartGet started in minutes
Follow these steps to connect your application to EUrouter.
Install the OpenClaw plugin
Add the EUrouter provider plugin with the OpenClaw CLI, then restart the gateway so the new provider is loaded.
1openclaw plugins install @eurouter/openclaw-eurouter
2openclaw gateway restartStore your API key in OpenClaw
Use the OpenClaw secrets store for `EUROUTER_API_KEY`. On macOS, this matters because the OpenClaw gateway runs as a LaunchAgent and does not inherit shell exports.
1openclaw secrets set EUROUTER_API_KEY eur_your_key_hereAllow and pick EUrouter models
Choose models with the `eurouter/...` prefix in the model picker or your config. If you already use `agents.defaults.models`, keep that allowlist in place and add either `eurouter/*` or the exact EUrouter models you want to permit.
Why use OpenClaw with EUrouter
Native provider workflow
This integration is a real OpenClaw provider plugin, not a per-tool base URL hack. Once installed, EUrouter shows up as its own provider and OpenClaw can treat `eurouter/...` models like first-class options in the existing workflow.
- Install with `openclaw plugins install` and load it through the normal gateway lifecycle
- Use provider-prefixed model IDs such as `eurouter/gpt-4o` and `eurouter/claude-sonnet-4-6`
- No need to reconfigure each OpenClaw tool around a custom OpenAI-compatible endpoint
- Fits the way OpenClaw already manages providers, plugins, and model selection
EU-hosted routing for OpenClaw sessions
OpenClaw workflows can include prompts, instructions, memory, and agent context. With EUrouter configured as the provider, those model calls route through EU-hosted infrastructure, which is the whole point if you need European data residency instead of sending traffic straight to a US-managed endpoint.
- Model traffic is routed through EUrouter's EU-based infrastructure
- Useful for teams that want OpenClaw without giving up GDPR requirements
- Keeps EU data residency aligned with the rest of your AI stack
- Lets you keep the OpenClaw interface while changing the compliance posture underneath
Safer desktop and team rollout
The plugin follows OpenClaw's operational model instead of fighting it. Credentials live in the secrets store, macOS users avoid broken shell-export setups, and teams that already use model allowlists can keep those guardrails in place.
- Store `EUROUTER_API_KEY` with `openclaw secrets set` instead of relying on shell exports
- Avoid macOS LaunchAgent issues where the gateway does not inherit interactive shell variables
- Preserve `agents.defaults.models` and add `eurouter/*` or explicit EUrouter IDs
- Suitable for individual desktops and shared OpenClaw gateways with stricter controls