Overview

Aquilifer is a browser extension that acts as a secure LLM provider for websites, the same idea as a crypto wallet extension like MetaMask, but for LLM access instead of a blockchain account.

A website never sees your API key. It asks the extension for a completion; the extension holds the credential, enforces your permissions and rate limits, and hands back only the response.

The three things that never change

However this project grows, these stay true: they're the entire point of it, not implementation details that might get relaxed later:

• The website can never obtain your credentials. It gets a completion, never a key.
• The website can never choose which provider answers. You bind a provider to a site when you connect it; the site only ever sends prompts and receives completions.
• Your own usage limits always apply, regardless of why a site is calling, including if it's only using Aquilifer as a fallback for its own, separate integration.

What's on this page vs. the rest of the docs

• Installing: installing from the Chrome Web Store, and building from source if you're contributing.
• Connecting a site: the approval flow, and what "connect once, then silent" actually means.
• Providers: Anthropic, OpenAI, and self-hosted/local models.
• The toolbar popup: the quick-glance view: what's connected, live rate-limit standing, switching models and the default provider.
• Rate limiting and History: the controls and the audit log that back the trust model.
• The vault: optional password-based encryption for stored API keys, and importantly, what it does not protect.
• Appearance: font size and the toolbar popup's width.
• The page-facing API: for developers integrating Aquilifer into a website.
• Limitations & downsides: read this one. Every project has tradeoffs; this page is where they're written down instead of left for you to discover.
• Privacy policy: what's stored, what's sent over the network and to whom, and that there's no analytics or tracking anywhere in the extension.