In short
Use DetectProxy to protect your own product. Don't copy the dataset, resell access, share keys, dodge limits, or use it to harm people. If your use case is unusual, ask us first.
1. Why this policy exists
This policy keeps the Service accurate, fast and fair for every customer. It applies together with our Terms of Service to everyone who uses the API or website, alongside RapidAPI’s Terms of Service, which govern the marketplace account and billing relationship you have with RapidAPI.
2. What you can do
- Check IP addresses at signup, checkout and login to catch fake accounts, trial abuse and card testing.
- Filter ad and click fraud, and flag suspicious traffic in your analytics.
- Support security investigations and monitoring for your own systems.
- Cache individual responses for up to 24 hours to avoid repeat lookups.
3. What you can't do
Reconstruct the dataset
Do not query the API in systematic patterns intended to rebuild or approximate our data. That includes sequential or random sweeps of address space, probing the edges of ranges, and harvesting responses into a persistent database. Spreading such queries across several keys, accounts or source addresses is treated the same way.
Resell or redistribute access
Do not resell, sublicense or republish the API or its raw responses as a lookup service, data feed, list or proxy API, and do not wrap the API so that third parties can query it through you.
Share keys or evade limits
Keep your API key private and use it for your own product only. Do not create multiple accounts, rotate keys, or split traffic to get around quotas or rate limits.
Bypass access controls
Use the Service only through RapidAPI. Do not call our infrastructure directly, forge or replay RapidAPI's headers, or probe our systems for weaknesses.
Disrupt the Service
Do not send traffic designed to degrade the Service, exceed your limits on purpose, or overload it with malformed requests.
Cause harm or break the law
Do not use the Service to stalk, harass, dox or unlawfully discriminate against anyone, to identify or track individuals, to distribute malware, or for any activity that is illegal where you or your users are located.
4. Monitoring and enforcement
We monitor usage patterns, such as request volume, distribution and sequencing, to detect violations of this policy. If we find one, we may, at our discretion and depending on severity:
- throttle or block requests;
- suspend or revoke API keys;
- terminate access without a refund; and
- report the activity to the marketplace or to the authorities where required.
We may act without advance notice where that is needed to protect the Service or other customers.
5. Unusual or high-volume use
If your use case might come close to these rules — for example you need very high volumes for your own infrastructure — contact us before you build. We can often suggest a plan that fits: Show email.
6. Reporting abuse
If you believe someone is misusing the Service, or that a verdict about your network is wrong, Show email and include the details.
7. Changes
We may update this policy from time to time. The date at the top of this page shows when it was last changed.