Tako

By Tako

Overview

Tako helps users find current data and metrics from proprietary datasets and the live web as citation-backed charts, retrieve the underlying result content, check available data coverage, and create shareable public chart links from user-provided structured data.

Tools

tako_available_data

ChatGPT

Find what data Tako holds on an entity or a metric, and the canonical name it holds it under. Best for: coverage questions themselves, or a metric's canonical name before a priced search. Put a company, person, or place in q to list the metrics tracked on it; put a metric in q to list the entities it covers. Add metric when you know the measure — you get the resolved pair and a ready-to-run next_call. Search on the canonical names it returns, not your own phrasing — tako_search matches the graph's names, not yours. A name here means the graph tracks it, not that a card exists. If the follow-up search comes back empty, say Tako has no card for it rather than rephrasing the query. Hand a node id to tako_graph_related to see what else connects to it.

tako_contents

ChatGPT

Fetch the full content behind a url: a web page's text, or an exportable Tako card's data rows. Batch up to 10 urls in one call — each one is billed and fails on its own. Fetch only cards that tako_search marked exportable: true. Rows bill per 1,000 delivered, so set max_rows when the recent rows are enough. A website-traffic or SEO card also bills a per-unit data minimum that max_rows doesn't bound. If a page is long, such as a filing or an annual report, set query to a question to get back only the passages that answer it. Best for: reading one source in full — a page you need to quote, or the rows behind a card you need to compute over.

tako_graph_related

ChatGPT

Explore what a graph node connects to — its metrics, the entities a metric covers, competitors, industry, index membership, and sources. Two modes. Pass node_id alone for the map: every relation group with its key, label, total, and its first 3 names. Pass relation to page one group, where each item comes back with the id that explores it. Read a key off the map rather than guessing — an unknown key returns an empty group, not an error. Best for: expanding a node you already resolved. Resolve a name to a node id with tako_available_data first. A metric listed here means the graph tracks it, not that a card exists — tako_search is the final check.

tako_search

ChatGPT

Search Tako's data graph and the live web in one call: many results at once, as structured cards plus web results, with the top card rendered inline as a chart. It finds data; tako_contents fetches it. Each card carries a headline value, node ids, and a url — pass the url to tako_contents for rows (exportable: true cards) or a web result's full page text. When exportable is false the rows are locked — read the headline value from the card's description. Best for: breadth — fan out several narrow queries in parallel. Each query resolves one metric — for one entity, or a comparison set ("Apple revenue", "Nvidia vs AMD gross margin"); several metrics or topics in one query retrieve poorly. To learn what Tako covers, or a metric's canonical name, run tako_available_data first, then search on the canonical name it returns.

tako_visualize

ChatGPT

Create a public, permanent Tako card from data you already have — to chart data Tako already holds, use tako_search. Tako stores what you send, the card never expires, and anyone with the returned url can open it without signing in. Confirm the user wants a public card before you call, then give them the url. Never put sensitive data in components: no passwords, API keys, payment-card or bank details, health information, government identifiers, precise home addresses, or personal data the subject hasn't agreed to publish. Aggregate or anonymize it first, or decline. Each component is {component_type, config}, rendered top to bottom. A titled bar chart is two: {"components": [{"component_type": "header", "config": {"title": "Revenue"}}, {"component_type": "categorical_bar", "config": {"datasets": [{"label": "Sales", "units": "USD", "data": [{"x": "NA", "y": 500}]}]}}]}. Use person_card alone, never beside another component.

Capabilities

InteractiveWrites

Example Prompts

Click any prompt to copy it.

Links

Documentation Privacy Policy

Similar Apps