/futurepedia/categories

POST /api/futurepedia/categories

Price: 1 credit

List Futurepedia (futurepedia.io) AI tool categories and their slugs

How to use it

The slug vocabulary /futurepedia/tools/search expects, delivered in one call. Futurepedia files a tool under two independent taxonomies at once — by what the tool makes and by the business function it serves — so the same slug can appear under both `group` values with a different `parent_alias`, and that is not a duplicate. `parent_alias` is itself a slug the search endpoint accepts, which is how you widen a query from one narrow category to its whole family.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of categories to return (examples: 100; min: 1; max: 300)
• group string — Which taxonomy to list: 'parent_category' groups tools by what they make, 'business_function' by the department that uses them, 'all' returns both. (default: "all"; one of: "all", "parent_category", "business_function")

Response

• @type string (default: "FuturepediaCategory")
• id string required
• alias string required
• name string required
• url string required
• group string required
• parent_alias string required
• page_title string nullable
• tagline string nullable
• description string nullable
• image string nullable
• category_code string 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.