/theresanaiforthat/tools/search

POST /api/theresanaiforthat/tools/search

Price: 1 credit

Search There's An AI For That (theresanaiforthat.com) AI tools by keyword

How to use it

Keyword search over the There's An AI For That directory. A hyphenated task slug and the same words as a phrase are two different queries with different answers — 'video-editing' reaches for the task's listing document while 'video editing' returns a shorter relevance match — so reach for a slug from /theresanaiforthat/tasks when you want coverage. The directory never reports 'no match': an unrecognised phrase still returns loosely related tools, so treat a result set whose names have nothing to do with the phrase as a miss rather than as evidence the tools exist. A task's listing is one document that renders at most roughly 195 rows regardless of `count`, and for a popular task that is a small fraction of what the directory holds for it (5433 for 'chatbot', per the site's own tab counter), and this endpoint cannot reach anything past that document. Rows flagged `is_promoted` are paid placements the directory inserted into the ordering; drop them if ranking matters, and check `is_unavailable` before treating a row as a live product. Feed `alias` to /theresanaiforthat/tools for the full record.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — A task slug such as 'video-editing', or a free-text phrase. The two are different queries: the hyphenated slug asks for the task's listing document (capped at roughly 195 rows, see this endpoint's hint), a phrase asks for a relevance match. (examples: "video-editing", "chatbot", "seo"; minLength: 1)
• count integer required — Max number of tools to return (examples: 20; min: 1; max: 200)
• sort string — Result ordering. 'top_rated' also narrows the set to tools carrying a rating. (default: "relevance"; one of: "relevance", "top_rated", "most_saved", "popular", "price", "sota")
• tool_type string — Restrict to one delivery form of AI tool. 'all' applies no restriction. (default: "all"; one of: "all", "apis", "gpts", "agents", "ios", "android", "chrome", "telegram", "mini_tools")

Response

• @type string (default: "TaaftToolSummary")
• id string required
• alias string required
• name string required
• url string required
• tagline string nullable
• icon string nullable
• website_url string nullable
• website_domain string nullable
• task string nullable
• task_id string nullable
• task_alias string nullable
• country string nullable
• released string nullable
• latest_release string nullable
• modality string nullable
• pricing string nullable
• trending_rank integer nullable
• view_count integer nullable
• save_count integer nullable
• rating number nullable
• match_labels array (default: [])
• is_verified boolean nullable
• is_promoted boolean nullable
• is_gpt boolean nullable
• is_mini_tool boolean nullable
• is_unavailable boolean nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.