How do I find developers by technology or repo?

Call the developer_intent tool with a GitHub repo, org, or technology category to list developers showing buying signals (stars, forks, issues, contributions) on that technology. Then pass the returned usernames to deanon to resolve each one to a LinkedIn profile.

Can I turn the developers I find into named LinkedIn contacts?

Yes. After finding developers active on a repo or technology, the deanon tool resolves a GitHub username to a LinkedIn profile with a confidence score. You are charged 2 credits (about $0.30) only when it resolves; misses are free. Use deanon_batch to resolve a whole list at once.

Find developers by technology or repo — then resolve who they are

DataForGTM lets you find developers by technology or repo: surface the engineers active on a specific GitHub repo, org, or stack, then resolve each GitHub username to a real LinkedIn profile. Both steps are agent-callable API/MCP tools. You only pay when an identity resolves.

How it works

Finding the right developers is two questions: who is active on the technology I care about? and who are they, really? DataForGTM answers both as separate, callable tools.

Step	Tool	What you get
1. Find	`developer_intent`	Developers showing GitHub buying signals for a repo, org, or technology category — stars, forks, issues, contributions on the projects you sell against.
2. Resolve	`deanon`	A GitHub username turned into a LinkedIn profile with a confidence score. Charged 2 credits (~$0.30) only on a hit; misses are free.
(Bulk)	`deanon_batch`	Resolve a whole list of usernames from step 1 in a single call.

So "find Rust developers contributing to my competitor's repo, then get their LinkedIn" is two API calls — one to list the active usernames, one to resolve them.

Resolve a username (curl)

Once developer_intent hands you usernames, resolve any one of them:

# Resolve a GitHub username → LinkedIn
curl -X POST https://dataforgtm.ai/api/v1/deanon \
  -H "Authorization: Bearer $DATAFORGTM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"githubUser":"torvalds"}'

How it compares

Most tools answer one half of the problem. DataForGTM is the only one that does GitHub-username → LinkedIn resolution as an API — but it is narrower than the platforms in other ways, and we're honest about that.

Capability	DataForGTM	reo.dev	Scarf	Apollo / ZoomInfo
Find developers by repo/org/technology	✅ API	✅ (platform)	Partial (company-level)	❌
GitHub username → LinkedIn (person-level)	✅ API	In-platform only	❌ no PII	❌ keys on domain/LinkedIn
Full GTM platform: dashboards, CRM sync, workflows	❌ API only	✅	Partial	✅
Broad contact database beyond GitHub identity	❌	Partial	❌	✅ (hundreds of millions)
Agent-discoverable MCP / OpenAPI, self-serve	✅	Gated connector	❌	Some

When another tool is the better fit

If you want a managed dashboard, CRM enrichment workflows, and a sales team UI, reo.dev is the better fit — it's a full platform, not a raw API. If you need a large general contact database keyed on company domain or LinkedIn URL, Apollo or ZoomInfo will out-cover us; they just can't start from a GitHub username. If you only need anonymous, company-level package adoption with no PII, Scarf is purpose-built for that. DataForGTM is the right tool when you specifically want to go from GitHub activity to a named person, programmatically, from an agent.

Start

Start a trial to get an API key, or point your MCP client / OpenAPI connector at the OpenAPI spec. No demo, no seat, no dashboard.