The data layer underneath UK property and risk workflows: area scores, source-backed signals, monitoring, and intelligence you can audit.
Drop one endpoint into your property detail render and ship richer area context than a competitor's roadmap. LSOA-grain signals across seven categories with country-scoped percentiles, per-signal confidence, and source attribution on every response.
GET/v1/areaSignals are the primitive. Scores compose them into a number. Monitor watches them over time. Intelligence queries them in plan-form. Use one. Use all four. Same engine, same lineage, same audit trail.
Raw normalized data per area. Every signal carries source, observed period, confidence, normalized value, and country-scoped percentile.
GET/v1/area?postcode=…Composite 0-100 score per area. Presets or custom weights. Deterministic frozen engine; same input always returns the same number.
POST/v1/scoreSave a portfolio, enrich it, detect material change month over month. Webhook alerts when a signal moves past your configured threshold.
POST/v1/portfolios/:id/enrichTyped query plane over the store. Ask in JSON or natural language. AI emits the plan; the database answers. Every result is reproducible.
POST/v1/queryConsume the engine however your stack works. Authenticated, versioned, documented. Every response stamped with the engine version that produced it.
01curl -H "Authorization: Bearer oga_..." \02 "https://onegoodarea.onrender.com/v1/area?postcode=M1+1AE"0304// 200 OK05{06 "geo_code": "E01005132",07 "engine_version": "1.0.0",08 "signals": {09 "deprivation.imd_decile": {10 "value": 2,11 "normalized_value": 0.78,12 "percentile": 0.92,13 "confidence": 1.014 }15 }16}
One authenticated call returns a full area profile: every signal with source citation, normalized value, country-scoped percentile, and confidence. Versioned, documented, production-ready.
See it on the referencePin the engine version once and your integration stays reproducible. Same plan → same result, regardless of when you replay it.
1.8 million postcodes resolved to 43,916 LSOAs across England, Wales, and Scotland. Captured once a month, never re-captured. The time-series corpus that compounds into the moat.
API plus a dashboard control plane. Deterministic, version-pinned, source-attributed on every response.