SynOI

Product · SynOI for OpenClaw

Testing

Native OpenClaw plugins.
LLM keys never leave your machine.

Two first-class plugins for the OpenClaw extension API: synoi-router bridges OpenClaw to any LLM provider using your own keys, and synoi-guard adds approval gates and signed receipts on top. Install one. Install both. License covers both. Your provider credentials stay on your machine. SynOI never sees them.

Install instructionsOpenClaw community →

Two plugins · one license

Router brings the models. Guard brings the governance.

OpenClaw plugin

synoi-router

Extension hook: registerProvider + createStreamFn

LLM bridge

Implements OpenClaw's LLM provider hook. Routes OpenClaw's calls to any Claude/OpenAI/Groq/Mistral/local-model endpoint you configure. Tier-aware routing built in: trivial queries go to free Groq, reasoning to Opus, defaults configurable per workspace. BYO keys flow through but never touch SynOI servers.

  • Provider routing across Anthropic, OpenAI, Groq, Google, Mistral, local
  • Tier-aware routing (cheap → expensive)
  • Streaming pass-through with no body mutation
  • X-Provider-Key per-request, never persisted

OpenClaw plugin

synoi-guard

Extension hook: before_tool_call

Governance layer

Implements OpenClaw's HITL hook. Evaluates every dangerous tool call against your risk policy. Routes approvals to the surfaces your team uses: mobile, Slack, SMS, desktop, email. Every decision mints a signed Decision Receipt that lives in your local OpenClaw state and verifies offline.

  • Per-workspace risk policy
  • Multi-surface HITL: mobile, Slack, SMS, desktop, email
  • Signed Decision Receipts in OpenClaw state
  • Timeouts fail closed

Composable. Use the router alone if you only need multi-provider routing with BYO keys. Add the guard when you're ready for HITL + receipts. Both ship under the same SynOI license; no second purchase required to graduate.

BYO keys, locally

Your provider credentials never leave OpenClaw.

The OpenClaw model differs from the hosted gateway. With synoi-router, your ANTHROPIC_API_KEY, OPENAI_API_KEY, or any other provider credential is stored only on your local machine. The router invokes the provider HTTP API directly from your OpenClaw process. SynOI's servers are never in the request path for inference.

What SynOI doessee is your license check - a periodic, body-less call to the SynOI control plane to validate the hashed-only license token. That's it. No prompts, no completions, no tool calls, no keys.

This is the deliberate architecture for the community wedge: customer cost stays predictable (they pay the provider, not us), customer credentials stay in customer custody, and SynOI's governance contribution is the parts that don't need the prompt body: policy evaluation, HITL routing, receipt minting against the local Decision Journal.

Data flow

# inference request

OpenClaw → synoi-router

→ Anthropic / OpenAI / local

# governance check

OpenClaw → synoi-guard

→ local policy eval

# HITL surface

synoi-guard → push svc

→ your mobile / Slack

# SynOI sees:

license heartbeat only

Design-partner install (pre-release)

From design-partner install to a signed receipt.

These plugins are pre-release: not yet listed in OpenClaw's public plugin manager. The steps below are the design-partner install path today; general availability through the plugin manager search lands once that listing is complete.

  1. 01

    Install both plugins (design-partner path)

    The plugins auto-register against the documented extension hooks (registerProvider, createStreamFn, before_tool_call) the same way once published. Until then, design partners install directly via the CLI below rather than searching OpenClaw's plugin manager.

    # Design-partner install (not yet in the public plugin manager):
openclaw plugin install synoi-router
openclaw plugin install synoi-guard

  2. 02

    Configure providers locally

    In OpenClaw's settings, point synoi-router at your provider keys. Keys are stored using OpenClaw's secret-store integration; they never touch SynOI's network. Configure the routing tiers per workspace.

    # openclaw/config/synoi-router.json
{
  "providers": {
    "anthropic": { "key": "secret://ANTHROPIC_API_KEY" },
    "openai":    { "key": "secret://OPENAI_API_KEY" },
    "groq":      { "key": "secret://GROQ_API_KEY" }
  },
  "routing": {
    "trivial":   "groq:llama-3-70b",
    "default":   "anthropic:claude-haiku-4-7",
    "reasoning": "anthropic:claude-opus-4-7"
  }
}

  3. 03

    Drop in the SynOI license

    Paste your SynOI license token. The plugins talk to the control plane only for license validation, no inference traffic. Free tier covers solo developers.

    # Same license covers synoi-router + synoi-guard.
SYNOI_LICENSE=lic_8b3c9f12...

# Verify locally:
openclaw plugin status synoi-router
# > license_valid: true · tier: free

  4. 04

    Receipts mint locally · approve remotely

    From the moment synoi-guard is active, every governed tool call produces a Decision Receipt in OpenClaw's local Decision Journal. HITL approvals route to whatever surfaces you've configured: mobile push, Slack DM, SMS reply, desktop toast.

    # Receipts are written to:
~/.openclaw/synoi/receipts/rcpt_8b3c9f....cbor

# Verify any of them with the public verifier:
openclaw synoi verify rcpt_8b3c9f...
# > Ed25519 + ML-DSA-65 ok · approver=a.rivera · surface=mobile

The community wedge into SynOI.

Free for solo developers. Same plugins scale into the team and enterprise tiers when you outgrow them. Provider keys remain yours forever.

Install instructionsPricing