Deep Research

Decide whether a single, known company fits your criteria in terms of recent activity and organizational structure as a qualifier.

<Info>No API key yet? Sign up via Agent Auth to get your X-API-Key - the only required header for this endpoint.</Info>

Combine an activity question (answered from job postings) and a team-composition question (answered from LinkedIn people) in a single call, with cited evidence per stage. Provide a domain plus at least one of activity_question or qualifier_question.

If you are not sure which domain OpenFunnel has indexed for a company, call Lookup Companies first. It accepts company names, domains, and LinkedIn URLs and returns the normalized company/domain records you can pass into Deep Research.

Each parameter is hard-wired to a specific data source - pick the one that matches where the answer lives:

activity_question → answered from the company's recent job postings. Use for hiring intent, team expansion, tech-stack adoption visible in JDs, geographic hiring footprint, count/spike questions, first-time hiring or first-time JD mentions, and recent-hire intent.
qualifier_question → answered from LinkedIn people data (current-employee profiles). Use for team composition, roles already filled, org structure (e.g. "has a Head of Security", "has ≥5 SDRs and a Sales Director", "has a dedicated AppSec team").

Activity question examples by category:

Single-role hiring: "Is this company hiring SDRs based on recent job postings?"; "Do their recent job postings show developer relations engineer hiring?"
Initiative/team buildout: "Do their job descriptions suggest they are building an AI customer support automation team?"; "Do recent postings indicate they are staffing a data governance program?"
Tech/vendor/concept mentions: "Are they posting roles that mention Snowflake in at least 5 job descriptions in the last 90 days?"; "Do their job postings mention Salesforce more than 3 times this month?"
Role-count hiring: "Have they posted more than 5 SDR roles in the last 90 days?"; "Are they expanding platform engineering with at least 4 platform engineer postings in the last 60 days?"
Concept-count hiring: "Are they building around AI automation, with at least 4 related job postings this quarter?"; "Are they staffing generative AI work, with 6 or more related job postings in the last six months?"
Relative spikes: "Does their recent job activity show a spike in SDR hiring?"; "Are data engineer postings up 40% week over week?"; "Are Kubernetes mentions in their job descriptions up 80%?"
Recent-hire intent: "Does recent hiring activity suggest they brought someone in to build outbound sales?"; "Does recent hiring suggest they brought in a leader to stand up product security?"
First-time signals: "Is this the first time their job postings mention Kubernetes?"; "Are they hiring Solutions Engineers for the first time?"; "Does this look like their first Head of Data hire?"

Qualifier question examples by category:

Named team / product ownership: "Which engineers are in the Dropbox Dash team?"; "Which VP + sales people are in the AWS Textract team?"
Recent people changes: "New joiners in sales in the last 60 days"; "Any recent GTM engineering hires in sales in the last 90 days?"
Team-size / count checks: "Do they have more than 2 customer support people?"; "Do they have at least 5 SDRs/BDRs?"
Seniority / role coverage: "Do they have a VP or Head of Data Platform?"; "Do they have a Head of Security?"
Specialized teams / skills: "Do they have a dedicated AppSec / product-security team?"; "Do they employ Kubernetes-experienced platform engineers?"

Pass both activity_question and qualifier_question when a question spans both signals - each stage runs against its own data source and returns independent evidence.

Each stage returns a natural-language answer suitable for inline display, a boolean qualified verdict, and structured source evidence. Activity evidence is returned in activity.sources; qualifier evidence is returned in qualifier.sources. Job sources include title, URL, location, created timestamp, and why-relevant reason. People sources include name, title, LinkedIn URL, seniority, department, and start date when available.

Credits: charged per call, not per source returned. 1 successful call (at least one stage produced a finding) = 1 charge at the per-call price configured for your workspace. A 404 (domain could not be resolved) is free. The exact amount billed is returned in credits_consumed on every response.

X-API-Keystring required

Your OpenFunnel API key. Get one via Agent Auth.

Request body

domainstring required

Company website domain to research (e.g. 'stripe.com'). Protocol and www. prefixes are stripped automatically. The domain is resolved to a LinkedIn org via the internal companies index before either stage runs. If this does not resolve, use Lookup Companies to find the normalized indexed domain.

activity_questionstring nullable

Answered from the company's recent job postings. Natural-language description of the activity signal to look for in open roles. Use this for hiring intent, team expansion, tech-stack or vendor adoption visible in JDs, geographic hiring footprint, count/spike questions, first-time hiring, first-time job-post mentions, or recent-hire intent. Examples: Is this company hiring SDRs based on recent job postings?, Do their job descriptions suggest they are building an AI customer support automation team?, Are they posting roles that mention Snowflake in at least 5 job descriptions in the last 90 days?, Have they posted more than 5 SDR roles in the last 90 days?, Are data engineer postings up 40% week over week?, Is this the first time their job postings mention Kubernetes?. Pass null or omit to skip this stage.

qualifier_questionstring nullable

Answered from LinkedIn people data (current-employee profiles). Natural-language criteria about who already works at the company or how the org is shaped. Use this for team composition, named teams/products, roles already filled, seniority coverage, team-size/count checks, recent joiners or start-date questions, and skill/team specialization. Examples: Which engineers are in the Dropbox Dash team?, New joiners in sales in the last 60 days, Do they have more than 2 customer support people?, Has at least 5 SDRs/BDRs and a Sales Director, Has a dedicated AppSec / product-security team. Pass null or omit to skip this stage.

timeframe_daysinteger

Lookback window (days) used by the activity stage. Has no effect when activity_question is omitted.

max_jobs_to_checkinteger

Upper bound on the number of recent job postings the activity stage scores with the LLM relevance pass. Higher values raise recall but add latency / token cost (each job is judged by an LLM call). Default 25 is tuned for interactive use; bump it for batch / data-extraction workflows where you want maximum recall. Has no effect when activity_question is omitted.

Example request

{
  "domain": "usepylon.com",
  "activity_question": "Have they posted more than 5 SDR roles in the last 90 days?",
  "timeframe_days": 90,
  "max_jobs_to_check": 25
}

Response

Research findings with natural-language answers and source evidence.

domainstring required

Echo of the requested domain (normalized).

credits_consumedinteger

Credits charged for this call. Charge is recorded in the background after the response is sent. 0 when the call failed before producing any findings.

latency_msinteger required

End-to-end request latency in milliseconds.

v1

Deep Research

Headers

Request body

Example request

Response