Signal

Industry inflections

GET/api/v2/industry-inflectionsUS only

Coverage: US
Billing: 1 cr / call

This dataset identifies common industry changes disclosed across multiple listed companies. Each result summarizes one shared change, its scope and severity, market attention, and company-level effects.

It is built from earnings calls held by US-listed companies after July 2026 and refreshed daily as new calls and evidence arrive. Existing themes are updated in place and retain the same change_id.

Results are evidence-based research, not share-price predictions. Raw transcripts are not included.

Questions this endpoint answers

What material changes in industry rules or the competitive landscape are under way this quarter?
Which themes discuss a given industry topic or mechanism?
Which companies does a change affect, and what are the direction, degree and stage for each?
Which changes may not yet have drawn enough market attention?

Query parameters

Parameter	Type	Required	Description
keyword	string	optional	Case-insensitive literal text contained in name or change_summary; 1–200 characters.
ticker	string	optional	Up to 10 comma-separated US ticker symbols; matches themes where any supplied company is a source company or an affected company.
limit	int	optional	Maximum 10. Default 10.
page	int	optional	Starts at 1. Default 1.

Sorted quarter desc, change_id asc. Paged with limit and page (pages start at 1); fewer rows than limit means the last page.

Response fields

Field	Type	Description
change_id	string	Stable public ID of the inflection theme; it stays the same when the content is updated
quarter	string	Research quarter the theme belongs to, in 2026Q2 format
name	string	Short English title of the inflection theme
regime_type	string	Change mechanism: regulation \| competition \| pricing_cost \| demand \| supply \| customer_access
impact_scope	string	Impact scope: company_limited (mostly confined to a single company) \| industry_wide (several companies in the same industry) \| cross_industry (affects several industries through the supply chain or customer relationships) \| systemic (systemic, beyond any single industry or supply chain)
impact_degree	int	Impact degree of the theme: 1 limited, 2 significant, 3 structural; not a prediction of share price movement
attention_verdict	string	Market absorption verdict: overlooked (not noticed) \| partly (partly absorbed); new enum values are additive-only
change_summary	string	Research summary (currently in Chinese) covering the change, its cause and its before-and-after state, the transmission mechanism, market absorption, supporting figures, counterexamples and the limits of the judgment
first_seen	date	Date the theme was first identified
source_tickers	string[]	Companies whose own earnings call disclosures form the primary basis for the theme (canonical ticker)
company_impacts	object[]	The specific impact on each company the theme affects, and the evidence status. The array is not limited to source_tickers: besides the source companies it also carries affected companies identified by the cross-company synthesis whose own earnings calls did not disclose the change; the relationship and evidence strength of each impact are given by that entry's own relation / evidence_status, independently of whether it is a source company. Each entry contains ticker, relation (direct \| indirect), direction (positive \| negative \| mixed \| unclear), magnitude (1–3, null when the degree cannot be determined), impact_stage (realized \| emerging \| not_yet \| unclear), evidence_status (confirmed \| inferred), affected_business (the business involved) and impact (the impact judgment and its limits). The array may contain companies in markets outside the product scope (such as KR); they are kept as analysis content only and cannot be used as a query entry point for this API

Request

curl -H "X-API-KEY: $DRILLR_API_KEY" \
  "https://gateway.drillr.ai/api/v2/industry-inflections?keyword=pricing&ticker=UFI"

Response · 200

{
  "data": [
    {
      "change_id": "theme_0652186192fd13ab",
      "quarter": "2026Q2",
      "name": "Conflict feedstock rationing re-sorts who can supply",
      "regime_type": "competition",
      "impact_scope": "cross_industry",
      "impact_degree": 2,
      "attention_verdict": "partly",
      "change_summary": "变化: …",
      "first_seen": "2026-08-13",
      "source_tickers": [
        "ANSLY",
        "GRSXY",
        "UFI"
      ],
      "company_impacts": [
        {
          "ticker": "UFI",
          "relation": "direct",
          "direction": "positive",
          "magnitude": 2,
          "impact_stage": "realized",
          "evidence_status": "confirmed",
          "affected_business": "Brazil segment …",
          "impact": "…"
        }
      ]
    }
  ]
}

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.