what3words
what3words has divided the world into a grid of three-metre squares and given each one a unique three-word address (e.g. ///filled.count.soap). The what3words Public API converts between three-word addresses and latitude / longitude coordinates, offers an AutoSuggest with autocorrect for voice/typing input, exposes supported languages and locale variants, and returns grid sections as GeoJSON. The API is HTTPS GET only, authenticated by API key in a query parameter or X-Api-Key header, and is wrapped by official SDKs for Swift, Android, Java, JavaScript, Python, PHP, and .NET, plus UI components for map and OCR experiences.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles what3words the way a machine reads it — 27 machine-readable artifacts across 20 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 — what3words scores 35.9/100 (thin), 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 what3words
Each block below is one kind of artifact we hold for what3words. 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 20
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.
what3words Public API
REST API for converting between three-word addresses and latitude / longitude coordinates, with AutoSuggest, available-languages, and grid-section endpoints. JSON or GeoJSON res...
what3words convert-to-3wa Endpoint
Converts a latitude / longitude coordinate into a three-word address in a chosen language.
what3words convert-to-coordinates Endpoint
Converts a three-word address into a latitude / longitude coordinate and a bounding square.
what3words AutoSuggest Endpoint
Validates and autocorrects partial or imperfect three-word input, returning ranked suggestions. Supports focus, clipping by polygon, country, bounding box or circle, and voice-i...
what3words available-languages Endpoint
Returns all supported what3words languages and locale variants.
what3words grid-section Endpoint
Returns the what3words three-metre grid for a specified bounding box as JSON or GeoJSON, suitable for map overlays.
what3words JavaScript SDK
Official JavaScript wrapper around the what3words Public API for browser and Node.js applications.
what3words Python SDK
Official Python wrapper around the what3words Public API.
what3words Java SDK
Official Java wrapper around the what3words Public API for server-side JVM applications.
what3words PHP SDK
Official PHP wrapper around the what3words Public API.
what3words Swift SDK
Official Swift wrapper around the what3words Public API for iOS, iPadOS, and macOS applications.
what3words Android SDK
Official Android wrapper around the what3words Public API for native Android applications.
what3words Swift Map Components
UI components for embedding what3words grids, markers, and AutoSuggest experiences in Apple Maps-based iOS and iPadOS applications.
what3words OCR Camera Component
UI component that uses the device camera to scan three-word addresses from signage, packaging, or printed materials.
what3words API Docs and OpenAPI Repository
Public repository hosting the OpenAPI specification, LLM files, and reference material for the what3words Public API.
what3words Autosuggest API
The Autosuggest API from what3words — 1 operation(s) for autosuggest.
what3words Available Languages API
The Available Languages API from what3words — 1 operation(s) for available languages.
what3words Convert To 3wa API
The Convert To 3wa API from what3words — 1 operation(s) for convert to 3wa.
what3words Convert To Coordinates API
The Convert To Coordinates API from what3words — 1 operation(s) for convert to coordinates.
what3words Grid Section API
The Grid Section API from what3words — 1 operation(s) for grid section.
Scroll within the panel for all 20 ·
Open 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).
what3words Public 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.
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.
What3Words 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.
What3Words Finops
FINOPSSecurity 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 what3words — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
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 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/what3words · machine-readable index on apis.io