Skip to content
IP Checker

Developer workflows

How can an AI agent check its outbound IP?

Autonomous agents, scripts and workers can check their public IP, country, ASN and network type with a single HTTP call. Examples for curl, Python and tool calling.

Software workers following separate egress routes and inspecting their public network identity

Each runtime can have a different outbound identity, even when the agents belong to the same system.

RUNTIME
worker
CHECK
egress identity
ASSERT
policy match
Test your own browser fingerprint

Why agents need this

Agents that browse, scrape or call region-restricted APIs need to know which network they are actually exiting from. It confirms that a proxy is applied, that a worker runs in the expected country, and gives support agents hard facts when a customer reports a connectivity problem.

Plain text: just the IP

The fastest check returns only the address, with nothing to parse.

bash
curl https://ipcheckhq.com/ip

Compact JSON for tool calls

format=agent returns a small object with stable keys, designed to be cheap in tokens and trivial to parse deterministically.

bash
curl "https://ipcheckhq.com/api/v1/me?format=agent"

Only the fields you need

Request an explicit list of fields to keep responses minimal.

bash
curl "https://ipcheckhq.com/api/v1/me?fields=ip,country,asn,isp,network_type"

Discovery

Agents can read https://ipcheckhq.com/llms.txt for a plain-language summary of every endpoint, or import https://ipcheckhq.com/openapi.json directly as a tool definition.