Skip to main content
Use Vaquill AI from the tools your team already has open: Claude, Slack, a marketing site, a Google Sheet. Every integration is open-source and self-hostable, and all of them call the same Vaquill statutes API.

MCP Servers

Connect Vaquill AI’s US statute corpus (US Code, CFR, all 50 state codes) to 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 with one script tag, an iframe, or a full Next.js deployment that adds voice and history.

Browser Extensions

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

Automation

n8n and Make.com templates that read questions from a Google Sheet and write back matching statute sections and citations.

GitHub

Every integration is MIT-licensed. Fork what you need.

​
Pick an integration

​
Common architecture

Each integration is a thin wrapper. It takes input from its surface (a Slack message, browser popup, or webhook), calls the statutes search endpoint, and renders the matching statute sections. One API key (vq_key_...) from your dashboard works for all of them. Configuration is through environment variables, and 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/us/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.
Last modified on October 24, 2026