wikipedia.nearby

stable Advanced

Wikipedia articles near a latitude/longitude (10 km).

GET /v1/wikipedia/nearby

What you get#

A list of Wikipedia results in Onekey's unified shape, in data (an array). An empty array is a normal, successful answer and is charged like any other; a source that reports "nothing found" as an error returns a free 404 not_found instead.

What it costs#

Advanced · 5 credits for a fresh fetch, charged only when it succeeds.
Free when served from cache (0.2 credit for a cached response over 100 KB).
Free if the request is invalid (never charged) or the source fails or reports not found (refunded).

Parameters#

Name	Type	Required	Default	What it is	Constraints
`lat`	string	yes	(required)	Latitude	max 10 chars; must match `-?(?:[0-8]?[0-9](?:\.[0-9]{1,6})?\|90(?:\.0{1,6})?)`; trimmed
`lon`	string	yes	(required)	Longitude	max 11 chars; must match `-?(?:1[0-7][0-9]\|[0-9]{1,2})(?:\.[0-9]{1,6})?\|-?180(?:\.0{1,6})?`; trimmed

Request#

curl "https://api.onekey.dev/v1/wikipedia/nearby?lat=51.5074&lon=-0.1278" \
  -H "x-api-key: YOUR_API_KEY"

Try it

Add your key to run this call right here. No key? Get one free. The key stays in this tab.

Recorded response#

A real Wikipedia response, recorded and returned in Onekey's shape. Fields the platform does not provide are null.

json

{
  "success": true,
  "data": [
    {
      "content": {
        "id": "33109245",
        "title": "Equestrian statue of Charles I, Charing Cross"
      },
      "ext": {
        "distanceMeters": 10.7
      },
      "place": {
        "lat": 51.50734,
        "lon": -0.12768
      }
    },
    {
      "content": {
        "id": "84221192",
        "title": "Parliament Street from Trafalgar Square"
      },
      "ext": {
        "distanceMeters": 18.7
      },
      "place": {
        "lat": 51.507503,
        "lon": -0.128014
      }
    }
  ],
  "metadata": {
    "platform": "wikipedia",
    "endpoint": "nearby",
    "cached": false,
    "stale": false,
    "age_s": 0,
    "fetched_at": "2026-01-01T12:00:00+00:00",
    "credits_charged": 5,
    "request_id": "7f3a9c2e5b1d4c8fa2e6d0b9c4f18e37"
  },
  "error": null
}

Field mapping#

How this endpoint's source fields become Onekey's unified schema. Fields the source lacks come back as null.

Source path	Onekey field	Transform
`pageid`	`content.id`	`toString`
`title`	`content.title`	-
`dist`	`ext.distanceMeters`	`toNumber`
`lat`	`place.lat`	`toNumber`
`lon`	`place.lon`	`toNumber`

Caching and freshness#

Fresh for about 2 minutes. Repeat calls in that window are served from cache and are free.
Between 2 minutes and 15 minutes the cached copy is still served instantly and marked stale: true while Onekey refreshes it in the background.
If the source is down when a refresh is needed, the last copy can be served for up to 1 hour more (marked stale).
A "not found" is remembered for 1 minute and is free.
The cache is shared across all customers, which is what keeps repeat calls cheap.

What can go wrong#

Status	Code	What to do
401	`unauthorized`	Check the `x-api-key` header.
402	`insufficient_credits`	Add credits; your balance must cover the price.
404	`not_found`	Unknown endpoint path.
422	`invalid_params`	Fix the parameters using the table above. Free.
429	`rate_limited`	Wait `Retry-After` seconds, then retry.
502	`upstream_error`	The source failed. Refunded; retry with backoff.

See Errors for the full list and retry guidance.

Status: stable (verified against the live source).