Notes
- Authenticated, no credits — send the same
X-API-Keyheader as every Tako endpoint. Graph calls consume no credits; rate limits are 180/minute and 10,000/day. - Start from a
node_idreturned by Graph Search, then use graph related to find which entity + metric combinations Tako actually covers. Once you’ve found a covered combination, query Search (/v3/search) or Answer (/v1/answer) for it — pinning the ids viasources.data.node_ids. - Results in each group are ranked by popularity, blended with how strongly each node matches
qwhen a filter is provided. On big entities, always passq— unfiltered, a big entity returns hundreds of items.
Response shape: overview vs. one group
The response always includes the resolvednode. The rest depends on whether you paginate:
- No
relation→relationsholds an ordered overview: one group per relation, each{key, kind, label, items (preview), total, total_capped}. Named semantic edges come first, then membership, data, and siblings; empty groups are dropped. relation=<key>set →relationholds a single paginated page for that one group, withitems,total,total_capped, and anext_cursor. Passnext_cursorback ascursorto page through. Items live inrelation.items.
kind:
An unknown
relation key returns 200 with empty items, not an error — so a typo’d key reads as “no relation.” Keys are per-node: read the overview to discover them, then drill.Narrowing with q
The optional q is a case-insensitive substring filter on related nodes’ names/aliases. It filters every group of the overview, or the single paginated group when relation is set:
label/infer_label boosts work as on Graph Search and apply within each group; inference runs only when q is set.
Capped totals
total stops counting at 250: total_capped: true means the true count is at least total — render it as “250+”. Pagination also ends at the cap, so narrow with q to reach the tail.
A
404 means the node_id does not resolve. A node with no relations returns 200 with empty groups — that’s the normal “nothing connected” outcome, not an error.