What is a developer intent data API?

It is an API that turns public developer activity into queryable buying signals. DataForGTM derives developer intent from GitHub activity — what repos, orgs, and technologies developers and their companies are engaging with — and exposes it through the developer_intent and company_intent tools, callable via MCP or OpenAPI with a bearer key.

How is developer intent data different from traditional B2B intent data?

Traditional B2B intent infers interest from content consumption across thousands of topics. Developer intent here is narrower and behavioral: it reads observable GitHub activity around specific repos and technologies, then lets you resolve a signal to a person. It is signal, not a guaranteed purchase, and it only covers developer tooling.

Agent-first · MCP / OpenAPI · no dashboard

Developer intent data API: GitHub buying signals you can query

A developer intent data API turns public GitHub activity into a question your AI agent can ask: which developers — and which companies — are actively working with the technology you sell? DataForGTM exposes that as two callable tools, developer_intent and company_intent.

What "developer intent" actually means here

Most intent data infers interest from page visits or form fills. Developer intent is different: developers signal what they're evaluating through what they do in public — starring, forking, opening issues, contributing, and adopting a library, repo, or ecosystem. DataForGTM reads those GitHub activity signals and lets you query them two ways:

developer_intent — find individual developers showing activity around a specific repo, org, or technology category.
company_intent — rank companies whose developers are active on the tech you sell, so you can prioritize accounts.

This is signal derived from public GitHub activity. It tells you who is engaging with a technology — not a guaranteed purchase intent, and not a substitute for qualifying the account.

How an agent calls it

Point any MCP-aware client or OpenAPI connector at the endpoint and authenticate with a bearer API key. The discovery documents describe every tool and its schema:

# OpenAPI / MCP discovery
https://dataforgtm.ai/api/v1/openapi.json
https://dataforgtm.ai/.well-known/mcp/server-card.json

A common workflow is to pull company- or developer-level intent, then resolve the people behind a signal to a real LinkedIn profile with deanon (charged 2 credits, ~$0.30, only on a hit — misses are free):

# Resolve a GitHub username surfaced by an intent query → 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

Developer intent is a narrow slice of the intent-data market. Here is an honest read of where DataForGTM fits — and where it doesn't.

Capability	DataForGTM	reo.dev	Scarf	Bombora / 6sense
Developer-level intent from GitHub activity	✅ as an API	✅ (platform)	Partial (download/registry)	❌ topic/B2B intent, not dev
Company-level intent ranking	✅	✅	✅ company-only	✅ broad topic coverage
Resolve a signal to a person (GitHub → LinkedIn)	✅	In-platform	❌ no PII	❌
Agent-discoverable MCP / OpenAPI, self-serve	✅	Gated connector	Partial	❌
Breadth of intent topics beyond developer tooling	❌ GitHub/dev only	❌ dev only	❌ dev only	✅ thousands of B2B topics

When another tool is the better fit

If you need broad B2B intent across thousands of non-developer topics, Bombora or 6sense cover far more ground than GitHub activity ever will. If you want a full dashboard, dedup, and a CRM-integrated workflow over developer signals rather than raw API calls, reo.dev's platform may be a better experience. If you only need company-level adoption of an open-source project and want zero PII handling, Scarf is purpose-built for that. DataForGTM is the right pick when you want developer/company GitHub intent as a plain, agent-callable API — and the ability to resolve a signal down to a specific person.

Pricing

Prepaid credits, pay-per-use, no subscription. Intent queries and a successful deanon resolution (2 credits, ~$0.30; misses free) draw down the same balance. Your agent can check usage and top up with a Stripe link in chat. Start with the self-serve trial via signup — no demo, no seat, no dashboard.

Start

Start a trial and get an API key, or read the full schema at /api/v1/openapi.json.

FAQ

What is a developer intent data API?: It is an API that turns public developer activity into queryable buying signals. DataForGTM derives developer intent from GitHub activity — what repos, orgs, and technologies developers and their companies are actively engaging with — and exposes it through the developer_intent and company_intent tools, callable via MCP or OpenAPI with a bearer key.
How is developer intent data different from traditional B2B intent data?: Traditional B2B intent (Bombora, 6sense) infers interest from content consumption across thousands of topics. Developer intent here is narrower and behavioral: it reads observable GitHub activity around specific repos and technologies, then lets you resolve a signal to a person. It is signal, not a guaranteed purchase, and it only covers developer tooling.