Find
Headhunt, prospect, or map a market. Ask in plain English and get back a real shortlist - people, companies, repos - read live from the open web.
NewI now search research paper authors too, ranked by what they publish.
A sentence in. The agent reads the open web, live.
- Results will appear here as the agent finds them.
How it works
One sentence in. A shortlist out.
01Describe who you're after
Plain English, no filters or booleans. "Staff backend engineers in NYC who shipped Rust in production" is a complete query.
Try that exact search02I read the open web, live
I plan the search, then read public LinkedIn and Crunchbase records, GitHub, and the sources they link to - at search time, not from a stale export. You watch every step as it runs.
03Act on a ranked shortlist
Every result comes with the reasoning behind it. From there I draft outreach in each person's language, put them on a role's pipeline, or you export the list to wherever you work.
See real shared results
Then run the hire
A pipeline for every role, set up before you ask.
Put the shortlist on a role's board in one click, clip more people from LinkedIn, and move them to hired by dragging or by saying so. Free with your account.
Pipeline
Senior Backend Engineer
Sourced3
Priya Raman
Staff Engineer
Marcus Lee
Senior Backend Engineer
Ana Souza
Platform Engineer
Interview3
Tom Becker
Software Engineer
Lena Fischer
Senior SRE
Omar Haddad
Tech Lead
Trusted by
Individual recruiters, investors, and founders.
The ones who source for themselves - from teams like these.
Ramp
Mercury
Linear
Retool
Vanta
Deel
Hunt Club
Riviera Partners
Uncork Capital
Craft Ventures
Boldstart
Amplify Partners
Base10
Initialized
Reach each one, in their language, with the line that earned them in.
Sarah K.·San Franciscomaintains tikv/raft-rs · 314 commits in last year
drafting
Mike T.·San Franciscoex-Stripe · founding eng at Quantum Forge
queued
Emily H.·New YorkRustConf ’24 · "async runtimes that don’t lie"
queued
Chris P.·San Franciscoex-Apple · founding eng at Foundry (18 ppl)
queued
You stay in the loop on every send.
API and MCP server
Put people search in your own stack.
Everything the interface does is one HTTP call away, and the same searches drop into Claude, Cursor, or VS Code as tools your assistant can call mid-conversation. One key, the same credits, no separate plan.
Call it from your code
A sentence in for a ranked shortlist with the reasoning attached, or an exact filter set for the same page every time.
curl https://www.refolk.ai/api/v1/search \
-H "Authorization: Bearer $REFOLK_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query": "Staff backend engineers in NYC who shipped Rust in production"}'Or add it to your assistant
One URL, one header, 12 tools. Then ask for a shortlist in the chat you are already in.
claude mcp add --transport http refolk https://www.refolk.ai/api/mcp \
--header "Authorization: Bearer rfk_live_your_key_here"A search in plain English costs 100 credits, and nothing at all when it finds nobody; a filtered search costs 10. A new account starts with 500 free credits, so the first calls are on me.
Shared searches
See what others are looking for.
Real prompts, real results. Each page is a snapshot of a search someone ran and decided to share.
- Shared
Engineers in Melbourne or Sydney who built FHIR or Best Practice integrations f…
- Shared
Venture partners who left a seed or Series A firm in the last 12 months and sti…
- Shared
Find US-based engineers who have merged PRs or maintainer roles in OpenTelemetr…
- Shared
Research scientists who left Google DeepMind London in the last 18 months and n…
- Shared
Engineers in the US with 10+ years of COBOL and CICS now working as independent…
- Shared
Software Engineer II at Microsoft in Redmond or Seattle, in their first few yea…
For developers
The same search, from your own code.
Everything the interface does is an endpoint: a sentence in, a ranked shortlist with the evidence out, or an exact filter set in and a deterministic page out. Point an assistant at /api/mcp and it can do the same thing mid-conversation.
curl https://www.refolk.ai/api/v1/search \
-H "Authorization: Bearer $REFOLK_API_KEY" \
-d '{"query": "Staff Rust engineers in NYC"}'No SDK to install. Read the API documentation.
From the blog
Playbooks and field notes.
Headhunting, sourcing, and prospecting - written for people who actually have to do it.
- 9 min read
Heidi Cut 108 as Its CTO Chose Robotics. Pitch the FHIR Engineers First
Heidi Health cut 108 roles as CTO Yu Liu left for robotics. Which Melbourne clinical AI engineers to source first, and the skill signals to search for.
Read post → - 9 min read
Connected Apps Earn Up to 2.9x the Messages. Source Who Skipped Them
LinkedIn Hiring Assistant 2 boosts verified, receptive profiles with Connected Apps, so shortlists overlap. Here is how to find the engineers it ranks last.
Read post → - 10 min read
Qualcomm's 'Performance' Cuts Follow a 26% Handset Drop. Call Modem Teams
Qualcomm layoffs 2026 are labeled performance cuts, but handset revenue fell 26%. How to vet, find, and hire modem and DSP engineers before WARN lists exist.
Read post →
Questions
The short version.
What is Refolk?
Refolk is an AI agent for headhunting and prospecting. Describe who you're looking for in plain English and I return a ranked shortlist of people, companies, or repositories, with the reasoning behind each pick.
What can I search for?
People - engineers, founders, operators, investors. Companies - by industry, stage, geography, or investor. GitHub repositories and the maintainers behind them. If it's on the open web, I can probably find it.
Who is it for?
Anyone whose job starts with finding a specific person or company. Headhunting and sourcing, sales and partnership prospecting, investor deal flow, market and competitor research. It is the same search either way: describe who you want, read the shortlist, see why each name is on it.
Where does the data come from?
Public LinkedIn and Crunchbase records, GitHub, and the open web - read live at search time, not from a stale database export.
What does it cost?
You can start for nothing: 500 free credits, no card required, and a balance that refills every month for as long as your account is open. Paid plans raise that monthly number when the free one stops being enough.
Do I need a credit card?
No. Signing in with your email is enough. Credits are granted to your account directly.
Is there an API?
Yes, and an MCP server with it. The same two searches run from your own code over one HTTP endpoint and one key, or from inside Claude, Cursor, or VS Code as tools your assistant can call mid-conversation. Same account, same credits, no separate API plan.
How is this different from LinkedIn or GitHub search?
Those tools need exact filters and keywords. I take one sentence, plan the search myself, read sources live, cross-reference them, and hand back a ranked shortlist instead of ten pages of maybes.
Can I use it from my own code?
Yes. Both searches are a keyed HTTP API, and there is an MCP server so Claude, Cursor, VS Code, or anything else that speaks the protocol can run them mid-conversation. Same account, same credits, documented in full at /developers.
More detail on the pricing page, and in the API documentation.
Find anyone. Just ask.
Your first searches are on me - 500 free credits, no card required.