Anthropic and ip-api.com

Anthropic

Actions

• Generate a Claude responseSend a prompt to Claude and get back its written response.

ip-api.com

Actions

• Look up an IP addressGeolocate an IP address or a domain name: the country, region and city it is in, its coordinates and time zone, the provider that runs it, and whether it is a proxy, a data centre or a mobile network.
• Look up this workflow's IP addressLook up the address your workflow's requests go out from, and where it is, which is what you need when a third-party API asks you to allow-list the address your calls arrive from.
• Look up several IP addressesGeolocate a list of addresses in one step and get a row for each with where it is and who runs it. Addresses that cannot be located are reported alongside the ones that can.
• Check whether an IP address can be locatedAnswer whether an address can be located at all, and say why not when it cannot: a typo, a private address from inside a local network, or a reserved one such as a loopback. It answers no rather than failing.
• Check an IP address's countryAnswer whether an address is in one of the countries you name, the check behind sending someone to the right regional site, gating a feature by market, or flagging a sign-up from outside the countries you sell in.
• Check an IP address for proxy, VPN or hostingReport what kind of connection an address is on: a proxy, VPN or Tor exit node, a data centre, or a mobile network. The first two are flagged together, which is the usual signal that a form submission is not coming from where it claims to be.