Turn an IP address in your logs into location, network, and proxy context
An address shows up in an alert or an access log and you need to know what it is. Ip2Location answers from the terminal: country, city, coordinates, and ISP via IP2LOCATION_GET_IP_GEOLOCATION, proxy, VPN, or TOR status via IP2LOCATION_GET_PROXY_DETECTION, and whole lists at once with IP2LOCATION_BULK_IP_GEOLOCATION. Domain WHOIS and hosted-domain lookups sit alongside. Connect with an API key. Everything here is read-only, so answers come back immediately.
8 tools, all read-only. They answer instantly, and every call is logged.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
No. Every one of the 8 tools LuumenAI has for Ip2Location is read-only, so it can answer questions from Ip2Location but cannot change anything in it. Reads are not gated — they answer immediately, and each one is recorded on the audit trail with the actor and the result.
You decide. Access is granted per agent, skill, and team, and per environment — production is not staging.
Every call to Ip2Location is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.