Migrate from Tako
Keep the Tako SDK. Change the host and the key.
typesearch speaks Tako Search v3 for web results, in the same format. With the official SDK, migrating is two lines.
from tako import Configuration, SearchRequest
from tako.lib import Tako
config = Configuration(host="https://api.typesearch.ai/compat/tako/api") # before: Configuration()
config.api_key["apiKey"] = TYPESEARCH_API_KEY # before: TAKO_API_KEY
r = Tako(config).search(SearchRequest.from_dict({
"query": "Boca Juniors",
"sources": {"web": {"count": 10, "category": "sports"}},
}))Partial, on purpose
Tako returns two things: data cards (charts built from licensed datasets) and web results. Web results
come back complete and in the same format. Data cards come back empty, with unsupported:data_cards in
X-Compat-Warnings; a request that only asks for cards returns empty without searching or billing.
Parameters
| Tako | On typesearch |
|---|---|
effort | instant → ultra · fast → fast · deep → deep. |
sources.web.count | Same, 1–20. |
sources.web.category | sports → the sports section · finance → economy · news → everything. |
include_domains, exclude_domains | Same. |
published_after, published_before | Same. |
highlights | Verbatim excerpts from the articles that were read. |
include_contents | content comes back null (limited:content): excerpts only. |
output_settings.flat_results, force_refresh | Same. |
Errors keep Tako’s format: { error_message, error_type }.
Our extras
Add a typesearch field to the JSON body for tone, essentials, a mode or a cost cap; it comes back in a
typesearch field of the response. For everything else, the native API and our
SDKs expose all of it.
What stays with Tako
If your product is built on Tako’s licensed data cards and charts, or on answers synthesized by the API itself, keep those on Tako and move your web search here.