LeadSearch is a Chrome extension (Manifest V3) that runs as a side panel — it sits beside the page you are looking at rather than covering it.
Getting it
Download — always-current build:
https://web.appmint.space/leadsearch/latest/leadsearch-extension.zipA versioned copy sits beside it (leadsearch-extension-1.0.2.zip), and the same folder hosts a short install page with the current version and checksum.
The latest path always serves the newest build — bookmark that rather than a versioned file.
Verify the download
shasum -a 256 leadsearch-extension.zipCompare against the SHA-256 published on the install page. At version 1.0.2 (156 KB) it is:
9b7760a1092a0c28d841aa7989a241bff598ebcaa613ef8beda7db2f2e6fbfbaA Chrome Web Store listing is on the way. Once it is live, install from there instead — Chrome then keeps the extension updated for you.
Loading it into Chrome
1. Unzip it somewhere permanent. Chrome loads the extension from that folder every launch, so do not unzip into Downloads and clear it later. If the folder moves or is deleted, Chrome disables the extension.
2. Open chrome://extensions.
3. Turn on Developer mode, top right.
4. Choose Load unpacked and select the unzipped folder.
5. Pin LeadSearch to the toolbar so the side panel is one click away.
With Developer mode on, Chrome shows a "Disable developer mode extensions" prompt each time it starts. Dismiss it — the extension keeps working. The prompt disappears once you install from the Web Store.
Updating
A manually loaded extension does not update itself. To move to a newer build:
1. Download the new zip and extract it over the same folder.
2. Open chrome://extensions and press the refresh icon on the LeadSearch card.
Check the version on the install page occasionally, or move to the Web Store listing when it is available.
Connecting it to your organization
Two ways. The second is easier if you already use Studio.
Automatic — pick up an existing session
If you are signed in to Studio in the same browser, the extension can detect that session and configure itself. Open Studio in a tab; a notification confirms the sync.
It watches for sign-in and sign-out, so signing into a different organization re-syncs the extension to that one.
The detector runs on *.appmint.io and on localhost for development. It reads the active session — organization and token — and copies it into extension storage.
Manual — API key
Otherwise, enter credentials in the extension:
| Field | What it is |
|---|---|
| Organization ID | Your orgid |
| API key | A key issued for this purpose |
| Base URL | The AppEngine endpoint, normally https://appengine.appmint.io |
The extension sends the key as x-api-key with your orgid.
There is no per-key scope. Issue the key against a dedicated low-privilege user rather than an administrator, so an extension on a laptop cannot do more than capture leads. See API keys.
Checking the connection
The extension pings the platform's health endpoint with your organization. If it reports connected, you are ready. A failure here is credentials or network — not the capture logic.
What it can access
The extension requests access to LinkedIn, Google Maps, Appmint domains and localhost, plus the ability to read the active tab, use storage, open the side panel and inject its scripts.
It reads pages you have opened in your own signed-in session. It does not browse on your behalf.