Gov Bc Ca APIs
9 APIs141 Endpoints4 Categories
Categories
API Catalog(5 of 9)
BC Geographical Names Web Service - REST API
The BC Geographical Names Web Service exposes searchable, authoritative records for the official place names of British Columbia, including features such as lakes, rivers, mountains, communities, and parks. It serves the Province's gazetteer with endpoints for keyword search, official-only and not-official-only search, spatial 'inside' and 'near' search, recent name decisions, name change history, and detail lookup by name or feature ID. The service responds in multiple output formats and supports a feature taxonomy enumeration for filtering by feature class.
14 endpointsBC Route Planner REST API
The BC Route Planner is the British Columbia government's routing engine for the province's public road network, computing shortest and fastest routes between a start point and one or more stops. It exposes pairwise distance, optimal route ordering, turn-by-turn directions, and a dedicated truck routing track that respects commercial vehicle restrictions. Output formats include JSON, GeoJSON, and KML, with 22 endpoints split across passenger and truck modes. Access is currently restricted to B.C. Government Ministries.
22 endpointsDriveBC's Open511 API
DriveBC's Open511 API publishes real-time road events for British Columbia's public road network, conforming to the Open511 specification. Agents can query traffic accidents, construction zones, weather closures, and other roadwork events filtered by jurisdiction, geographic area, severity, and event type. The endpoint set covers four resources: events, jurisdictions, jurisdiction geography, and named areas, returning GeoJSON-style geometry alongside structured event metadata.
Connect Your Agent
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.