Legal Data Plugin for OpenClaw

Stop your OpenClaw agent from hallucinating legal citations. Real regulations from 66 official sources across 100+ countries — GDPR, customs/HS codes, sanctions, dual-use, GOST, EAEU.

What it does

• /cleo-search "GDPR Article 17" — Real article text from EUR-Lex, not hallucinated
• /cleo-classify "stainless steel beam" — HS code with confidence + customs rationale (multilingual)
• /cleo-compliance "drone with infrared camera" KZ — Full decision pack: tariff + obligations + dual-use + EAEU + lead time
• /cleo-doc <UUID> — Full text of any document
• /cleo-changes 30d — Regulations that moved in the last 30 days
• /cleo-setup — First-run onboarding (3 free lookups, then pay-as-you-go)

Plus 5 SEO-targeted skills that auto-invoke when your agent detects regulatory questions: regulatory-research, gdpr-data-protection, customs-hs-classifier, dual-use-export-control, sanctions-screening.

Install

openclaw plugins install clawhub:@alexbloch-ia/legal-data

Then run setup:

openclaw run /cleo-setup

This opens cleolabs.co/signup in your browser. Create an account, copy the ld_live_... API key, paste it back.

Set the env var:

echo 'export CLEO_LEGAL_API_KEY="ld_live_..."' >> ~/.zshrc
source ~/.zshrc
openclaw mcp restart cleo-legal

Verify

openclaw run /cleo-search "GDPR Article 17"

You should get real Article 17 text from EUR-Lex.

Pricing

Composite endpoints (/cleo-compliance) consume 5 units per call.

Coverage

66 official sources, including:

• EU: EUR-Lex, EDPB, ECHA, EFSA
• France: Legifrance (PISTE), CNIL
• Germany: BWB, BaFin, BfArM
• UK: legislation.gov.uk, ICO, FCA
• US: eCFR, Federal Register, FDA, OFAC SDN
• Spain: BOE, AEPD
• Italy: Normattiva
• Russia / EAEU: EEC TR CU, GOST R
• WIPO Lex as universal fallback for 100+ countries

Full list: coverage report.

Examples

• GDPR audit on user data flows
• Customs HS classification for a complex product
• Composite compliance check for cross-border shipment

Troubleshooting

See docs/troubleshooting.md — covers the streamable-http header bug workaround (OpenClaw issue #65590, May 2026).

Compatibility

Declared in package.json:

"openclaw": {
  "compat": { "pluginApi": ">=2026.3.24-beta.2", "minGatewayVersion": ">=2026.3.24-beta.2" },
  "build":  { "openclawVersion": ">=2026.3.24-beta.2" }
}

If openclaw plugins install fails with a runtime-version mismatch, upgrade OpenClaw (openclaw --version to check) before retrying.

Architecture

This plugin is a declarative bundle wrapping the Cleo Legal API's MCP server (Streamable HTTP, Bearer auth, 19 tools). It is not a heavy native runtime plugin — the dist/index.js entry is a no-op required only by OpenClaw's validator. All value lives in:

• .mcp.json — MCP server config (auto-detected by OpenClaw)
• commands/*.md — 6 user-invocable slash commands
• skills/*/SKILL.md — 5 auto-invoked skills
• openclaw.plugin.json + .claude-plugin/plugin.json — manifests

The Cleo Legal API's MCP server handles 66 sources, multi-language search, embeddings, content-change detection, and the WIPO Lex universal fallback for geo-blocked jurisdictions. The plugin merely surfaces it inside OpenClaw with a sensible UX.

For the backend architecture, see the main repo.

License

MIT-0 (ClawHub requirement). Plugin source is fully open; API access requires an account.

Issues & feedback

github.com/AlexBloch-IA/legal-data/issues

Maintainer setup

CI requires two GitHub secrets (Settings → Secrets → Actions):

• CLAWHUB_TOKEN: ClawHub publisher token (obtain via clawhub login locally, copy from ~/.clawhub/credentials)
• NPM_TOKEN: npm automation token with publish rights to @alexbloch-ia/*

Release: git tag v1.0.x && git push origin v1.0.x. CI publishes to ClawHub + npm.