resolve_insights
resolve_insights is the catalog browser for OnFire’s insights — the
curated signal layer pre-computed per person and per company:
technologies (“Snyk”, “Kubernetes”, “CrowdStrike”), personas and roles
(“code_contributor”, “devops”, “secops”), seniority
(“seniority_executive”), and buying authority.
It is optional. ask_onfire runs without it,
resolving the insight values you pass when the query is submitted.
When to use it
Section titled “When to use it”- Before an
ask_onfirequery that filters on a role or technology, when you want the exact value up front. Batch it with your other preparation calls (e.g.match_company) so it costs one round-trip. - To check the exact spelling of a persona or vendor before reusing it across several filters.
- To read an insight’s
coverageband before betting a query on it.
Inputs
Section titled “Inputs”| Parameter | Type | Required | Description |
|---|---|---|---|
concepts | string[] | Yes | Free-text terms to resolve, e.g. ["snyk", "code contributors", "devops"]. |
kind | string | No | Confine the search to one family — "persona" or "technology". Omit for both. |
Pass kind whenever you know the family: without it a persona phrase can
match the technology index (e.g. “sales” → “Salesforce”).
Returns
Section titled “Returns”{ "results": [{ "concept": "devops", "matches": [] }], "resolved_count": 0, "unresolved_count": 0, "confident_count": 0, "weak_count": 0, "how_to_use": "..."}Each match carries:
insight_value— the canonical value to use in aninsight_filter.kind—personaortechnology.categoryandmatchtier — onlyexact/synonymare confirmations;partialandfuzzyare candidates to eyeball.coverage—common/moderate/thin/none: how many people carry the insight overall.
Both families are concept-searched, technologies (~1,600) included — pass the roles and vendor names you care about.
Using a resolved value
Section titled “Using a resolved value”An insight value is the value of an insight_filter on an
ask_onfire query:
{ "entity": "contact", "select": ["full_name", "job_title", "current_company_name"], "insight_filters": [ { "kind": "persona", "value": "devops" }, { "kind": "technology", "value": ["Datadog", "Kafka"] } ], "limit": 50}A list of values inside one filter means OR. On the company entity an
insight filter can also carry min_count — the minimum number of active
employees carrying that insight.
Notes & limits
Section titled “Notes & limits”- A concept absent from the persona catalog is the case where a
job_title contains [...]filter is the right instrument. A concept present in it should be filtered as a persona — including when the question names one company. - Insight matching is case- and space-sensitive server-side; always reuse
the returned
insight_valueverbatim. - Read-only and free.