Skip to main content
Put Vaquill wherever your team already works - Claude, Slack, a marketing site, a Google Sheet. Every integration is open-source, self-hostable, and calls the same Vaquill statutes API under the hood.

MCP Servers

Plug Vaquill’s full US statute corpus (US Code, CFR, all 50 state codes) into Claude, Cursor, VS Code, or any MCP client.

Chatbots

Legal Q&A in Slack, Discord, Microsoft Teams, Telegram, WhatsApp, or Signal with thread memory and cited sources.

Widgets

Embed a chat widget on any site - one script tag, an iframe, or a full Next.js deployment with voice and history.

Browser Extensions

Research from any browser tab without leaving the page. Chrome, Edge, Brave, Arc, Opera.

Automation

n8n and Make.com templates that turn a Google Sheet of questions into a Sheet of answers and cited sources.

GitHub

Every integration is MIT-licensed and ready to fork.

​
Pick an integration

​
Common architecture

Every integration is a thin wrapper: take input from the surface (Slack message, browser popup, webhook), call the statutes search endpoint, render the matching statute sections. One API key (vq_key_...) from your dashboard drives them all. Configuration is via environment variables; every integration ships with a Dockerfile and at least one cloud-deploy recipe.

​
Build your own

To add a surface we do not ship (Outlook, Notion, a CRM, an internal portal):
  1. Generate a key in your dashboard.
  2. POST /api/v1/statutes/search with { "query": "..." } and Authorization: Bearer vq_key_....
  3. Render the returned statute sections (title, code, section number, text).
  4. Pass filters (jurisdiction, code) to narrow results.
See Authentication for key setup and Errors for status-code handling.