IPRegistry for AI agents
Agents read IPRegistry at once. Changes and sends are held for a person's approval by default.
About IPRegistry
IPRegistry provides IP geolocation, network, company, carrier, threat, autonomous-system, and user-agent intelligence.
What an agent can do in IPRegistry
Every IPRegistry 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 IPRegistry without asking first. 5 actions.
- Batch Look Up ASNsReturn ordered Autonomous System lookup results for 1 to 16 ASNs; an invalid item is returned as an inline error without failing successful items.
- Batch Look Up IP AddressesReturn ordered lookup results for 1 to 1024 public IP addresses; an invalid item is returned as an inline error without failing successful items.
- Look Up ASNReturn organization, country, registry, network-prefix, and relationship data for one public Autonomous System Number.
- Look Up IP AddressReturn geolocation, network, company, carrier, time-zone, currency, and threat data for one public IPv4 or IPv6 address.
- Parse User AgentsParse 1 to 256 raw User-Agent strings into browser or application, device, rendering-engine, and operating-system details in input order.
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.
IPRegistry questions
Can an agent change data in IPRegistry on its own?
Not by default. Changes and sends in IPRegistry 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 IPRegistry?
This connector lists 5 read actions. Reads run at once, without waiting for approval.
How does IPRegistry connect?
It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.