COMPUTED
Follow-on from Hiring — exposed via API when written
COMPUTED
Pull stack motion inferred from hiring evidence.
Tool Adoption is computed from prior Hiring — one live row per tool per company when usage intent is clear. Wire it to enrich accounts with stack context without a separate technographics crawl.
- Computed from Hiring evidence — available when a Tools row writes
- One live row per company + tool, refreshed in place
- Firehose for stack changes; dossier for full tool set
- Stronger when job text shows real usage intent
REST and firehose require the API Access add-on on Pro. Docs stay public.
tool-api.previewPro
POST outbound · Settings → Webhooks · type=tool
POST /api/v1/companies · signal_query: "signal:tool:30d"
GET /api/v1/companies/{id}
At a glance
How this signal type shows up in the API
1 tool
One live row per company and catalog tool
Hiring
Not a separate install fingerprint feed
Stack
Dossier returns tool rows beside other timeline signals
What you get via API
Stack context as scored timeline facts
When Hiring keeps pointing at a catalog tool, VeilStrat writes or refreshes a Tool Adoption signal. With Pro and API Access you can subscribe to those writes and read them from company search and dossiers.
Use Tools to personalize outreach and to route accounts to the right product specialist.
- Subscribe to Tools for stack-change automations
- Read all live tools from the dossier after any related ping
- Pair with Hiring subscriptions when you need the underlying roles
Integration loop
Stack write → enrichment field
Keep tool fields current without polling. Enrich on firehose, then map catalog tools into CRM multi-selects.
- 01
Subscribe to Tools
Enable Tool Adoption on the firehose for stack motion events.
- 02
Map live tools into CRM
GET /api/v1/companies/{id} and write tool names into enrichment multi-selects.
- 03
Route to specialists
Branch ownership by LangChain vs Claude vs OpenAI evidence from the dossier.
- 04
Bounded discovery
Occasionally search with a tool signal_query for net-new accounts — keep pages small.
Example calls
Common Tool Adoption API patterns
Illustrative requests for stack enrichment workflows.
Search
Companies with recent Tool signals
Find accounts showing stack motion in-window.
curl -s -X POST "${BASE_URL}/api/v1/companies" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "signal_query": "signal:tool:30d", "page": 1, "pageSize": 50 }'Enrich
Dossier for live tool rows
Pull the full scored timeline including Tools after a webhook.
curl -s "${BASE_URL}/api/v1/companies/COMPANY_UUID" \
-H "Authorization: Bearer YOUR_API_KEY"Catalog
Discover filter ids
GET /filters before building advanced search payloads.
curl -s "${BASE_URL}/api/v1/filters" \
-H "Authorization: Bearer YOUR_API_KEY"GTM automations
Where Tool API hooks land
Turn stack evidence into routing and personalization without a second data vendor.
Enrichment
Maintain live stack fields
Update CRM multi-selects when Tool rows write or refresh.
Routing
Send accounts to specialists
Branch ownership by LangChain vs Claude vs OpenAI evidence.
Personalization
Cite tools in first-touch copy
Inject tool labels from the dossier into sequence tokens.
Partners
Co-sell into shared stacks
Alert partner managers when mutual ecosystem tools appear.
Evidence rule
Hiring-backed, not install-backed
Tool Adoption is not a browser fingerprint or OAuth scrape. API consumers get stack motion VeilStrat inferred from hiring evidence.
Related
Keep exploring this signal surface
Jump to the buyer-facing signal guide, sibling APIs, or the technical docs.
FAQ
Tool Adoption API, answered
Stack enrichment questions before you ship jobs.
No. Tools write only when hiring evidence supports a catalog tool with enough intent. Many Hiring pings will not produce a Tool firehose event.
Enrich accounts withhiring-backed stack proof.
Subscribe to Tool Adoption, map live tools into CRM fields, and personalize outbound with the same evidence as the dashboard.
REST and firehose require the API Access add-on on Pro. Docs stay public.
© 2026 VeilStrat. All rights reserved.All systems operational