FilePursuit
filepursuit.com · Debrid · 1 record · JSON
FilePursuit Debrid
fails: identityemailno cardUrequest-rate
| Free tier | The site was not readable today. The API is documented on RapidAPI as a Basic plan at $0.00/month with 3,000 requests per day and 500 requests per hour. unit requests; metered on request-count; The website itself returned HTTP 530 through the broker on four attempts; the API figures are the vendor's published plan on a marketplace we could read. |
|---|---|
| Price | USD 0 |
| Per-object cap | not applicable: a search result, not an object we store |
| Retention | unknown: the index's own retention was not readable, and the API terms say nothing about how long a link stays in the index |
| Egress | the API returns links, not bytes; bytes come from whichever host the link names free_allowance: 3,000 requests/day on the free RapidAPI plan |
| Identity | email The API needs a RapidAPI account and key, which is an email signup; the amount of identity RapidAPI demands beyond that was not established because the signup flow was not entered. |
| Limits |
The free plan also meters bandwidth at 10,240 MB/month plus $0.001 per 1 MB over. A third-party scraper reports that flooding the site triggers a captcha, which is the HTML path's limit rather than the API's. |
| Binding | request-rate 500/hour is 0.14 req/s, so enumeration stops long before any byte quota does; and the API additionally requires an account, which is recorded under identity_cost. |
| Interface | rest RapidAPI JSON endpoint with an X-RapidAPI-Key header; the site itself is HTML. The API is also offered through third-party clients (filepursuit-cli, go-filepursuit, a PyPI scraper). endpoint: rapidapi.com/azharxes/api/filepursuit |
| Tooling | The PyPI 'filepursuit' scraper and a Go client exist. Both drive the site rather than the paid API, and the scraper's own documentation says the site answers a flood of requests with a captcha. |
| Composes with | Query the index for a filename, then hand the file-host URL to a debrid service. The value is discovery: the index is what tells you which public link exists. |
| Reliability | The site answered HTTP 530 four times on 2026-10-23, which is Cloudflare reporting an origin failure. The API is a third-party marketplace listing, so its availability is a second dependency on top of the index. |
| Notes | Not recorded as dead: HTTP 530 is an origin failure, and the API is a separate endpoint that may still answer. The identity finding is independent of the outage, because the machine interface is behind a RapidAPI key whatever the website does. |
| Evidence rung | unverified The site itself produced no page: four broker attempts returned HTTP 530 (broker exit 4 on some, an origin failure on others) and no archive capture after 2025-11-25 was reachable. The API numbers came from the RapidAPI pricing page, which is the vendor's plan page and was read today, but nothing was executed against the API. A successful API call would settle both the index's liveness and the real quota. |
| Checked | 2026-10-24 (live); stale on 2026-11-07 |
| Parsed numbers |
|
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | rapidapi.com/azharxes/api/filepursuit/pricing | Basic $0.00/mo, 'Requests 3,000 / Day Hard Limit', 'Rate Limit 500 requests per hour', 10240 MB/month bandwidth |
| 2026-10-23 | filepursuit.com/ | four broker attempts returned HTTP 530; nothing was established about the live site |
| 2026-10-23 | pypi.org/project/filepursuit/ | a third-party scraper's README says FilePursuit answers flooding with a captcha |
More fields (4)
{
"http_status_observed": 530,
"attempts": 4,
"api_marketplace": "RapidAPI",
"anonymous_api": false
}