positionstack
Forward and Reverse Batch Geocoding REST API by positionstack (an apilayer product, owned by Idera, Inc.). Convert addresses to coordinates and coordinates to addresses across 2+ billion global places, with optional data modules for country, timezone, sun, and bounding-box enrichment.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles positionstack the way a machine reads it — 54 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 — positionstack scores 66.9/100 (strong), 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 positionstack
Each block below is one kind of artifact we hold for positionstack. 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.
positionstack Batch Geocoding API
Run multiple forward or reverse geocoding lookups in a single request (Professional plan and above).
positionstack Forward Geocoding API
Convert addresses, place names, or partial location strings into geographic coordinates.
positionstack Reverse Geocoding API
Convert latitude/longitude coordinates into a full address with locality, region, and country.
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
positionstack
POSTMANOpen Collections 1
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).
positionstack
OPEN COLLECTIONArazzo Workflows 3
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
positionstack Geocode with Confidence Branch
Forward geocode an address and branch on the match confidence to either enrich or re-verify the result.
ARAZZOpositionstack Geocode Roundtrip
Forward geocode an address, then reverse geocode the resulting coordinates to verify the match.
ARAZZOpositionstack Reverse Geocode Enriched Place Profile
Reverse geocode a coordinate pair with country, timezone, and sun modules to build a full place profile.
ARAZZOPricing 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.
Positionstack 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.
Positionstack Finops
FINOPSFeatures 13
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.
Forward Geocoding
Convert addresses, place names, and postal codes into geographic coordinates.
Reverse Geocoding
Convert latitude/longitude coordinates into structured address data.
Batch Geocoding
Run up to 80 forward or reverse lookups per request (Professional plan and above).
Multiple Output Formats
Responses available in JSON, XML, and GeoJSON.
Embeddable Maps
Each result includes a `map_url` that can be embedded via iFrame.
Multi-Language Results
Localize results in multiple languages via the `language` parameter.
Country Module
Optional enrichment adding ISO codes, currency, languages, flag, dial code, and area.
Timezone Module
Optional enrichment with IANA timezone, GMT offset, abbreviation, and DST status.
Sun Module
Optional enrichment with sunrise, sunset, and solar transit times.
BBox Module
Optional enrichment with bounding box coordinates per result.
2+ Billion Places
Global coverage across 2+ billion addresses and places.
99.9% Uptime
Average reported availability across forward, reverse, and batch endpoints.
Overage Notifications
Email and dashboard alerts at 75%, 90%, and 100% of monthly quota.
Scroll within the panel for all 13 ·
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.
Positionstack 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.
positionstack API Rules
SPECTRALpositionstack API Rules
SPECTRALJSON Schema 2
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.
ErrorResponse
JSON SCHEMALocation
JSON SCHEMAJSON Structure 1
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.
Positionstack Location Structure
JSON STRUCTUREExamples 4
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 7
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.
Address Autocomplete
Power address autocomplete and validation in signup or checkout flows.
Fleet & Asset Tracking
Resolve GPS coordinates from vehicles, IoT devices, or pet trackers into addresses.
Store Locator
Geocode user-entered addresses to find nearest stores or service centers.
Logistics & Delivery
Cleanse and standardize delivery addresses across bulk shipment manifests.
Real Estate Listings
Map property listings by geocoding street addresses.
Market Analysis
Enrich CRM records with geographic, country, and timezone data.
Weather & Local Services
Pair coordinates with weather APIs (e.g. weatherstack) for hyper-local services.
Scroll within the panel for all 7 ·
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
weatherstack
Sibling apilayer API providing weather data for resolved coordinates.
ipstack
Sibling apilayer API offering IP geolocation that pairs with positionstack lookups.
streetlayer
Sibling apilayer API for address verification and autocomplete.
Mapbox / Leaflet / OpenStreetMap
Display positionstack results on third-party map libraries via the embeddable `map_url`.
Power BI / Tableau / Excel
Bulk-enrich spreadsheet data with coordinates via the batch endpoint.
Solutions 5
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Free / Hobbyist
100 requests/month, personal use, JSON output, no HTTPS.
Basic
100k req/mo, $9.99/mo, HTTPS, multi-format, commercial license.
Professional
1M req/mo, $49.99/mo, batch endpoint enabled.
Business
3M req/mo, $99.99/mo.
Enterprise / Platinum
Custom volume + SLA + dedicated account team.
Resources
Every other property we hold for positionstack — 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 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
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 4
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 2
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/positionstack · machine-readable index on apis.io