Docs › API Reference › Inspect Endpoint

Inspect Endpoint

A public diagnostic endpoint that returns your client IP and proxy detection details. Use it to verify whether your outbound traffic is going through a proxy before you start sending requests through FourA.

Request

GET /inspect

This endpoint is public. No API key, no X-API-Key header.

curl https://eu.api.foura.ai/inspect

Response

{
  "clientIp": "203.0.113.42",
  "proxyDetection": {
    "isProxy": false,
    "proxyType": "none",
    "anonymityLevel": "none",
    "confidence": "medium",
    "detectedHeaders": [],
    "explanation": "Direct connection (no client-side proxy detected). Note: Elite proxies cannot be ruled out without additional data."
  },
  "proxyChain": {
    "originalClientIp": "203.0.113.42",
    "proxyCount": 0,
    "hasPrivateIps": false
  },
  "timestamp": "2026-04-29T08:07:04.683Z"
}

Top-Level Fields

Field Type Description
clientIp string Original client IP (leftmost address in the forwarded chain)
proxyDetection object Proxy detection and anonymity analysis
proxyChain object Client-side IP chain breakdown
timestamp string ISO 8601 timestamp of when the request was inspected

proxyDetection

Field Type Description
isProxy boolean True if client-side proxy headers were detected
proxyType string One of: transparent, anonymous, distorting, elite, none
anonymityLevel string One of: transparent, anonymous, elite, none
confidence string Detection confidence: high, medium, or low
detectedHeaders string[] Header names that signaled a proxy (e.g. via, forwarded)
explanation string Plain-English summary of the result

proxyChain

Field Type Description
originalClientIp string Same as top-level clientIp
proxyChain string[] List of proxy IPs between you and FourA, if any
proxyCount number Number of proxies detected in the chain (0 = direct)
via string[] Contents of the Via header, if present
hasPrivateIps boolean True if any private/internal IPs appear in the chain

Proxy Types

Type What it means
transparent Forwards your real IP and identifies itself as a proxy
anonymous Hides your real IP but identifies itself as a proxy
distorting Sends a fake client IP to the destination
elite No proxy headers, looks like a direct connection
none No client-side proxy detected

When to Use This

  • Confirm your outbound traffic isn't passing through a corporate or VPN proxy you didn't expect.
  • Debug why your real IP shows up in target site logs even when you thought you were anonymous.
  • Verify a residential or rotating proxy is masking your origin before you send paid requests through FourA.

This endpoint inspects your connection to FourA. It does not test FourA's own proxy network. To verify which IP a FourA-routed request comes from, use the Proxy endpoint and read the response.

Limits

  • No authentication required.
  • Subject to a generous public rate limit. If you call it more than a few times per second from the same IP, expect throttling.
  • The response reflects only headers and IPs. It cannot detect a perfectly transparent elite proxy that strips all proxy headers.
Last updated: April 29, 2026
← Rate Limits