/ip-intelligence/ — proxycheck.io
Compare daily address allowances for proxy, VPN, Tor and hosting classification. The v3 reference separates risk from detection confidence and recency; free access includes the core detection features, with lower usage and customization limits.
IP intelligence. Official documentation · Checked · Review due .
Choose a product and access method
documented decisionSwipe or scroll the table to compare response checks and billing.
| Starting point | Access method | Check before use | Billing basis |
|---|---|---|---|
| You need small-volume detection with network context | Use a registered free API key. | Core detection features are included, but free customization limits apply and allowance is daily. | A free key provides 1,000 queries/day; keyless access provides 100.[1][3] |
| You want to check a batch of addresses | Use the v3 multiple-address request format. | Keep batches at or below 100 addresses without a key or 1,000 with a registered key, and check the remaining daily quota. Use limits for the selected API version. | Each checked address consumes one query from the daily allowance.[1] |
| You need to decide how long a detection remains relevant | Choose the documented days window and inspect confidence and last-seen data. | Extending the window retains older detections; confidence and risk answer different questions. Confirm the selected API version's fields. | These core fields are available across detection plans; request allowance still applies.[1][2][3] |
documented capabilities
HTTP API- Delivery
- HTTP JSON API. The v3 reference documents nested network, location and detection objects; some prose still calls v2 the latest version, so keep the API version explicit.[1][2]
- Location data
- The v3 OpenAPI schema lists country, region, city, coordinates and timezone. Missing values can be null.[2]
- ASN and network
- The v3 reference lists ASN, network range, hostname, provider, organization and allocation type.[1][2]
- Privacy signals
- The v3 schema lists proxy, VPN, Tor and hosting booleans, plus risk, confidence and detection timestamps. Pricing includes core detection features on Free; customization limits vary by plan.[2][1][3]
- Access and free use
- Keyless access allows 100 queries/day; a registered free key allows 1,000/day. Origin-bound public browser keys check only the requesting visitor's IP. One free account is allowed per customer.[1][4]
- Billing unit
- Each checked address consumes daily quota. The v3 service table allows up to 100 addresses per keyless request or 1,000 with a registered key. The daily allowance is separate from this batch limit.[1][3]
- IP versions
- The API documentation accepts IPv4 and IPv6 inputs, including multiple-address requests.[1]
- Risk and confidence
- Risk includes a baseline related to detected usage type and attack history. Confidence emphasizes recency of positive detections; it is a separate field.[1][2]
- Data reuse
- Terms permit selected data to enrich a service but prohibit republishing entire results, resale or a service whose main value is access to the data.[4]
Billing: Subscriptions buy daily query allowances even when billed monthly or yearly. Every checked address consumes quota, including addresses sent in bulk. Registered free access permits 1,000 queries per day.
Outputs: json
Documented for: Proxycheck.io API
getting started
documentation reviewed- Choose a private server-side API key or an origin-bound public key for browser requests.
- Select the API version explicitly in the dashboard or documented version parameter. Compare its reference with the v3 schema before implementing.
- Use HTTPS and parse the chosen version's documented JSON types, preserving null values and checking status and HTTP errors.
- Set a daily address budget and detection-age window; account for each IP in a batch and the plan's burst-token behavior.
Requirements & limitations
- The documentation contains both v2 and v3 sections, with some stale v2 wording in the v3 material. This listing follows the v3 service-limit table; older batch limits do not apply. No live response or runtime compatibility was tested.
- Longer detection windows can retain old classifications. Confidence, risk and timestamps should not be collapsed into a single claim of present misuse.
- Missing location, network or operator data can be null.
- Pricing changed on 1 October 2026. Check the current purchase quote; complete-response republication and resale are restricted by the terms.
We reviewed the linked documentation. No live service connection, checkout or performance test is claimed for this listing.
primary sources
4 references- proxycheck.io API DocumentationChecked 2026-10-01
- proxycheck.io OpenAPI specificationChecked 2026-10-01
- proxycheck.io PricingChecked 2026-10-01
- proxycheck.io TermsChecked 2026-10-01