IP Threat Intelligence AI Agent / LLM

# IP Threat Intelligence API — Way2API®

- **Endpoint:** `POST https://app.way2api.com/api/v1/ip/threat`
- **Auth:** `Authorization: Bearer YOUR_API_KEY` (or `X-API-Key: YOUR_API_KEY`)
- **Content-Type:** `application/json`
- **Category:** IP and Network Intelligence
- **Availability:** Available worldwide
- **Docs:** https://app.way2api.com/documentation/ip-threat

## What it does

IP Threat Intelligence API — real-time risk signals for an IPv4 or IPv6 address. Returns a threat_score from 0 to 100 (higher is riskier) alongside the individual flags behind it: is_tor, is_proxy, is_residential_proxy, is_vpn, is_relay, is_anonymous, is_known_attacker, is_bot, is_spam and is_cloud_provider — plus detected provider names and confidence scores for the proxy and VPN verdicts. ip_address is optional: omit it and the IP that called this API is looked up. Built for login-risk checks, signup fraud screening and payment review. Use the bulk endpoint to screen many addresses in one call.

## Request body (application/json)

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `ip_address` | string | no | IPv4 or IPv6 address to screen, e.g. 8.8.8.8. Optional — if omitted, the IP that called this API is used. |

## Example request

```bash
curl -X POST https://app.way2api.com/api/v1/ip/threat \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"ip_address":"8.8.8.8"}'
```

## Success response — 200

```json
{
    "status": "SUCCESS",
    "status_code": 200,
    "charged": true,
    "success": true,
    "message": "",
    "message_code": "OK",
    "order_id": "W2A1739512345abcdef01",
    "data": {
        "order_id": "W2A1739512345abcdef01",
        "result": {
            "ip_address": "8.8.8.8",
            "security": {
                "threat_score": 5,
                "is_anonymous": false,
                "is_tor": false,
                "is_proxy": false,
                "is_residential_proxy": false,
                "proxy_providers": [],
                "proxy_confidence": 0,
                "proxy_last_seen": "",
                "is_vpn": false,
                "vpn_providers": [],
                "vpn_confidence": 0,
                "vpn_last_seen": "",
                "is_relay": false,
                "relay_provider": "",
                "is_known_attacker": false,
                "is_bot": false,
                "is_spam": false,
                "is_cloud_provider": true,
                "cloud_provider": "Google LLC"
            }
        }
    }
}
```

## Error response — 400

```json
{
    "status": "FAILED",
    "status_code": 400,
    "charged": false,
    "success": false,
    "message": "'127.0.0.1' is a reserved (bogon) IP address.",
    "message_code": "REQUEST_FAILED",
    "order_id": "W2A1739512345abcdef01",
    "data": {
        "order_id": "W2A1739512345abcdef01",
        "error_code": "Locked"
    }
}
```

## Integration rules

- Every response is JSON carrying `status`, `status_code`, `charged`, `success`, `message`, `message_code` and (once a call reaches the provider) `order_id`. The verification payload is under `data.result`.
- `charged` (boolean) is the authority on billing. Do NOT infer it from the HTTP status: `422` is returned both for input we rejected (not charged) and for a lookup the provider ran and billed us for that returned a negative result (charged).
- `message_code` is a fixed vocabulary — branch on it instead of parsing `message`. Values: `OK`, `ACCEPTED`, `PROVIDER_NO_RESPONSE`, `VERIFICATION_FAILED`, `NO_RECORD_FOUND`, `INVALID_INPUT`, `REQUEST_FAILED`, `MISSING_API_KEY`, `INVALID_API_KEY`, `INSUFFICIENT_BALANCE`, `NO_API_ACCESS`, `NOT_FOUND`, `RATE_LIMITED`, `INTERNAL_ERROR`, `PROVIDER_UNAVAILABLE`.
- `success` reports the verification outcome; `status` reports the ORDER lifecycle (`SUCCESS`/`PENDING`/`FAILED`). They differ on a charged negative result: the order completed and was billed while the verification did not pass.
- A failed verification is still a successful HTTP call — the outcome lives in the response body, so do not treat `200` as "verified".
- Status codes: `200` result returned, `202` pending or provider did not respond (both charged — quote the `order_id`), `401` missing/invalid key, `402` insufficient balance, `403` no access to this service, `422` see `charged`, `429` rate limited (honour the `Retry-After` header), `503` temporarily unavailable.
- Rate limits are per API key, per service, on a 1-minute sliding window.
- Load the API key from an environment variable or secret store. Never hard-code it, never commit it, and never ship it in client-side code — calls must be made from your backend.