Connect proof sources to Excellent
The Excellent extension reads an API key off a dashboard you're already signed into and hands it to your local Excellent service. No copy-paste, no new login, and keys never reach our servers.
then load it unpacked at chrome://extensions
Requires the Excellent app running locally · Chrome 116+
How it connects.
The extension runs in your real browser, on your real sessions — so there is nothing to re-authenticate. Each connection lets Excellent read the evidence source you choose.
Click Connect in Excellent
In your local Excellent app, hit Connect for a proof source like GitHub, CI, or a deployment tool. The app asks the extension to fetch the key that connects that source.
It reads the key, already signed in
The extension opens that provider's settings page in your real browser — where you're already logged in — reveals the API key, and reads it. No new login, no copy-paste.
The key goes to your machine only
It hands the key straight to your local Excellent service over loopback, which seals it. The key never touches Excellent's servers or anyone else's.
Two reads, both yours.
The extension does exactly two things, and both start with you. That is the whole scope it asks for — no background access.
One API key, when you click Connect
When you click Connect for a tool, the extension opens that provider's settings page where you're already signed in, reads the one API key shown on it, and hands it to your local Excellent service. It may click Reveal to surface the key — never a destructive control like delete, revoke, or regenerate.
Public result rows, only if you grant Watched sites
If you turn on the distribution monitor and grant the optional Watched sites permission, the extension reads the public search-result rows for your keywords — post titles, links, snippets, the same listing anyone browsing would see — and returns them to your local Excellent service. Only public rows; never private messages, never credentials, and it writes or clicks nothing.
The full data practices are in the extension privacy policy.
Your keys, your machine.
Local-first, separation of duties, nothing phones home — the same posture as the rest of Excellent. A credential physically cannot reach us.
Local-first by construction
The extension talks only to your local Excellent service on localhost. It refuses any non-loopback target — there is no cloud endpoint to leak to.
Acts only when you ask
It does nothing on its own. Every capture is a job you started by clicking Connect, authenticated with a one-time pairing token you generate in the app.
Keys are never stored
The extension keeps only the pairing token and your app URL. API keys are read on demand, delivered, and never persisted by the extension.
Install Excellent.
Install the extension, run Excellent on your machine, and pair them once. Every outside proof source then connects to the local verification loop.