POST /api/theresanaiforthat/tools/alternatives
Price: 1 credit
Get There's An AI For That (theresanaiforthat.com) alternatives to one AI tool
Tools the directory offers instead of the one you name. The head of the list is the directory's own editorial 'Top alternatives' selection; past that it continues with tools from the same task's listing document, in the directory's own order, so relatedness weakens down the list. That listing document renders at most roughly 195 rows, which for a popular task is only a slice of everything the directory files under it — this is not the task's whole catalogue. The tool itself is never returned. A tool the directory files under no task returns only the editorial block, which is why a small result set is normal rather than a sign of failure.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)tool string required — There's An AI For That tool slug ('gling') or full tool URL ('https://theresanaiforthat.com/ai/gling/'). (examples: "gling", "https://theresanaiforthat.com/ai/supernormal/"; minLength: 1; pattern: ^(?:https?://[^\s]+|//[^\s]+|(?:www\.)?theresanaiforthat\.com[^\s]*|/?[A-Za-z0-9][A-Za-z0-9._+%-]*/?)$)count integer required — Max number of alternative tools to return (examples: 20; min: 1; max: 200)@type string (default: "TaaftToolSummary")id string requiredalias string requiredname string requiredurl string requiredtagline string nullableicon string nullablewebsite_url string nullablewebsite_domain string nullabletask string nullabletask_id string nullabletask_alias string nullablecountry string nullablereleased string nullablelatest_release string nullablemodality string nullablepricing string nullabletrending_rank integer nullableview_count integer nullablesave_count integer nullablerating number nullablematch_labels array (default: [])is_verified boolean nullableis_promoted boolean nullableis_gpt boolean nullableis_mini_tool boolean nullableis_unavailable boolean nullable422 — 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 — Tool not found 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.