docs: add Tako community provider

[25eliu]

Background

Tako is the knowledge layer for agents, grounding your AI with the most accurate proprietary data and web content.

Tako grounds your agent in two kinds of knowledge at once: proprietary structured data from trusted providers, and full web search. One API returns typed values with named sources when curated data exists, and agent-ready web results and page text for everything else.

Domains Tako covers with proprietary data: finance and markets, company KPIs and earnings, macroeconomics (inflation, unemployment, GDP, policy rates), website and app traffic, sports, weather, elections, prediction markets, demographics, energy, and real estate.

@takoviz/ai-sdk exposes it as three tools, matching Tako's own API surface:

• takoSearch() — knowledge cards plus web results
• takoAnswer() — the same retrieval, blended into a synthesized, source-attributed answer
• takoContents() — the rows behind a card, or a page's extracted text

Summary

Adds content/providers/05-community-providers/53-tako.mdx and the corresponding entry in content/docs/02-foundations/02-providers-and-models.mdx. Docs only — no package changes, so no changeset (per CONTRIBUTING, changesets aren't needed for docs).

The page follows the existing community-provider structure: Setup → Tool Usage (generateText / streamText) → Configuration → Results → TypeScript. It uses <InstallPackages /> and documents configuration as a - **name** _type_ list, matching neighbouring pages.

It also includes a short "With AI Gateway models" example, since Tako's tools are client-executed and compose with a bare Gateway model string without extra configuration.

Precedent for a tool-only provider in this section: nia, supermemory, mem0, mixedbread, zeroentropy.

Relationship to the existing tools-registry entry

Tako already appears in the tools registry at ai-sdk.dev/resources/tools/tako-search (content/tools-registry/registry.ts). That entry is a one-line listing; this PR adds the full provider page it currently links out to GitHub for.

Three fields there could be improved, which I'd like to do in a follow-up PR under feat(tools-registry): per add-new-tool-to-registry.md:

• description covers only takoSearch, not takoAnswer / takoContents
• docsUrl points at the GitHub README rather than https://docs.tako.com
• apiKeyUrl points at the site root rather than the API keys page

Happy to fold that into this PR instead if you'd prefer one change — flagging it separately only because the contributing guide prescribes a different title prefix for registry changes.

Draft status

This documents @takoviz/ai-sdk v3, which is not published yet — npm currently serves 2.0.1, where several documented fields (content_format, exportable, data_freshness, the data source key) do not exist. Holding in draft until v3 ships, then marking ready. Tracking in TakoData/ai-sdk#9.

Notes

• MIT licensed, zero runtime dependencies (ai and zod are peers).
• Types mirror Tako's published OpenAPI document and are contract-tested against it.
• Repository: TakoData/ai-sdk

Verification

• Documented options, defaults, and result shapes checked field-by-field against the package source, not just its README
• isStepCount confirmed against ai@7.0.0's exported types
• Model ids match those used in content/docs/02-foundations and content/providers/01-ai-sdk-providers
• Positioning and the proprietary-data domain list taken from https://docs.tako.com
• Filename follows the section's numbering (53-, next free after 52-neon-ai-gateway.mdx)
• <InstallPackages /> and the internal AI Gateway link resolve against the current tree
• Code samples use single quotes and 2-space indent, matching .oxfmtrc.jsonc
• Docs-only path — konsistent conventions apply to packages/* and are unaffected

[25eliu]

Parking this as a draft for now.

Tako is already listed in the tools registry (content/tools-registry/registry.ts), which renders at /resources/tools/tako-search. Looking at how comparable packages are listed, the tools registry looks like the right home for a tool-only package like this one, with the registry's docsUrl pointing at our own AI SDK integration guide.

I'm opening a small separate PR against content/tools-registry/registry.ts to correct three stale fields in the existing entry. Leaving this one open as a draft rather than closing it, in case a full provider page is wanted later — happy to close it if you'd prefer.