/theresanaiforthat/tasks

POST /api/theresanaiforthat/tasks

Price: 1 credit

Get There's An AI For That (theresanaiforthat.com) task (category) details by slug or task URL

How to use it

Resolves one curated task page — the directory's own category for a job people want done. Returns the task's counts, its most popular tool and its narrower child tasks, but no tool list: pass the same slug as `keyword` to /theresanaiforthat/tools/search for the tools themselves. An unknown slug is rejected rather than answered with a near match, so a 412 here means the slug is not a task — the phrase may still work as a search keyword. `subtasks` slugs are valid input back into this endpoint.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• task string required — There's An AI For That task slug ('video-editing') or full task URL ('https://theresanaiforthat.com/task/video-editing/'). (examples: "video-editing", "https://theresanaiforthat.com/task/marketing/"; minLength: 1; pattern: ^(?:https?://[^\s]+|//[^\s]+|(?:www\.)?theresanaiforthat\.com[^\s]*|/?[A-Za-z0-9][A-Za-z0-9._+%-]*/?)$)

Response

• @type string (default: "TaaftTask")
• id string required
• alias string required
• name string required
• url string required
• summary string nullable
• subscriber_count integer nullable
• tool_count integer nullable
• model_count integer nullable
• robot_count integer nullable
• device_count integer nullable
• most_popular_tool string nullable
• most_popular_tool_alias string nullable
• subtasks array (default: [])
  • @type string (default: "TaaftSubtask")
  • name string required
  • alias string required
  • url string required
  • tool_count integer 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 — Task 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.

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.