IP2Location.io for AI agents
Agents read IP2Location.io at once. Changes and sends are held for a person's approval by default.
About IP2Location.io
IP2Location.io provides a fast and accurate IP Geolocation API tool to determine a user's location and use the geolocation information in different use cases.
What an agent can do in IP2Location.io
Every IP2Location.io action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in IP2Location.io without asking first. 5 actions.
- Bulk IP GeolocationTool to retrieve geolocation information for multiple IP addresses in bulk. Use when processing up to 1000 IPs at once.
- Domain WHOIS LookupTool to retrieve WHOIS information for a given domain. Use when you need domain registration and contact details via IP2WHOIS API.
- Get API KeyTool to retrieve the configured API key. Use when authentication is needed for IP2Location.io requests.
- Get IP GeolocationTool to retrieve comprehensive geolocation data for an IPv4 or IPv6 address. Returns location details including country, region, city, coordinates, timezone, ISP, ASN, and proxy information.
- IP2WHOIS Hosted DomainTool to retrieve hosted domain names by IP address. Use when you need to list domains hosted on a given IP. Call after confirming the IP.
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 0 actions.
None in this connector.
Related connectors
IP2Location.io questions
Can an agent change data in IP2Location.io on its own?
Not by default. Changes and sends in IP2Location.io are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in IP2Location.io?
This connector lists 5 read actions. Reads run at once, without waiting for approval.
How does IP2Location.io connect?
It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.