Use case
People doing Morocco-focused research, policy analysis or map products fetch commune-level population and boundary data by code through the API or MCP server for statistics and mapping.
Previously teams manually downloaded official census files, cleaned codes themselves and joined boundary files, or used incomplete third-party map data.
Commune-level census data and boundaries are usually scattered across official files and tables with inconsistent coding, so assembling a usable dataset takes heavy manual work and easily mismatches years.
xOcto's call
Demand is evidenced
Trend: local public data is being packaged into open datasets with API and MCP interfaces so AI agents can query administrative units directly. Entry: start with Moroccan research institutes, NGOs or government contractors, charging for data subscription or custom queries; no pricing or customers are disclosed, so the selling model remains unverified.
Reason to use it
Why users would choose it
Inference: versus manual cleaning, it packages codes, two census rounds and boundaries behind one interface, saving a cleaning and alignment step, so researchers or map developers who query repeatedly would pick it when building a dataset.
Where the easy answer breaks down
The tension worth following
An English validation note will follow from the public evidence.
If this is your job
Worth trying. Inference: versus manual cleaning, it packages codes, two census rounds and boundaries behind one interface, saving a cleaning and alignment step, so researchers or map developers who query repeatedly would pick it when building a dataset.
Entry and what to borrow
Trend: local public data is being packaged into open datasets with API and MCP interfaces so AI agents can query administrative units directly. Entry: start with Moroccan research institutes, NGOs or government contractors, charging for data subscription or custom queries; no pricing or customers are disclosed, so the selling model remains unverified.