FilePursuit
- Free allowance
- The site was not readable today.
- Verdict
- deadthe offer or the service no longer exists
- Cost
- no price statedsee Price below
- Identity
- emailno card, no phone
- Binding limit
- request-rate500 requests per hour on the free RapidAPI plan, with a hard cap of 3,000 requests per day
- Evidence
- unverified9 sources; asserted and not checked
- Freshness
- checked 2026-11-04checked 2026-11-04 (live)
| 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 on four attempts; the API figures are the vendor's published plan on a marketplace. |
|---|---|
| Price | USD 0 |
| 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. |
| 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. |
| 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 |
| 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 |
| 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 | On 2026-11-03 the .com registry lists filepursuit.com with status client hold and the domain has no DNS answer (NXDOMAIN); the site answered an origin failure on 2026-10-23. Whether a datacenter address is accepted: not published. |
| Notes | The index domain no longer resolves, so the service is recorded dead. The RapidAPI listing remains, showing a 0% service level, and its machine interface needs a RapidAPI key. |
| Evidence note | unverified The domain's DNS answer (NXDOMAIN) and registry status (client hold) were read on 2026-11-03 and the RapidAPI listing shows a 0% service level; the API plan figures come from the RapidAPI pricing page and nothing was executed against the API. |
| Parsed numbers |
|
Evidence 9
| 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/ | 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 |
| 2026-11-03 | probe: https://dns.google/resolve?name=filepursuit.com&type=A | the public resolver answers NXDOMAIN (status 3) for filepursuit.com |
| 2026-11-03 | probe: https://rdap.verisign.com/com/v1/domain/filepursuit.com | the registry shows the domain on client hold, which removes it from DNS |
| 2026-11-03 | rapidapi.com/azharxes/api/filepursuit | the marketplace listing for the API shows 0% service level |
| 2026-11-04 | rapidapi.com/azharxes/api/filepursuit/pricing | the free plan rate limit is 500 requests per hour |
| 2026-11-04 | probe: filepursuit.com | the site does not resolve in DNS |
| 2026-11-04 | probe: https://dns.google/resolve?name=filepursuit.com&type=A | the public resolver answers NXDOMAIN for filepursuit.com |
More fields 5
| http status observed | 530 |
|---|---|
| attempts | 4 |
| api marketplace | RapidAPI |
| anonymous api | no |
| death | {"on": "2026-11-03","cause": "dead-service"} |