Chrome Extension

A Manifest V3 Chrome extension that puts Vaquill’s statute search in any browser tab. The popup calls api.vaquill.ai directly using the user’s own API key - no proxy server, no backend to run, no infrastructure to maintain. Works in any Chromium-based browser (Chrome, Edge, Brave, Arc, Opera). The public API covers US statutes only: the US Code, the CFR, all 50 state statute codes, the U.S. Constitution, the Federal Rules, and Executive Orders. Source: github.com/Vaquill-AI/integrations/chrome-extension.

What you get

Manifest V3, service-worker based
Direct calls to api.vaquill.ai - no middleware
BYOK (bring your own key): each user configures their own API key in the Options page
Structured statute source cards: title or code, section number, jurisdiction, heading, excerpt
Vanilla JavaScript, no build step - edit and reload

Prerequisites

Google Chrome (or any Chromium-based browser) version 110+
A Vaquill API key (vq_key_...) from app.vaquill.ai/settings/api. See Authentication.

Quickstart

Clone the repo

git clone https://github.com/Vaquill-AI/integrations.git
cd integrations/chrome-extension

Load the extension

Open chrome://extensions/
Toggle Developer mode on (top right)
Click Load unpacked
Select the extension/ folder

Configure your API key

Right-click the Vaquill icon in the toolbar and choose Options (or click the gear icon inside the popup)
Paste your API key (vq_key_...)
Choose a default Jurisdiction
Click Save

Test

Click the extension icon and try a search like “42 USC 1983” or “FRCP Rule 12”. Expand a source card to see the section number, jurisdiction, heading, and excerpt.

Configuration

Extension defaults

Edit extension/js/config.js:

Setting	Description
`API_URL`	Vaquill API base URL (default: `https://api.vaquill.ai`)
`MAX_SOURCES`	Maximum number of statute sections returned per query
`SUGGESTED_QUESTIONS`	Array of starter searches shown on the welcome screen

Per-user settings (stored in `chrome.storage.local`)

Setting	Description
API Key	The user’s Vaquill API key, entered via the Options page
Jurisdiction	Preferred jurisdiction for search context

API keys live in chrome.storage.local on the user’s device. The extension never transmits them anywhere except to api.vaquill.ai.

API contract

The extension calls a single endpoint:

POST https://api.vaquill.ai/api/v1/statutes/search
Authorization: Bearer vq_key_...
Content-Type: application/json

Request body:

{
  "query": "42 USC 1983",
  "limit": 5
}

Full schema in the Statute search API reference.

Project layout

extension/
  manifest.json          Chrome extension manifest (v3)
  popup.html             Main chat popup
  options.html           Settings page (API key, mode, jurisdiction)
  css/popup.css          All styles (CSS custom properties for theming)
  icons/                 16, 48, 128 px icons
  js/
    config.js            API URL, defaults, suggested questions
    session.js           Storage manager (API key, chat history)
    background.js        Service worker - calls POST /api/v1/statutes/search
    popup.js             Search UI logic, source rendering
    markdown.js          Lightweight markdown-to-HTML renderer
    options.js           Settings page logic

Branding and theming

Name and description

Edit extension/manifest.json:

{
  "name": "Vaquill Statute Search",
  "description": "Statute search assistant for US Code, CFR, and all 50 state statute codes",
  "version": "1.0.0"
}

Icons

Place PNGs in extension/icons/:

icon16.png (16x16) - toolbar
icon48.png (48x48) - extensions page
icon128.png (128x128) - Chrome Web Store listing

Colors

Edit CSS custom properties at the top of extension/css/popup.css:

:root {
  --primary-color: #8b5cf6;
  --primary-hover: #7c3aed;
  /* ... */
}

Host permissions

host_permissions in manifest.json must match the API domain the extension calls. Default (Vaquill production API):

"host_permissions": [
  "https://api.vaquill.ai/*"
]

Custom API domain:

"host_permissions": [
  "https://api.yourdomain.com/*"
]

Multiple domains (dev + production):

"host_permissions": [
  "http://localhost:8000/*",
  "https://api.vaquill.ai/*"
]

Always use specific domains rather than wildcards (https://*/*). The Chrome Web Store reviews extensions with broad host permissions more aggressively and may reject them.

Publishing to the Chrome Web Store

Prerequisites

A Google Developer account ($5 USD one-time fee)
Register at chrome.google.com/webstore/devconsole

Preparation checklist

Set the production API_URL in config.js
Update manifest.json with name, description, version, and host_permissions
Add extension icons (16, 48, 128 px)
Prepare at least one screenshot (1280x800 px)
Prepare a privacy policy URL (required by Google)

Package the extension

cd extension/
zip -r vaquill-extension.zip . -x "*.DS_Store" "*.git*"

Upload

Open the dashboard

Go to the Chrome Web Store Developer Dashboard.

Create a new item

Click New Item and upload vaquill-extension.zip.

Fill out the listing

Name: Vaquill Statute Search
Summary: Statute search assistant for US Code, CFR, and 50 states (132 chars max)
Description: Full feature description
Category: Productivity
Language: English
Screenshots: At least 1 (1280x800 px)
Privacy Policy: URL to your privacy policy
Permissions Justification: Explain why storage and activeTab are needed

Submit for review

Typical review time: 1-3 business days.

Development

The extension uses vanilla JavaScript with no build step. Edit files directly, then reload the extension at chrome://extensions/ (click the refresh icon on the extension card).

Troubleshooting

“Failed to fetch” errors

host_permissions in manifest.json does not match the API URL in config.js. Make both point to the same domain (e.g., https://api.vaquill.ai).

API key not working

Generate a new key at app.vaquill.ai/settings/api and re-enter it in the Options page.
Check you have credits at app.vaquill.ai/billing.

Extension not loading

Validate JSON syntax in manifest.json.
Ensure all required Manifest V3 fields are present (manifest_version: 3, name, version, action, background.service_worker).

No sources in responses

Try a more specific query (cite a statute by title and section number).
Verify MAX_SOURCES is greater than 0 in config.js.

Content Security Policy errors

Do not add inline scripts or external script sources.

Restore the default CSP in manifest.json:

"content_security_policy": {
  "extension_pages": "script-src 'self'; object-src 'self'"
}

Statute search API

The endpoint this extension calls.

Authentication

How to generate and rotate API keys.

Embedded Chat Widget

Drop the same chat into any website via iframe.

GitHub

Source code and issue tracker.

Overview

MCP Servers

Chatbots

Widgets

Browser

Automation

What you get

Prerequisites

Quickstart

Configuration

Extension defaults

Per-user settings (stored in `chrome.storage.local`)

API contract

Project layout

Branding and theming

Name and description

Icons

Colors

Host permissions

Publishing to the Chrome Web Store

Prerequisites

Preparation checklist

Package the extension

Upload

Development

Troubleshooting

Statute search API

Authentication

Embedded Chat Widget

GitHub

​What you get

​Prerequisites

​Quickstart

​Configuration

​Extension defaults

​Per-user settings (stored in chrome.storage.local)

​API contract

​Project layout

​Branding and theming

​Name and description

​Icons

​Colors

​Host permissions

​Publishing to the Chrome Web Store

​Prerequisites

​Preparation checklist

​Package the extension

​Upload

​Development

​Troubleshooting

​Related

Statute search API

Authentication

Embedded Chat Widget

GitHub

What you get

Prerequisites

Quickstart

Configuration

Extension defaults

Per-user settings (stored in `chrome.storage.local`)

API contract

Project layout

Branding and theming

Name and description

Icons

Colors

Host permissions

Publishing to the Chrome Web Store

Prerequisites

Preparation checklist

Package the extension

Upload

Development

Troubleshooting

Related