/futurepedia/tools

POST /api/futurepedia/tools

Price: 10 credits

Get Futurepedia (futurepedia.io) AI tool details by slug or tool URL

How to use it

Resolves one Futurepedia tool page. `id` is the directory's internal document identifier and is not a URL, so pass the `alias` back, not the id. `long_description` is the editorial write-up flattened to plain text: the tool's overview, feature walk-through and pricing tiers, then its frequently asked questions, use cases, how-to-use steps, limitations, plan guide, audience and workflow ideas, each under its own heading line. The directory's rating breakdown, key takeaways, video, family listing, community reviews and alternatives are not part of it; reviews come from /futurepedia/tools/reviews and alternatives from /futurepedia/tools/alternatives. `rating` is the directory's own user score, separate from the editorial verdict. `categories` slugs are valid input to /futurepedia/tools/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• tool string required — Futurepedia tool slug ('chatgpt') or full tool URL ('https://www.futurepedia.io/tool/chatgpt'). (examples: "chatgpt", "https://www.futurepedia.io/tool/midjourney"; minLength: 1; pattern: ^(?:https?://[^\s]+|//[^\s]+|(?:www\.)?futurepedia\.io[^\s]*|/?[A-Za-z0-9][A-Za-z0-9._-]*/?)$)

Response

• @type string (default: "FuturepediaTool")
• id string required
• alias string required
• name string required
• url string required
• tagline string nullable
• description string nullable
• long_description string nullable
• pros array (default: [])
• cons array (default: [])
• website_url string nullable
• image string nullable
• video_thumbnail string nullable
• youtube_url string nullable
• operating_system string nullable
• pricing_model string nullable
• starting_price string nullable
• rating number nullable
• rating_count integer nullable
• fav_count integer nullable
• is_verified boolean nullable
• categories array (default: [])
  • @type string (default: "FuturepediaToolCategory")
  • name string required
  • alias string required
  • url string required
• social_links array (default: [])
• author_name string nullable
• author_title string nullable
• updated_at 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 — 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.

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.