Company

Company discovery

GET/api/v2/company-discovery

Coverage: US / CN / JP
Billing: 3 cr / call

Takes natural-language criteria (optionally scoped to a market) and returns every candidate company that passes verification, one row per company, containing only the ticker, the company name and the reason for the match; then call the other endpoints with the ticker.

Division of responsibilities with /tickers: /tickers resolves a known name or code; this endpoint discovers companies from a description.
query is semantic matching, not keyword matching; the endpoint is not paginated and has no limit, and the number of candidates is not capped; the return order is not guaranteed, so do not read row order as relevance.
Scope is US / CN / JP only; HK / KR / TW companies never appear in the results, and market accepts only US CN JP.

Query parameters

Parameter	Type	Required	Description
query	string	required	Natural-language description, such as US companies that design GPUs for data centers, electric vehicle manufacturers with strong dividends; semantic matching, not keywords.
market	string	optional	US CN JP, comma-separated for multiple values. Default All.

Response fields

Field	Type	Description
ticker	string	canonical ticker
company_name	string	Company name
reason	string	The reason the company matches the query criteria

Request

curl -H "X-API-KEY: $DRILLR_API_KEY" \
  "https://gateway.drillr.ai/api/v2/company-discovery?query=US%20companies%20that%20design%20GPUs%20for%20data%20centers&market=US"

Response · 200

{
  "data": [
    {
      "ticker": "NVDA",
      "company_name": "NVIDIA Corp",
      "reason": "Designs data-center GPUs and accelerated-computing platforms, which matches the query for US GPU designers."
    }
  ]
}

No key yet? Create one under API Keys — it is shown once, so store it where your shell can read it. Connecting an agent over MCP instead? That signs in through the browser and needs no key at all.

Authentication, conventions, rate limits and error shapes are the same for every endpoint — they live on REST API.