Chrome extension for LinkedIn
The disburse extension adds one button to every LinkedIn profile, beside Message and Follow. Press it and the side panel shows whether we hold a verified mobile and email for that person. Looking is free. Revealing costs one credit, the same for a mobile as for an email, from the same balance your API keys and Claude use.
It is the surface for the moment you already know who you want. When you do not know yet, describe the buyer to disburse in Claude or ChatGPT and let it find them.
Install and connect
- Install it from the Chrome Web Store and pin it to the toolbar.
- Open the panel from the toolbar icon and press Connect Disburse. The dashboard opens, you sign in if you are not already, and one click creates a key for this browser and hands it to the extension. The key is never shown on screen and never leaves the extension.
- Open any LinkedIn profile and press the Disburse button.
Only an organisation owner or admin can connect a browser, because connecting creates an API key. Ask one to connect, or ask to be made an admin. The same steps are on the dashboard's Connect page.
What you see
| Panel | Meaning | Cost |
|---|---|---|
| Who they are, with mobile and email each marked available or not | The free preview | Nothing |
| Reveal contact | Shows the mobile and email on file | One credit, once per person per organisation |
| No email or phone found | We are not confident in any contact for this person | Nothing |
Revealing someone a second time, from any browser, key or agent in your organisation, is free. Emails carry the same verification status the API returns, so a verified badge in the panel means the same thing it does there.
Keys and revoking
Each connected browser is an API key named Chrome extension (Name) on your
API keys page. Revoke it there to disconnect that browser immediately; the
extension asks to connect again the next time it is opened. Revoking one browser
does not affect any other.
Privacy
The extension reads nothing from the LinkedIn page. The profile URL of the tab
you are on is the whole input, and the lookup is the same
POST /v1/enrich/person call the API reference documents. The
production build only talks to *.disburse.dev. Reveals appear in your
dashboard's request log like any other request.