BC Data docs

crtc_service_availability

B.C. broadband and mobile service availability by community (CRTC)

CRTC Communications Market Report data (Table 9) for British Columbia census subdivisions (municipalities and similar areas), 2016 to 2025: the dwellings counted and, for each fixed-broadband speed marker (1.5+, 5+, 10+, 16+, 25+, 50+, 100+, 150+, 200+ Mbps, Gigabit, 50/10 any plan or unlimited) and mobile technology (any mobile, HSPA+, LTE, LTE-Advanced, 5G NR), the dwellings with that service available, with a computed percentage. Give community (name words at the start of the name, for example Chilliwack or North Vancouver) or csd_id. Without years the latest year is returned; year_from and year_to give a series (one alone is open-ended); speed narrows to one marker. Results are per community and population-centre class (rural, small, medium, large), plus a computed total for the whole community. These are provider-reported availability counts for census subdivisions, not address-level availability, subscriptions, prices or measured speeds, and the CRTC's dictionary does not define this table's columns (see notes). For hexagon-level availability and providers around a point use broadband_availability.

Cost: 2 units of your allowance (see Rate limits).

Parameters

  • community (string, optional): min length 2, max length 60
  • csd_id (string, optional)
  • year_from (string, optional)
  • year_to (string, optional)
  • speed (1.5+, 5+, 10+, 16+, 25+, 50+, 100+, 150+, 200+, Gigabit, 50/10/Any, 50/10/U, AllMobile, HSPA+, LTE, LTEA, NR, optional)
  • limit (integer, optional): min 1, max 10, default 3

REST

curl -X POST https://api.bcmcp.ca/v1/tools/crtc_service_availability \
  -H "Authorization: Bearer $BCDATA_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

MCP

Call the tool crtc_service_availability with these arguments. Over raw JSON-RPC:

curl -X POST https://api.bcmcp.ca/mcp \
  -H "Authorization: Bearer $BCDATA_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"crtc_service_availability","arguments":{}}}'

What comes back

Every answer is the same envelope, over REST and over MCP: available, data, citations, freshness and notes. See Citations and freshness.

On this page