Government of British Columbia APIs for AI Agents
Maps GeolocationContent DeliveryData TransformationOfficial Vendor SpecsNo authAPI keyoauth2, apiKeyAgent Ready
Government of British Columbia API Catalog
9 APIs across 4 product groups.
Maps Geolocation5
BC Route Planner REST APICompute distance, optimal routes, and turn-by-turn directions across British Columbia's road network, with a separate truck mode that respects commercial vehicle restrictions.~22 endpointsGeocoder REST APIGeocode and reverse-geocode British Columbia addresses, occupants, and intersections, with proximity search around a coordinate.~16 endpointsBC Geographical Names Web Service - REST APISearch and retrieve official British Columbia geographical names - features, name histories, and name authority decisions - with no authentication required.~14 endpointsGeoMark Web Service REST APICreate reusable geographic areas of interest and serve them in multiple file formats and coordinate systems for cross-tool sharing.~7 endpointsDriveBC's Open511 APILook up live road events, closures, and construction in British Columbia, filtered by area, jurisdiction, or event type.~4 endpoints
Data Enrichment2
Groundwater Wells, Aquifers and Registry APILook up British Columbia groundwater wells, mapped aquifers, and registered well drillers and pump installers along with the supporting code lists.~24 endpointsBC Data Catalogue APISearch and retrieve metadata for British Columbia open government datasets exposed through the CKAN-based BC Data Catalogue.~22 endpoints
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring these APIs by hand means juggling different hosts, output-format path segments, and auth models across nine services. With Jentic you install Jentic One once, then find and add any of the Government of British Columbia APIs from the Jentic directory to your workspace, and your agent calls them through one consistent path.
Permission scoping
You decide which operations each API exposes to the agent, so you can allow read-only lookups such as geocoding, dataset search, or listing road events while leaving out operations like creating a geomark or truck routing. Your own rules in your Jentic One instance scope which operations and credentials the agent may use, so it cannot reach anything you have not included.
Credential isolation
FAQs
Specific to using Government of British Columbia APIs through Jentic.
What can I build with the Government of British Columbia APIs together?
The APIs combine into province-wide workflows. You can geocode an address, check live road events, and plan a route that avoids closures; resolve official place names for geocoded points; or discover an open dataset and geocode the addresses inside it. Each API covers the same province, so their coordinates, road network, and named features line up.
Do these APIs all use the same authentication?
No. Several are anonymous open data, including the news, geographical names, geomark, job posting, and Open511 services. The geocoder and route planner require an apikey issued through the BC API directory, GWELLS uses a JWT bearer token for protected operations, and the data catalogue accepts a CKAN API key for restricted reads.
Is the whole portfolio limited to British Columbia?
Yes. These are provincial government services, so coverage is British Columbia only. The geocoder, route planner, geographical names, and Open511 feeds do not extend to other provinces or countries, and for locations elsewhere you would use a global provider instead.
Can any developer use every API in this portfolio?
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
