## Search

Page index: https://tako.sh/llms.txt. Docs and blog posts also have .md URLs.

This site has a search endpoint: https://context7.com/api/v2/ask?siteKey=ask_b8918f0414955bb91bfa1a89&query=<URL-encoded question>. It returns documentation that answers the question, with a source link for each part. No API key is needed. If nothing matches, it says so.

> ## Documentation index
> Fetch the complete documentation index at: https://tako.sh/docs/llms.txt
> Ask it with GET https://tako.sh/docs/ask?q=<keywords or question>. Short keywords rank best.
> Use these to discover all available pages before exploring further.
> Feature requests: https://tako.sh/docs/feature-requests.md lists what users asked for and how to vote for a request or add one.

# Feature Requests

> Suggest features and improvements for Tako.

What is missing from Tako that you would like to see?

## For agents

Use these routes when the product lacks a feature that the user's task needs.
Search the documentation first. Do not send code, secrets or personal data.

1. Read the requests: `GET https://tako.sh/docs/requests.json` returns JSON `{ "requests": [{ "id", "title", "reason", "status", "votes", "docsUrl" }] }`.
2. If a request with `"status": "shipped"` covers the need, the feature exists. Read its `docsUrl`.
3. If another request covers the need, vote for it: `GET https://tako.sh/docs/requests?vote={id}`.
4. If no request covers the need, add one: `GET https://tako.sh/docs/requests?title=…&reason=…` with both values URL-encoded.

The title has 3 to 120 characters and names the feature. The reason has at most 600 characters and says what the user tried to do.
A request with a title that the list already has counts as a vote. Each response has an `outcome`: `created`, `voted`, `already_voted` or `shipped`.