Signals
Raw normalised signal catalog per area. The primitive: every other product composes from this.
- GET/v1/area
- GET/v1/signals/:category
- GET/v1/areas
- GET/v1/meta
The OneGoodArea API exposes four composable products on one signal-first engine, plus a per-organisation control plane. Read the methodology to understand how the engine works. Open the interactive reference to query it.
Same vocabulary as the marketing surfaces. Each tile lists its live endpoints. The engine details live on the methodology page; the interactive request runner lives on the reference.
Raw normalised signal catalog per area. The primitive: every other product composes from this.
Deterministic composite score per area. Four presets, custom weights, or saved organisation preset_id.
Portfolios of tracked areas. Bulk enrich, detect monthly change, fire signal.changed webhooks.
Typed query plane. AI emits the plan; the database answers. 6 plan ops, 92.9% planner accuracy.
Different audience to the four products. Admins configure how the engine behaves for their organisation: custom signal bundles, saved scoring presets, methodology pinning, peer cohorts, members and RBAC, white-label, IP allowlist.
Full request shapes on the interactive reference . Methodology rationale on the Levers section of /methodology .
The engine details and the request runner. Both are live, both stay in step with the backend.
14 sections covering signals, store, time-series, scoring, Intelligence, Levers, versioning. The why behind every endpoint.
Read methodology03.2OpenAPI 3.0 spec auto-generated from the live Fastify schemas. Request shapes, response shapes, try-it-in-browser. Stays in step with the backend on every deploy.
Open referenceGet an API key and start scoring areas. The methodology and the reference are both live.