# Geocode Cache (Postgres-backed) — https://db-geo-geocode.0exec.com

Same shape as geo-geocode, with a Postgres cache layer in front.

First request hits geo-geocode upstream; subsequent identical queries return cached result.

## Endpoints
- `GET /` — Geocode with caching
    - `text` (query, required): Address (free-form text)
    - `output` (query, optional): json | xml
    - returns: application/json
    - example: `https://db-geo-geocode.0exec.com/?text=Cluj-Napoca`

## Examples
    curl 'https://db-geo-geocode.0exec.com/?text=Cluj-Napoca'

## Meta endpoints (gateway-served, no upstream call)
- `GET /.deploy/version.json` — current deployed commit
- `GET /openapi.json`         — machine-readable OpenAPI 3.1 spec
- `GET /llms.txt`             — this file
- `GET /_gw_health`           — gateway liveness probe

Source: https://github.com/baditaflorin/db-geo-geocode