ZylerZee Data API · Beta
Place data with
its context intact.
Search the public place and occupation facts that support ZylerZee. Every measurement includes a unit, every dataset includes its source and release, and private customer activity stays private.
Start here
No key required during beta.
The first public release is read-only and covers the United States. Responses are JSON, list endpoints use cursor pagination, and the current maximum page size is 100 records.
curl "https://zylerzee.com/api/v1/places?q=Portland"
Endpoints
A small, legible surface.
GET /api/v1/placesSearch metros and micropolitan areas by name, region or geography type.
GET /api/v1/places/{id}Read household, mobility, housing and climate facts plus an approved place guide and structured characteristics when available.
GET /api/v1/occupationsSearch the U.S. occupation vocabulary by title or SOC code.
GET /api/v1/occupations/{id}/marketsCompare employment, wages and concentration across local markets.
GET /api/v1/trendsRead privacy-thresholded anonymous trends from completed matches.
The contract
Built to travel.
Identifiers include their country and source geography. Names are language-addressable, currency and measurement units are never implied, and each detailed record identifies its underlying release. The schema can therefore grow beyond one country without changing what an existing field means.
This is a beta interface. We will preserve version 1 semantics, announce material changes, and introduce a new version before making incompatible changes.
Privacy boundary
Public facts, not private lives.
The Data API does not expose customer accounts, questionnaire answers, recent searches, saved results or public-share tokens. Trend reporting uses separate anonymous aggregate counts, suppresses low-volume categories and never provides a feed of individual activity.
Questions or commercial use? support@zylerzee.com