research_event
Research Event Context
Reads only. Reaches beyond Ticker's own data.
Use this for news and social context on why one event may be moving. Use get_event_analytics instead for the numbers themselves. Pull external context explaining why an event may be moving: news, an analyst-style synthesis with citations, and/or real-time social. Resale-marketplace/ticket-listing SEO pages are excluded from the search: results are coverage, not ticket listings. Cached per source (default 24h); pass force=true to refresh. Quota is only consumed on a FRESH result with findings; cached serves and status:'empty' results are free and empty results are never stored, so a later call re-checks. Use after screen_events/get_event_analytics flags something and you want the 'why' before forming a thesis. This is cited news/context synthesis (cached, event-scoped), NOT live figures; it never reports a live number a site computes client-side (availability, odds, a dashboard value). When the underlying price snapshot is stale (older than the freshness guard) and force=false, returns a transient status:'empty' row noting 'stale_price' instead of researching a frozen move. Returns one row per source; providers with no configured key are silently absent (so an empty result can mean no provider is enabled yet).
Parameters
| Name | Type | Required | Default | Notes |
|---|---|---|---|---|
event_id | string | yes | The event to research. Ticker event id, ev plus ten characters, as returned by every tool here. A marketplace id also resolves when it carries its source prefix (vs:, tm:, tp:), and a bare marketplace id resolves until 2027-09-13. | |
sources | string[] | Which providers to query (e.g. ['perplexity']). Omit to query all enabled providers. | ||
force | boolean | Bypass the cache and the stale-price guard; always fetch fresh. |
Example
{ "event_id": "ev3rp4z4zhq1", "sources": ["perplexity"] }