API documentation

Base URL

https://streetsignal.co.za/api/v1

Endpoints

Meta

API version, data source descriptions, update cycles, and schema reference.

GET /api/v1/meta.json

All suburbs (summary)

Lightweight array of all 744 suburbs with key metrics: safety index, risk profile, median property valuation, school count, healthcare access, civic responsiveness, and taxi route connectivity.

GET /api/v1/suburbs.json

Bulk download (CSV)

The same summary dataset as a CSV file, one row per suburb, for spreadsheet users and bulk analysis. Same licence and attribution terms as the JSON endpoints.

GET /api/v1/suburbs.csv

Suburb detail

Full profile for a single suburb including safety, property, education, transport, services, healthcare, and census data.

GET /api/v1/suburbs/{slug}.json

OpenAPI spec

A machine-readable OpenAPI 3.1 specification is available at /api/openapi.json. It documents all endpoints, request parameters, response schemas, and reserved headers for the upcoming commercial tier. Import it into Swagger UI, Postman, or any OpenAPI-compatible tool.

MCP server

AI assistants can query StreetSignal data directly through our Model Context Protocol server. It exposes the same public data as the static API through five read-only tools:get_suburb_profile, compare_suburbs, rank_suburbs,search_suburbs, and get_methodology.

https://mcp.streetsignal.co.za/mcp

The transport is streamable HTTP with no authentication. Requests are limited to 60 per minute per IP. A machine-readable server card is published at/.well-known/mcp.json. Tool responses carry the same caveats as the site: safety indices are relative to other Cape Town suburbs, not absolute measures.

Example client configuration:

{
  "mcpServers": {
    "streetsignal": {
      "type": "http",
      "url": "https://mcp.streetsignal.co.za/mcp"
    }
  }
}

The MCP server is experimental (v0.1.0). The tool surface may change while we learn how assistants use it.

Example

Fetch the full profile for Camps Bay:

curl https://streetsignal.co.za/api/v1/suburbs/camps-bay.json

Response structure:

{
  "slug": "camps-bay",
  "name": "Camps Bay",
  "coordinates": { "lat": -33.951, "lng": 18.378 },
  "police_station": "Camps Bay",
  "is_proxy_precinct": false,
  "safety": {
    "score": 72,
    "risk_profile": "Lower reported crime",
    "trend": "Stable",
    "is_proxy_precinct": false,
    "tourist_paradox": true
  },
  "property": {
    "median_gv": 5500000,
    "percentile": 99,
    "cagr": 0.054,
    "median_band": "R4M – R6M"
  },
  "education": {
    "school_count": 3,
    "matric_pass_rate": 92.1
  },
  "transport": {
    "dominant_mode": "car",
    "taxi_routes": 2
  },
  "services": {
    "civic_responsiveness_percentile": 85,
    "median_resolution_days": 4
  },
  "healthcare": {
    "facilities_within_5km": 12,
    "nearest_facility_km": 1.2
  },
  "census": {
    "population": 3890
  }
}

Values shown are illustrative. Fetch the endpoint for current data.

Schema reference

Summary fields (suburbs.json)

Detail fields (suburbs/{slug}.json)

Includes all summary fields plus nested objects for safety,property, education, transport,services, healthcare, and census. See the example response above for the full structure.

Data sources

• Safety: SAPS quarterly crime statistics, processed through the CHI composite safety pipeline.
• Property: City of Cape Town General Valuation Roll 2022. Municipal rates valuations, not market transaction prices.
• Education: Department of Basic Education EMIS masterlist, Western Cape Q2 2025.
• Healthcare: City of Cape Town health facility register. Haversine distance to 157 facilities.
• Transport: City of Cape Town minibus taxi route data and MyCiTi stop locations.
• Civic: City of Cape Town C3 service request complaints data (2.5 million records).
• Census: Statistics South Africa Census 2022 sub-place population crosswalk.

Full methodology documentation is available on themethodology page.

Usage terms

The API is free for non-commercial use. Attribution to StreetSignal is required when displaying data publicly. For commercial use, custom integrations, or bulk access, see our data products or contact us at[email protected].

Data is regenerated at each site build. Responses are served as static files via Cloudflare CDN. There are no rate limits, but please cache responses on your end where possible.