Tor Node Detector API GET

Tor Detect is an API that checks whether a given IP address belongs to a known Tor exit node. Useful for security, access control, and analytics.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/tordetect

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Tor Node Detector response payload
  }
}

About the Tor Node Detector API

Tor Detect uses up-to-date exit node lists from the Tor network to verify if the specified IP address is actively being used as a Tor exit node. This is essential for services that wish to restrict access from anonymous sources or monitor traffic.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use Tor Node Detector

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the Tor Node Detector API.

Read the docs →

What does the Tor Node Detector API do?

Tor Detect is an API that checks whether a given IP address belongs to a known Tor exit node. Useful for security, access control, and analytics.

How do I authenticate Tor Node Detector API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the Tor Node Detector API cost?

Each call spends 10 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the Tor Node Detector API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the Tor Node Detector API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the Tor Node Detector API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — GET /v1/tordetect

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`ip`Required	string	`185.189.183.143`	The IP address to check against the Tor exit node list ip

Example request

1
2

curl "https://api.apiverve.com/v1/tordetect?ip=185.189.183.143" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — GET /v1/tordetect

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "ipAddress": "185.189.183.143",
    "isTor": true,
    "ipDetails": {
      "range": [
        3116217344,
        3116218367
      ],
      "country": "NL",
      "region": "ZH",
      "timezone": "Europe/Amsterdam"
    },
    "parsed": true
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`ipAddress`	string	`"185.189.183.143"`	The IP address being checked for Tor exit node status
`isTor`	boolean	`true`	Whether the IP is a known Tor exit node
`ipDetails`Premium	object	`{...}`	Detailed information about the IP geolocation and network
`range`Premium	array	`[3116217344, ...]`	IP address range in numeric format for this location
`country`Premium	string	`"NL"`	Two-letter ISO country code of IP location
`region`Premium	string	`"ZH"`	Region or state code of IP location within country
`timezone`Premium	string	`"Europe/Amsterdam"`	IANA timezone identifier for IP location
`parsed`	boolean	`true`	Whether the IP address was successfully parsed and validated

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 10 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	Tor Node Detector calls	Per 1,000 calls
Free	Free	200	20	Free
Starter	$29.99	200,000	20,000	$1.50
Pro	$99.99	1,000,000	100,000	$1.00
Mega	$299.99	4,000,000	400,000	$0.75

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/tordetect

No SDK to install — this is a plain HTTPS call to /v1/tordetect with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/tordetect" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/tordetect-apiSource, issues and the examples this page is built from.ReferenceTor Node Detector API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/tordetectnpm APIVerve.API.TorNodeDetectorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/tordetect

Install the Node.js SDK, then call the Tor Node Detector API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/tordetect

Node.js

const res = await fetch("https://api.apiverve.com/v1/tordetect", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/tordetectThe published Node.js client, versioned and signed.GitHubapiverve/tordetect-apiSource, issues and the examples this page is built from.ReferenceTor Node Detector API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.TorNodeDetectorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/tordetect

No SDK to install — this is a plain HTTPS call to /v1/tordetect with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/tordetect",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/tordetectnpm APIVerve.API.TorNodeDetectorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/tordetect

Install the C# / .NET SDK, then call the Tor Node Detector API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.TorNodeDetector

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/tordetect");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.TorNodeDetectorThe published C# / .NET client, versioned and signed.GitHubapiverve/tordetect-apiSource, issues and the examples this page is built from.ReferenceTor Node Detector API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/tordetectnpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/tordetect

No SDK to install — this is a plain HTTPS call to /v1/tordetect with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/tordetect", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/tordetectnpm APIVerve.API.TorNodeDetectorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/tordetect

No SDK to install — this is a plain HTTPS call to /v1/tordetect with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/tordetect");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/tordetectnpm APIVerve.API.TorNodeDetectorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/tordetect

No SDK to install — this is a plain HTTPS call to /v1/tordetect with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/tordetect")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/tordetectnpm APIVerve.API.TorNodeDetectorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

How to Detect VPN and Proxy UsersIdentify VPN, proxy, and datacenter IPs to prevent fraud and enforce geo-restrictions. Complete tutorial with code examples.Read

IP Fraud Detection: VPNs, Tor, and BlacklistsBuild an IP-based fraud scoring system. Detect VPNs, Tor exit nodes, and blacklisted IPs before they cost you money.Read

7 SSL Certificate Problems That Kill TrustExpired certs, mismatched domains, weak encryption. A practical checklist for catching SSL issues before your users do.Read

Tor Node Detector API GET

Try it — live request, no key required

About the Tor Node Detector API

Ways to call it

Other ways to use Tor Node Detector

Questions.

Request parameters — GET /v1/tordetect

Required

Authentication

Response — GET /v1/tordetect

Response fields

Response headers

Errors

What a call costs — 10 credits per call

Call it from cURL — GET /v1/tordetect

Resources

Also published for

Call it from Node.js — GET /v1/tordetect

Resources

Also published for

Call it from Python — GET /v1/tordetect

Resources

Also published for

Call it from C# / .NET — GET /v1/tordetect

Resources

Also published for

Call it from Go — GET /v1/tordetect

Resources

Also published for

Call it from PHP — GET /v1/tordetect

Resources

Also published for

Call it from Ruby — GET /v1/tordetect

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Tor Node Detector API

Networking

Related articles

Ready to build with Tor Node Detector? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog