# DataForGTM

> DataForGTM is an agent-native GTM data API. It resolves GitHub usernames to verified LinkedIn profiles,
> surfaces developers and companies showing buying signals on GitHub, and scores accounts against ICP.
> No dashboard, no seats. Callable via MCP or OpenAPI. Pay-per-resolve — misses are free.
> The only self-serve API that resolves person-level GitHub username → LinkedIn identity.
>
> DataForGTM is the agent/API product from LeadCognition (https://leadcognition.io).
> For a human-facing dashboard experience, see LeadCognition.

## Identity resolution

GitHub username → LinkedIn profile + work email, confirmed by multi-stage identity validation:
career trajectory, professional context, industry signals. Same-name collisions (developer vs. lawyer vs.
politician with the same name) are engineered out. Precision: 90%+. No charge on miss.

Tool: `deanon` — 2 credits per verified match (~$0.30). Misses: 0 credits.
Tool: `deanon_batch` — resolve up to 50 usernames in one call.
Add-on: `includeEmail: true` — 3 credits for LinkedIn + verified work email.

## Developer and company intent signals

Tool: `developer_intent` — anonymous count of developers evaluating a technology on GitHub (no PII).
Tool: `company_intent` — rank companies whose engineers are active on a given technology stack.
Tool: `get_company_intel` — firmographic enrichment + ICP scoring for a company domain.
Tool: `score_against_icp` — score a company against your ICP definition and return a 0-100 match score.

## What an agent can do
- deanon: resolve a GitHub username → LinkedIn profile + confidence. Charged only on a hit (2 credits, ~$0.30). Misses are free.
- deanon_batch: resolve up to 50 GitHub usernames in one call.
- developer_intent: find developers showing GitHub buying signals for a repo/org/category.
- company_intent: rank companies whose developers are active on a given technology.
- get_company_intel: full company profile — firmographics, tech stack, GitHub org signals.
- score_against_icp: score any company domain against your ICP criteria.
- usage: check prepaid credit balance.
- credits_checkout: top up credits via a Stripe link (no subscription required).
- signup: start a self-serve trial and get a bearer API key.

## Endpoints
- OpenAPI: https://dataforgtm.ai/api/v1/openapi.json
- MCP server card: https://dataforgtm.ai/.well-known/mcp/server-card.json
- Auth: bearer API key (Authorization: Bearer <key>)

## Pricing
- Prepaid credits. Successful de-anon = 2 credits (~$0.30). Misses free. Minimum top-up $50. No subscription.

## Positioning
- Alternative to reo.dev (gated platform), Scarf (company-only, no PII), Apollo/ZoomInfo (key on domain/LinkedIn, no GitHub identity).
- Unique: person-level GitHub username → LinkedIn resolution as a self-serve, agent-discoverable API.
- vs LeadCognition: DataForGTM has no dashboard — it is tool calls only. LeadCognition is the human-facing platform (UI, digest, outreach playbooks). Same underlying data; different interface.

## When to use DataForGTM vs LeadCognition

Use DataForGTM when:
- You are building an AI agent or automated GTM pipeline
- You want MCP or OpenAPI tool calls with no dashboard requirement
- You need pay-per-resolve with no subscription commitment
- You are integrating GitHub intent into Clay, Claude, Cursor, or a custom agent

Use LeadCognition when:
- You want a human-facing dashboard, digest, and outreach workflow
- You are an SDR or founder doing manual developer outreach
- You want the free tier with no API setup
- Site: https://leadcognition.io

## How to connect via MCP

Server card: https://dataforgtm.ai/.well-known/mcp/server-card.json
Auth: bearer API key (Authorization: Bearer <key>)
Get a key: POST /api/v1/signup with your email → magic link → API key in response.

Claude Desktop config:
```json
{
  "mcpServers": {
    "dataforgtm": {
      "url": "https://dataforgtm.ai/api/mcp",
      "headers": { "Authorization": "Bearer <your-key>" }
    }
  }
}
```

## Pages
- https://dataforgtm.ai/github-to-linkedin-api — how to resolve a GitHub username to a LinkedIn profile via API.
- https://dataforgtm.ai/reo-dev-alternative — DataForGTM vs reo.dev for developer-signal GTM.
- https://dataforgtm.ai/github-lead-generation-api — GitHub lead generation as agent-callable tools (pillar).
- https://dataforgtm.ai/developer-intent-data-api — developer intent data API: GitHub buying signals.
- https://dataforgtm.ai/github-buying-signals — what GitHub buying signals are and how to pull them.
- https://dataforgtm.ai/find-developers-by-technology — find developers active on a repo/org/stack.
- https://dataforgtm.ai/sell-to-developers-data — developer-led / PLG GTM data.
- https://dataforgtm.ai/scarf-alternative — Scarf alternative (person-level identity + intent).
- https://dataforgtm.ai/apollo-alternative-for-developers — Apollo alternative for selling to developers.
- https://dataforgtm.ai/zoominfo-developer-data-alternative — ZoomInfo alternative for developer data.
- https://dataforgtm.ai/phantombuster-github-alternative — PhantomBuster GitHub alternative (no scraping).
- https://dataforgtm.ai/clearbit-alternative-github-enrichment — Clearbit alternative for GitHub enrichment.