IPGeolocation.io
IPGeolocation.io is a multi-product IP intelligence platform offering IP geolocation, IP security/threat intelligence, ASN lookup, abuse contact, timezone, astronomy (sunrise, sunset, moon phase, celestial position), and user-agent parsing APIs. All endpoints are served under https://api.ipgeolocation.io with API-key authentication. The free plan offers 1,000 credits/day; paid plans (Starter through Premium) scale from 150K to 5M requests/month, with custom Enterprise pricing on top.
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 IPGeolocation.io the way a machine reads it — 169 machine-readable artifacts across 7 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 — IPGeolocation.io scores 58.3/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 IPGeolocation.io
Each block below is one kind of artifact we hold for IPGeolocation.io. 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 7
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.
IPGeolocation.io ASN Lookup API
API endpoint for retrieving Autonomous System Number (ASN) information associated with IPv4 addresses, IPv6 addresses, or specific ASN numbers. The response includes ASN metadat...
IPGeolocation.io Astronomy API
API endpoints for retrieving astronomical information for a given location, including sunrise and sunset times, moonrise and moonset times, twilight phases, golden hour and blue...
IPGeolocation.io IP Abuse Contact API
API endpoint for retrieving abuse contact information associated with IPv4 and IPv6 addresses. The response contains registry-based contact details for reporting malicious or ab...
IPGeolocation.io IP Geolocation API
IP geolocation API endpoints for looking up geographic location, network routing, ASN ownership, company attribution, timezone, currency, security threat intelligence, abuse con...
IPGeolocation.io IP Security API
IP security intelligence endpoints used to detect VPNs, proxies, Tor exit nodes, relay networks, bot activity, spam activity, cloud providers, and other anonymization technologi...
IPGeolocation.io Timezone API
API endpoints for retrieving current date, time, and timezone information for a given input such as an IANA timezone identifier, geographic coordinates, location address, IPv4 o...
IPGeolocation.io User Agent API
API endpoints for parsing user agent strings into browser, device, layout engine, and operating system details. Supports single lookups via request header, custom string lookups...
Scroll within the panel for all 7 ·
Open Collections 7
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).
IPGeolocation.io: Abuse Contact API
OPEN COLLECTIONIPGeolocation.io: ASN Lookup API
OPEN COLLECTIONIPGeolocation.io: Astronomy API
OPEN COLLECTIONIPGeolocation.io: IPGeolocation API
OPEN COLLECTIONIPGeolocation.io: IP Security API
OPEN COLLECTIONIPGeolocation.io: Date, Time & Timezone API
OPEN COLLECTIONIPGeolocation.io: User Agent API
OPEN COLLECTIONScroll within the panel for all 7 ·
Pricing 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.
Rate 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.
Ipgeolocation 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.
Ipgeolocation Finops
FINOPSSemantic Vocabularies 8
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.
Scroll within the panel for all 8 ·
Spectral 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.
IPGeolocation.io API Rules
SPECTRALIPGeolocation.io API Rules
SPECTRALJSON Schema 47
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.
AbuseLookupResponse
JSON SCHEMAAbuse
JSON SCHEMAASN
JSON SCHEMAASNConnection
JSON SCHEMAASNLookupResponse
JSON SCHEMAAstronomyData
JSON SCHEMAAstronomyLookupResponse
JSON SCHEMAAstronomyTimeSeriesEntry
JSON SCHEMAAstronomyTimeSeriesResponse
JSON SCHEMALocation
JSON SCHEMATwilightPhase
JSON SCHEMAAbuse
JSON SCHEMAAsn
JSON SCHEMABulkGeolocationErrorItem
JSON SCHEMABulkGeolocationRequest
JSON SCHEMABulkGeolocationResponseItem
JSON SCHEMABulkGeolocationSuccessItem
JSON SCHEMACompany
JSON SCHEMACountryMetadata
JSON SCHEMACurrency
JSON SCHEMADstTransition
JSON SCHEMAIpGeolocationResponse
JSON SCHEMALocation
JSON SCHEMANetwork
JSON SCHEMASecurity
JSON SCHEMATimeZone
JSON SCHEMAUserAgentDevice
JSON SCHEMAUserAgentEngine
JSON SCHEMAUserAgentOperatingSystem
JSON SCHEMAUserAgent
JSON SCHEMABulkSecurityErrorItem
JSON SCHEMABulkSecurityRequest
JSON SCHEMABulkSecurityResponseItem
JSON SCHEMABulkSecuritySuccessItem
JSON SCHEMAIpSecurityResponse
JSON SCHEMASecurity
JSON SCHEMAAirportDetails
JSON SCHEMADSTTransition
JSON SCHEMALocation
JSON SCHEMALocodeDetails
JSON SCHEMATimeConversionResponse
JSON SCHEMATimezoneLookupResponse
JSON SCHEMATimezone
JSON SCHEMADevice
JSON SCHEMAEngine
JSON SCHEMAOperatingSystem
JSON SCHEMAUserAgentResponse
JSON SCHEMAScroll within the panel for all 47 ·
JSON Structure 47
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.
Abuse Abuse Lookup Response Structure
JSON STRUCTUREAbuse Abuse Structure
JSON STRUCTUREAsn Asn Structure
JSON STRUCTUREAsn Asnconnection Structure
JSON STRUCTUREAsn Asnlookup Response Structure
JSON STRUCTUREAstronomy Astronomy Data Structure
JSON STRUCTUREAstronomy Astronomy Lookup Response Structure
JSON STRUCTUREAstronomy Astronomy Time Series Entry Structure
JSON STRUCTUREAstronomy Astronomy Time Series Response Structure
JSON STRUCTUREAstronomy Location Structure
JSON STRUCTUREAstronomy Twilight Phase Structure
JSON STRUCTUREIp Location Abuse Structure
JSON STRUCTUREIp Location Asn Structure
JSON STRUCTUREIp Location Bulk Geolocation Error Item Structure
JSON STRUCTUREIp Location Bulk Geolocation Request Structure
JSON STRUCTUREIp Location Bulk Geolocation Response Item Structure
JSON STRUCTUREIp Location Bulk Geolocation Success Item Structure
JSON STRUCTUREIp Location Company Structure
JSON STRUCTUREIp Location Country Metadata Structure
JSON STRUCTUREIp Location Currency Structure
JSON STRUCTUREIp Location Dst Transition Structure
JSON STRUCTUREIp Location Ip Geolocation Response Structure
JSON STRUCTUREIp Location Location Structure
JSON STRUCTUREIp Location Network Structure
JSON STRUCTUREIp Location Security Structure
JSON STRUCTUREIp Location Time Zone Structure
JSON STRUCTUREIp Location User Agent Device Structure
JSON STRUCTUREIp Location User Agent Engine Structure
JSON STRUCTUREIp Location User Agent Operating System Structure
JSON STRUCTUREIp Location User Agent Structure
JSON STRUCTURESecurity Bulk Security Error Item Structure
JSON STRUCTURESecurity Bulk Security Request Structure
JSON STRUCTURESecurity Bulk Security Response Item Structure
JSON STRUCTURESecurity Bulk Security Success Item Structure
JSON STRUCTURESecurity Ip Security Response Structure
JSON STRUCTURESecurity Security Structure
JSON STRUCTURETimezone Airport Details Structure
JSON STRUCTURETimezone Dsttransition Structure
JSON STRUCTURETimezone Location Structure
JSON STRUCTURETimezone Locode Details Structure
JSON STRUCTURETimezone Time Conversion Response Structure
JSON STRUCTURETimezone Timezone Lookup Response Structure
JSON STRUCTURETimezone Timezone Structure
JSON STRUCTUREUser Agent Device Structure
JSON STRUCTUREUser Agent Engine Structure
JSON STRUCTUREUser Agent Operating System Structure
JSON STRUCTUREUser Agent User Agent Response Structure
JSON STRUCTUREScroll within the panel for all 47 ·
Examples 45
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.
Abuse Abuse Example
EXAMPLEAsn Asn Example
EXAMPLEAsn Asnconnection Example
EXAMPLEAstronomy Location Example
EXAMPLEIp Location Abuse Example
EXAMPLEIp Location Asn Example
EXAMPLEIp Location Company Example
EXAMPLEIp Location Currency Example
EXAMPLEIp Location Location Example
EXAMPLEIp Location Network Example
EXAMPLEIp Location Security Example
EXAMPLESecurity Security Example
EXAMPLETimezone Location Example
EXAMPLETimezone Timezone Example
EXAMPLEUser Agent Device Example
EXAMPLEUser Agent Engine Example
EXAMPLEScroll within the panel for all 45 ·
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.
Resources
Every other property we hold for IPGeolocation.io — 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.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 10
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 10 ·
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/ipgeolocation · machine-readable index on apis.io