<summary>Find companies whose technographic profile matches a target tech stack.
Use ONLY when the user explicitly wants to discover companies BY THEIR
INSTALLED TECHNOLOGY — e.g. "find DTC brands using Shopify and Klaviyo",
"who runs Snowflake AND Looker", "US e-commerce companies using HubSpot".
For hiring-signal discovery (companies posting jobs that mention a tech),
use `theirstack_search` instead — that surfaces investment intent,
whereas this surfaces installed base.
That installed base is what TheirStack DETECTS from job-posting text, not
from crawling storefronts, so it only sees companies that hire and name the
tool in their JDs — treat a company's absence as "not detected here," not
"not using it" (a storefront-sniffing method like BuiltWith/Wappalyzer
would surface more).
For ecommerce-platform tools, results may include the platform's SERVICE
PROVIDERS (agencies, ISVs) alongside actual merchants — job mentions don't
distinguish "we run on Shopify" from "we sell to Shopify merchants," so
name the kind of company you want in `criteria` and the check filters
them out. Recruiting agencies are always excluded (company_type =
direct_employer), matching theirstack_search.
Costs 1.5 Sliq credits per company returned; a failed search is free.
In chat, STATE THE COUNT AND THE COST in the same reply as the
results — every time, without stopping to ask first. Use the user's
number when they gave one, otherwise the default: "pulled 25
companies — 37.5 credits; say if you want more, max 100." Price the
companies actually returned, which `count` gives: fewer than `limit`
costs less. Because this endpoint pages, prefer one page at the
user's number over silently walking `offset` past it — every extra
page is more credits.
Each company returned is then checked against `criteria` on its own,
reading its name, firmographics and technologies, and only
the matches come back in `companies`; the rest come back in `rejected`
as {name, reason}. It adds a few seconds per ten companies.
When this runs in an agent, every company with a domain is saved to the
Output tab as a company row (deduped by domain) with its verdict,
carrying its firmographics and matched technologies; the rejected ones
are hidden from the list's default view.
The tool resolves each technology name to a TheirStack catalog slug
(calling /v0/catalog/technologies per name; popularity tiebreak; exact
name match wins), then queries /v1/companies/search with
`company_technology_slug_and` so EVERY supplied technology must be
present on the returned company.</summary>
<returns>
<description>{
"companies": [
{
"id": str, "name": str, "domain": str | None,
"industry": str | None, "employee_count": int | None,
"country_code": str | None, "linkedin_url": str | None,
"technologies_found": [
{"slug": str, "name": str, "confidence": str,
"jobs": int, "last_date_found": str},
...
],
"verdict": str | None, # 'qualified', 'unclear', or None when the check couldn't run
"verdict_reason": str,
},
...
],
"rejected": [{"name": str, "reason": str}, ...], # companies the check turned down
"count": int, # companies in this page, rejected ones included; the number billed
"total_matches": int, # universe size for this query (or None)
"created_identifiers": [str], # domains of matching companies this call newly added to the list
}
On upstream failure (timeout / 5xx / connection error), returns
`{"companies": [], "count": 0, "theirstack_available": False}`
so the agent can read the flag and degrade gracefully.</description>
</returns>