// Docs
Current live boundaries, query semantics, and integration-facing product notes for the public delivery surface.
// Quick Start
The public surface is managed and clearly bounded. Start by identifying the correct product surface and reading its delivery boundary.
01
Use geo_object_id as the primary contract key across region-facing products.
02
Macro and Facilities are the strongest stable live surfaces; News and Events have explicitly bounded coverage.
03
This documentation describes public delivery contracts and product usage guidance.
// Documentation Index
Each entry opens a dedicated reference page with request shape, field semantics, freshness notes, and delivery boundaries.
// Product Docs
5 documents
Stable country-level macro series delivered through a managed API surface with explicit query contracts.
Audience
Integrators, portfolio teams, economic monitoring workflows
Applies to
Country-level macro package
Updated
March 2026
Normalized facility outputs tied to standard geo objects and optimized for regional lookup.
Audience
Spatial products, regional overlays, location-aware workflows
Applies to
Facility and POI surfaces
Updated
March 2026
Current regional news baseline with freshness semantics and coverage boundaries stated up front.
Audience
Regional monitoring, context feeds, intelligence curation
Applies to
Enabled-source regional news surface
Updated
March 2026
Aggregated event view derived from current regional news updates rather than a complete global event archive.
Audience
Event surveillance, escalation monitoring, regional alerting
Applies to
Recent non-empty event aggregates
Updated
March 2026
Contextual region profile with source contribution notes and designed to be read as synthesized intelligence.
Audience
Regional screening, context intelligence, profile overlays
Applies to
Multi-source synthesized profile surface
Updated
March 2026
// API Reference
1 document
// GEO & Query Semantics
1 document
// Release Notes
1 document
// Boundary
This documentation covers the public delivery surface and integration contract. Administrative workflows are intentionally outside this layer.