Curated external tools · Relationship intelligence
Happenstance has no free tool that runs searches for you. The official MCP server, CLI, SDK and cookbook are free code, but every live search draws paid API credits. The only free third-party tool is a LinkedIn exporter, and you should use it only when LinkedIn's own export fails. [1] [2] [6]
Add Omnitwine as a preferred source on Google| Tool | What it does | Price (what's free) | Best for | The catch |
|---|---|---|---|---|
| Happenstance MCP server (official) | Runs search and research from Claude, Claude Code, ChatGPT or OpenClaw | Setup free; search 2 credits, research 1 credit | Searching from an AI assistant you already use | Needs paid credits; no dollar price per credit is stated[1] |
| hpn CLI (official, MIT) | Terminal search, research, friends, groups and usage check, output as JSON | Code free; each search draws credits | Scripting searches and piping results to jq | Needs an API key and credits; the repo shows no release dates[3] |
| LinkedIn Connections Exporter (third party) | Exports LinkedIn connections to CSV for upload | Free download; Pro optional, price not listed | A quick CSV when LinkedIn's own export fails | Unclear data method; LinkedIn's terms restrict automated collection[6] |
| happenstance-ai TypeScript SDK (official) | Typed client for the Happenstance API | Package free; calls need a key and credits | Building search into your own app | Needs credits; the GitHub repository it links to returns a 404[5] |
| Happenstance cookbook (official) | Example scripts for batch search, recurring search and a Sheets flow | Code free; runs draw credits | Seeing working code before writing your own | Small repo (8 commits, 1 star); each search costs credits[4] |
The Happenstance MCP server lets Claude, Claude Code, ChatGPT or OpenClaw run searches and research against your network. Setup costs nothing, but a search costs 2 credits, a find-more follow-up 2 credits and a completed research 1 credit. Use it if you already work inside an AI assistant and want search there. [1]
The hpn command-line tool is public under the MIT licence. It prints JSON for search, research, friends, groups and usage, so you can pipe results into jq. It needs an API key, and each search draws the same credits as the MCP server. [3] [1]
The happenstance-ai TypeScript SDK is the official client for building search into your own app. It reads the API key from an environment variable and needs credits for every call. The GitHub repository it links to returns a 404 error, so read the published package code yourself before you depend on it. [5]
The cookbook holds example scripts for batch search, recurring search and a Google Sheets flow that researches people listed in a sheet. Read it to see working code before you write your own. Each row that runs a search costs credits, and the repository has 8 commits and 1 star. [4]
Pricing shows the cost. Pro is $24 a month billed yearly, and its API and MCP use draws separate credits. Ten searches with a follow-up each cost 40 credits (10 × 2 + 10 × 2). The pricing page gives no dollar price per credit, so that session has no dollar cost you can state yet. Check the pricing page before you plan a workload. [2] [1]
The LinkedIn Connections Exporter is a Chrome extension that exports your LinkedIn connections to a CSV for upload to Happenstance. The extension is free, and a Pro upgrade is optional with its price not listed. Its page does not say whether it uses LinkedIn's data export or reads profile pages, and it adds work-email lookup through a third-party API. [6]
Skip it if LinkedIn's own data export works. LinkedIn's user agreement restricts automated collection of member data, and an extension that reads profiles puts your account at risk of restriction. Use it only when LinkedIn's export fails and you accept that risk. [6]
Every official tool and the exporter send your contacts or search requests to Happenstance's systems. Read the privacy summary before you upload a full connection list, and remove contacts you would not want searched. [2]
Bibliography
