Skip to main content

​
When to use Contents

Contents fetches the full content behind a result you already have from Search or Answer — in agent-ready form. Pass the result’s URL and Tako returns one of two things, depending on what the URL points to:
  • a structured-data CSV export — the exact series behind a Tako card, ready to parse, compute on, or load into a dataframe; or
  • the full extracted contents of a web page — clean, parseable text, not raw HTML.
Reach for it when:

You've already found the result and want the content itself, not prose

There’s no synthesis and nothing to re-derive — the CSV is the card’s data, and the extracted text is the page, ready to use directly.

It's a second step, not a search

Contents operates on a URL you already have: find the result with Search or Answer first, then fetch what’s behind it.

You're building agentic apps that need precise, source-grounded inputs fast

Pull the exact numbers behind a card, or the full clean text behind a web result, and act on real content instead of scraping it yourself.

​
How it fits

Contents operates on a result you already have:
1

Search or Answer with a query

Call Search or Answer with a query.
2

Find the downloadable result

A downloadable result carries a content descriptor in the response (format is csv for a Tako card, text for a web page).
3

Pass its URL to Contents

Pass that result’s URL — a card’s webpage_url or a web result’s url — to Contents to download the data.
A result is downloadable only when it carries a content descriptor in the Search or Answer response. Some results’ underlying data can’t be exported, so they come back without one — that’s expected, not an error. Check for the descriptor and skip Contents for results that don’t have it. Both shapes carry a cost, reported on the descriptor: a card CSV bills a per-export baseline plus a per-row rate, and web-page text extraction bills per page. See Contents pricing.

​
What the content looks like

A Tako card → structured-data CSV. Contents returns the card’s data as a CSV with a header row and one row per data point — the same series the card visualizes. A time-series card comes back keyed by an ISO‑8601 Timestamp (with timezone offset), one column per series:
The header names the series exactly as the card sources it, so the values are self-describing and ready to attribute.

​
Example

Pass a card’s URL — Tako detects the right content from the URL and returns a short-lived download link:
Want the data straight back in the response instead of a download link? Set "mode": "inline". See the For Your Coding Agent page for the full request and response reference.

​
Use cases

Feed exact numbers to an agent. Ask for inline mode and the rows come back in the response body, so the agent computes on real values instead of inferring them from prose.
Load a series into a dataframe. Ask for url mode instead and you get a short-lived signed link rather than the rows, which is what you want when the series is large or a tool reads it directly.
Read the full page behind a web result. Pass a web URL where the examples above pass a card URL — the call is otherwise identical. You get clean extracted text instead of raw HTML, in contents[0].data, ready to drop into a model’s context with no crawler and no HTML parser.