Skip to main content

Skip the wiring — install the tako-graph-agent skill

One command teaches your coding agent this whole workflow: resolve names to nodes, read what data exists, compose pinned searches, and report gaps honestly.

​
When to use the Data Graph

The Data Graph is Tako’s index of what its curated data covers. Every entity (companies, countries, teams, commodities) and every metric (revenue, CPI, win percentage) is a node, and real relationships connect them. Query the Data Graph before you call Search. Your agent then searches for data that exists, pins the nodes it resolved, and reports what’s missing. Use it when:

You want to know what Tako has before you search

Resolve a name, such as Nvidia or inflation, to real graph nodes, then read what data exists for them. You spend searches on confirmed coverage instead of on guesses.

You want deterministic grounding

Pin resolved node ids into Search with sources.data.node_ids, and each pinned node becomes a retrieval candidate. To return only the cards that match your nodes, add strict: true.

You want real relationships, not model memory

Read competitors, subsidiaries, industry peers, and cohort members off named graph edges such as rel:competes_with and members. A database read replaces the recalled list that produces a hallucinated comparison.

You want honest gaps

If the Data Graph can’t ground part of a question, your agent can say so: “Tako has X and Y, but not Z.” An empty result is an honest answer, not a failure.

​
Endpoints

​
Free to call

No credits consumed

Graph calls use the same X-API-Key header as every Tako endpoint, and they consume no credits. Rate limits are the only bound: 180 calls per minute, and 10,000 per day.

Explore the Data Graph at tako.com/data

Sign in to your Tako account and browse the Data Graph. Search any entity or metric, walk its relationships, and see what your agent sees before you write any code.
Warning: A listed metric doesn’t prove that Tako covers that exact entity-and-metric pair. A node’s related metrics come from the datasets that cover the entity, so treat a listed metric as strong evidence and confirm it with a search.The Data Graph also isn’t the whole index. Stock prices, market quotes, rankings, and overviews often sit outside it, and Search still returns them. If the Data Graph returns a thin result for an entity you expect Tako to cover, search anyway before you report a gap.
1

Resolve the entity

The response holds nodes with id, name, aliases, and subtype. Pick the company node and keep its id.
2

See what data exists for it

The response holds the metrics that match “revenue”, ranked by popularity and match strength. These are the combinations Tako covers.
3

Search, pinned to what you resolved

Search makes every pinned node a retrieval candidate and boosts it. Organic results don’t change.

​
Next steps

  • For your coding agent — the complete build reference: every parameter, label boost, relation kind, response shape, and common mistake.
  • Building an agentic app? Install the tako-graph-agent skill. It packages the discover, ground, and report-gaps loop for your coding agent.