/futurepedia/tools/search

POST /api/futurepedia/tools/search

Price: 1 credit

Search Futurepedia (futurepedia.io) AI tools inside one category, with pricing and sort filters

How to use it

Browses one Futurepedia category. There is no free-text tool search on this source, so start from a slug out of /futurepedia/categories rather than a phrase; an unknown slug is a 412, not an empty list. Repeating `pricing` is an OR — asking for Free and Paid returns both, never only tools that are somehow both. Retired entries stay in the catalogue, so check `is_defunct` and `is_duplicate` before treating a row as a live product. Rows carry summary fields only; the written review, the pros and cons and the long description come from /futurepedia/tools on the same `alias`.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• category string required — Futurepedia category slug ('marketing') or full category URL ('https://www.futurepedia.io/ai-tools/marketing'). List the valid slugs with /futurepedia/categories. (examples: "marketing", "chatbots", "https://www.futurepedia.io/ai-tools/video-generators"; minLength: 1; pattern: ^(?:https?://[^\s]+|//[^\s]+|(?:www\.)?futurepedia\.io[^\s]*|/?[A-Za-z0-9][A-Za-z0-9._-]*/?)$)
• count integer required — Max number of tools to return (examples: 24; min: 1; max: 600)
• sort string — Result ordering (default: "trending"; one of: "trending", "new", "popular")
• pricing array — Keep only tools carrying at least one of these pricing models. Several values widen the result set rather than narrowing it. Empty means no restriction. (default: []; one of: "Free", "Freemium", "Free Trial", "Paid", "Contact for Pricing", "Deals"; examples: ["Free","Freemium"])
• verified_only boolean — Keep only tools the directory marks as verified (default: false)

Response

• @type string (default: "FuturepediaToolSummary")
• id string required
• alias string required
• name string required
• url string required
• short_description string nullable
• website_url string nullable
• is_affiliate boolean nullable
• image string nullable
• thumbnail string nullable
• favicon string nullable
• youtube_url string nullable
• pricing array (default: [])
• starting_price string nullable
• rating number nullable
• review_count integer nullable
• review_score number nullable
• rating_breakdown object nullable
  • @type string (default: "FuturepediaRatingBreakdown")
  • accuracy number nullable
  • ease_of_use number nullable
  • features number nullable
  • speed number nullable
  • support number nullable
  • value number nullable
• fav_count integer nullable
• popularity_score integer nullable
• top_rank_score integer nullable
• vote_count integer nullable
• is_verified boolean nullable
• verified_reason string nullable
• label string nullable
• tool_type array (default: [])
• status string nullable
• is_defunct boolean nullable
• defunct_reason string nullable
• is_duplicate boolean nullable
• capabilities array (default: [])
• categories array (default: [])
  • @type string (default: "FuturepediaToolCategory")
  • name string required
  • alias string required
  • url string required
• social_links array (default: [])
• created_at string nullable
• updated_at string nullable
• published_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 — Category 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.