ipify
ipify operates two complementary IP APIs. The free Public IP Address API (api.ipify.org, api6.ipify.org, api64.ipify.org) returns the caller's public IPv4, IPv6, or dual-stack address as plain text, JSON, or JSONP — with no authentication, no rate limit, and no logging. The paid IP Geolocation API (geo.ipify.org), operated by WhoisXML API, resolves an IP, domain, or email to a country/region/city, ISP, and Autonomous System (ASN) profile using credit-metered subscription plans.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles ipify the way a machine reads it — 42 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — ipify scores 54.2/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile ipify
Each block below is one kind of artifact we hold for ipify. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 3
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
ipify Account API
Account balance and credit utilities.
ipify Geolocation API
Resolve an IP, domain, or email to a country, region, city, and ISP.
ipify IP Address API
Operations that return the caller's public IP address.
Open Collections 2
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
ipify IP Geolocation API
OPEN COLLECTIONipify Public IP Address API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Ipify Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Ipify Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Ipify Finops
FINOPSFeatures 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Public IP Lookup
Return the caller's public IPv4, IPv6, or dual-stack address with zero authentication.
Multi-Format Response
Plain text, JSON, or JSONP — pick what the client speaks natively.
Credit-Metered Geolocation
Resolve IP, domain, or email to country/region/city, ISP, and ASN.
Reverse DNS Lookup
Optionally return up to five reverse-DNS associated domains for an IP.
Account Balance Endpoint
Query remaining credits on the API key in real time.
100 req/s Rate Ceiling
Hard 100 requests/second per API key on the Geolocation API.
Open Source Server
The free public IP server is MIT/Unlicense-licensed Go (github.com/rdegges/ipify-api).
Scroll within the panel for all 7 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Ipify Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
ipify API Rules
SPECTRALipify API Rules
SPECTRALJSON Schema 3
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
JSON Structure 3
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Geolocation Api Account Balance Structure
JSON STRUCTUREGeolocation Api Geolocation Response Structure
JSON STRUCTUREIp Api Ip Response Structure
JSON STRUCTUREExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Cloud Server Provisioning
Bootstrapping cloud instances that need to know their own egress IP.
Firewall Tunneling Setup
Configuring SSH/VPN tunnels that need the client's current public IP.
Geotargeted Content
Personalize banners, currency, or language based on visitor country/city.
Fraud Detection
Flag suspicious traffic by ASN, ISP, or geographic mismatch.
Compliance Geofencing
Block or restrict access from disallowed regions or countries.
Bot and Scraping Defense
Cross-reference IP origin with AS classification (Hosting vs ISP) for traffic scoring.
Integrations 3
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
WhoisXML API
Geolocation product line is part of WhoisXML API's broader IP/DNS intelligence catalog.
Heroku
Public IP API server (rdegges/ipify-api) is deployed on Heroku.
20+ Community Client Libraries
Bash, C, Clojurescript, Crystal, Dart, Elixir, Go, Java, Kotlin, .NET, Node.js, Objective-C, PHP, Python, R, Rust, Swift, Xojo, and more.
Solutions 3
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Free Public IP Lookup
Drop-in HTTP call to api.ipify.org with no signup. Best for client-side IP discovery.
Server-Side IP Geolocation
Credit-metered Geolocation API for backend enrichment of inbound traffic.
Reverse IP Enrichment
Geolocation API with `reverseIp=1` for associating an IP with up to five domains.
Resources
Every other property we hold for ipify — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/ipify · machine-readable index on apis.io