KAIROS
Global Places of Worship API / v1 Production Ready

Places of Worship API for churches, mosques, temples & synagogues.

Find nearby churches, mosques, temples, synagogues and other places of worship by latitude and longitude, religion or denomination — without managing raw OpenStreetMap schemas, Overpass queries, PostGIS storage and cache logic yourself.

verified OpenStreetMap-derived data
speed Normalized JSON responses
lock Stable OSM-backed IDs
kairos-query-runner
200 OK Example response
GET https://kairos.yarumaltech.com/v1/places/nearest?lat=6.96333&lon=-75.41722&radiusKm=8&religion=all
lat: 6.96333 lon: -75.41722 radiusKm: 8 religion: all
Spherical Canvas FIX ACTIVE
Δ 80.52m
EPSG:4326 WGS 84
{
  "data": {
    "id": "osm:way:164880258",
    "name": "Basílica Nuestra Señora de La Merced",
    "location": {
      "lat": 6.9635248,
      "lon": -75.4165179
    },
    "religion": "christian",
    "denomination": "catholic",
    "distance_m": 80.52
  },
  "meta": {
    "radius_km_used": 10
  }
}
public Global coverage

OpenStreetMap-derived coverage retrieved and cached on demand.

schema Normalized JSON

One stable response model across supported religion filters.

fingerprint Stable place IDs

Deterministic identifiers mapped to OSM ways, relations, and nodes.

filter_alt Religion filters

Religion and denomination filters for nearby searches.

radar Geospatial search

Nearest and nearby geospatial search with distance in meters.

Live API demo

Try Kairos before you integrate it.

Run a real nearest or nearby Places of Worship query. No API key is exposed in your browser. The public demo is intentionally rate-limited and uses a maximum radius of 8 km.

5 req/min per visitor live data
Query Builder

Search a location

ready

Location is only used for the query you run. Kairos does not need your location to browse this website.

Production integration

The demo endpoint is for evaluation. Production apps should use a commercial API key through RapidAPI, Zyla, or direct Kairos access.

Get an API key arrow_forward
kairos-live-demo
waiting —
Live result
Ready to query

Pick a location and press Run live query.

Response JSON
{
  "status": "ready"
}
Use this query in your app

These snippets use the production /v1 API, not the public demo endpoint.

Get API key arrow_forward
Architectural Implementations

Engineered for location-aware applications

Designed for production engineering stacks that demand high read availability, deterministic spatial geometry, and zero semantic mapping headaches.

explore
01 • TRAVEL & NAVIGATION

Travel & Local Discovery

Build nearby religious-place discovery into travel guides, municipal wayfinding, and cultural city touring applications.

radiusKm • nearest arrow_right_alt
groups
02 • AFFILIATION LOOKUPS

Faith & Community Apps

Search strictly by specific religion or denomination and retrieve stable place identifiers for community discovery and directory experiences.

religion • denomination arrow_right_alt
map
03 • CARTOGRAPHY ENGINE

Maps & Directories

Use normalized coordinates and normalized coordinates and source metadata without managing raw OSM tag parsing yourself.

coordinates • source arrow_right_alt
analytics
04 • SPATIAL ANALYTICS

Research & Location Analytics

Access structured global place-of-worship points for urban planning density models, demographic research, and spatial intelligence.

distance • stable-ids arrow_right_alt
API Reference

A small API surface. Everything you need.

Predictable resource-oriented URLs, standard HTTP response codes, and clean JSON schemas.

Base URL: https://kairos.yarumaltech.com/v1
GET Nearest Hit
/places/nearest

Find the nearest single matching place from an exact latitude and longitude origin.

Query Parameters
lat float • required
lon float • required
radiusKm float • default: 8
religion string • optional
Returns single PlaceObject with spherical distance in meters.
GET Ordered Set
/places/nearby

Return all matching places within a specified radius ordered strictly by spherical distance.

Query Parameters
lat, lon float • required
limit int • max: 200
offset int • default: 0
denomination string • optional
Returns a normalized PlaceObject[] page ordered by distance.
GET Deterministic
/places/{id}

Retrieve a specific place using a stable public identifier such as osm:node:4928192, osm:way:164880258, or osm:relation:<id>.

Path Parameter
id osm:<node|way|relation>:<id>
Returns one normalized place. distance_m is null because no search origin is supplied.
Integration in 60 seconds

One request. No Overpass QL gymnastics.

Kairos turns OpenStreetMap-derived place data into a predictable REST interface. Use a direct Kairos API key, or follow your marketplace authentication instructions, and receive normalized JSON.

check_circle
Direct and marketplace authentication Direct calls use X-API-Key. RapidAPI and Zyla manage their own consumer authentication.
check_circle
Consistent Error Schema Normalized JSON error codes with standard HTTP status codes.
check_circle
Developer resources OpenAPI, Postman, cURL, Python and JavaScript examples are public.
curl -X GET \
  -H "X-API-Key: $KAIROS_API_KEY" \
  -H "Accept: application/json" \
  "https://kairos.yarumaltech.com/v1/places/nearest?lat=6.96333&lon=-75.41722&radiusKm=8&religion=all"
The Abstraction Advantage

Stop wrestling with raw geospatial pipelines

Building directly on OpenStreetMap data means handling query logic, inconsistent tagging, geospatial storage and caching. Kairos provides a smaller normalized API surface.

cancel Without Kairos
DIY Ingestion Overhead
  • remove Overpass QL rate limits: Frequent timeouts, throttling, and inconsistent availability on public servers.
  • remove Inconsistent schemas: Wrestling with amenity=place_of_worship vs building=church vs historic=monastery.
  • remove PostGIS hosting debt: Running and maintaining spatial storage, indexes and distance queries.
  • remove Missing polygon centroids: Complex ways require dynamic center calculation and bounding box indexing.
  • remove Cache logic: Deciding when to refresh source data and how to handle temporary upstream failures.
check_circle With Kairos
Cached • Normalized
  • done One RESTful query: A simple GET request with lat, lon and radius returns a normalized response.
  • done Uniform normalized JSON: Religion, denomination, and coordinates structured cleanly across all global traditions.
  • done Deterministic stable IDs: Explicitly maps to osm:way, osm:node, or osm:relation for reliable client-side caching.
  • done Automated spherical math: Distance values are returned in meters for spatial search responses.
  • done Zero infrastructure overhead: Kairos manages query construction, normalization, caching and geospatial storage behind the API.
Places of Worship API FAQ

Common integration questions

Can Kairos work as a church API, mosque API, temple API or synagogue API?

Yes. Use the religion filter to search supported religious categories, or use religion=all to search places of worship without limiting the query to one religion.

Can I find the nearest place of worship from coordinates?

Yes. GET /v1/places/nearest accepts latitude, longitude and an optional radius, religion and denomination filter.

Where does the place data come from?

Kairos normalizes OpenStreetMap-derived data. Coverage, names, religion and denomination metadata can vary by region, and missing source values are not fabricated.

How do I try the API?

You can start through RapidAPI or Zyla Labs, and review the public Quickstart for direct integration details.

Explore Kairos

Places of Worship API guides and use cases

Explore religion-specific discovery guides and technical documentation for the Kairos nearest, nearby and stable-ID endpoints.

Ready to Integrate?

Add global places-of-worship search to your product.

Start with the RapidAPI BASIC plan or follow the public Quickstart and OpenAPI documentation for integration details.