Intelligence Jobs
Deep analysis runs as an async job:
POST /intelligence/jobssubmits it and returns ajobIdright away.GET /intelligence/jobs/{id}polls it until it hassucceeded, then returns the result.
Most jobs finish in 10–40 seconds. Not sure which job you need? See Choosing the Right Call.
Submit
cURL
estimated_cost is the most the job can cost. Those credits are held until it finishes, and you’re charged only for what it actually used.
Two other responses are possible:
200withfromCache: true: you ran the same job recently, so the result comes back right away. No need to poll.202withdedup: true: the same job is already running. Poll thejobIdyou got back.
Poll
cURL
Poll every 2–5 seconds. status goes queued → running → succeeded or failed. window: "all" and large jobs can take 1–3 minutes; allow up to 5 before treating a job as stuck.
Large results (usually big records jobs) come back as a download link instead of result. If you see resultUrl, GET it for the full JSON. The link lasts about an hour; poll the job again for a fresh one.
Results are kept for about 24 hours. After that, polling returns 410. Store anything you need longer.
Inputs
insights
Each narrative in an insights result includes:
label,summary,topTagsandrepresentativeContent[](its top 8 posts).corpusEvidence: how big the narrative is across the whole corpus, not just your results, and whether it’s growing.persistentLink.narrativeId: pass it toGET /narratives/{id}to follow the narrative over time.
patterns
No window. See Pattern Intelligence.
stats
Returns { query, window, total, platforms[] }, an exact count over everything that matches.
records
Each post is a content object.
Through the MCP
In an AI assistant, the hosted MCP’s kinetk_get_context tool submits a job and waits for the result in one step. See What You Can Ask.