Technographics API

List the technologies detected for a company (CRM, analytics, marketing automation, infrastructure, ...), grouped by category. Address the company by org_id (from resolve_company) or domain. tech_source picks the detection signal: "stack" (default) reads only precise website tech-stack scans; "jobs" reads only LinkedIn job-posting mentions of tools (broader reach, softer signal — also catches competitor/integrator mentions, not just tools the company directly runs); "both" merges the two and marks each tool's source(s) so you can tell a confirmed website detection from a softer job-posting mention.

Parameters

Call it from your agent (MCP)

Connect once and company_tech appears in your agent’s toolbox next to every other gtm.dev tool. Claude Code:

claude mcp add --transport http gtm https://mcp.gtm.dev \
  --header "Authorization: Bearer YOUR_API_KEY"

Under the hood, the client sends:

curl -X POST https://mcp.gtm.dev \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"company_tech","arguments":{"domain":"rippling.com"}}}'

other clients (cursor, claude desktop, openai agents sdk, langchain): mcp setup

Call it over REST

curl -X POST https://api.gtm.dev/v1/tools/company_tech \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain":"rippling.com"}'

Errors (401, 402, 429, 400) are listed in the REST reference. Calls that error are not billed — see pricing.

Related tools

• who_is_advertisingAd intelligence API: who is advertising
• who_is_hiringHiring signals API: who is hiring
• find_fundedRecently funded companies API
• company_ad_activityCompany ad activity API
• company_fundingCompany funding data API
• company_hiringCompany hiring data API
• who_uses_techTechnology install base API: who uses a tool