Gov Bc Ca BC Geographical Names Web Service - REST API
Browse all Gov Bc Ca APIs54
AI ReadinessFoundational (C)54/100
Official vendor OpenAPI document · agent-readyMaps GeolocationPlaces Searchnone14 EndpointsREST
For Agents
Search and retrieve official British Columbia geographical names - features, name histories, and name authority decisions - with no authentication required.
Use for: Search BC geographical names for 'fraser river', Find the official name of a feature near a coordinate, List all geographical names inside a bounding box in northern BC, Get the full record for a specific BC name ID
Not supported: Does not geocode addresses, render maps, or cover places outside British Columbia - use for searching the BC Geographical Names gazetteer only.
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.
Install Jentic One Beta
Connect the BC Geographical Names Web Service - REST API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BC Geographical Names Web Service - REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgov.bc.ca%2Fbcgnws" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgov.bc.ca%2Fbcgnws" | 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.
Capabilities
What an agent can do with BC Geographical Names Web Service - REST API.
Search BC geographical names by keyword across official and unofficial records
Limit search to officially adopted names or to not-official names only
Find names whose feature lies inside a supplied bounding box or polygon
Find names whose feature is near a supplied point within a distance
List recent BC name authority decisions across a date range
Look up the full record for a single name by name ID and output format
Look up the full record for a feature by feature ID
Use Cases
Patterns agents use BC Geographical Names Web Service - REST API for, with concrete tasks.
★ Authoritative Place Name Lookup
Resolve a possibly informal place reference (such as 'mount baker bc') to the official BC name and its feature class. GET /names/search performs a keyword search and the result identifies whether the name is officially adopted by the BC Geographical Names Office. Useful for downstream mapping or government correspondence that needs canonical names.
Search BC geographical names for 'mount robson' and return the name ID and the official adoption status of the top result.
Spatial Names Around a Point
List every named geographical feature inside a polygon or near a coordinate to enrich a map with point-of-interest labels. GET /names/inside accepts bounding geometry and GET /names/near accepts a point and distance, both returning matching named features with classes such as lake, river, or peak.
List all BC geographical names within 5 kilometres of latitude 49.7 longitude -123.1 and return their names and feature classes.
Name Change Monitoring
Track BC Geographical Names Office decisions over time so downstream maps and gazetteers can be refreshed promptly. GET /names/decisions/recent returns recent adoption and rescission decisions and GET /names/changes covers historical name changes. This is critical when reconciliation reflects modern Indigenous place names.
List BC name authority decisions from the most recent year and return the official names and decision dates.
AI Agent Place Name Resolver
An AI agent built on Jentic disambiguates user references to BC places by calling the BC Geographical Names Web Service. The agent searches Jentic for 'find a bc geographical name', loads the names search operation, and returns the official record so downstream tools (maps, routing) use canonical identifiers.
Use Jentic to search 'find a bc geographical name' and resolve 'haida gwaii' to its official BC name record and feature class.
Key Endpoints
14 endpoints — 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.
METHOD
PATH
DESCRIPTION
GET
/names/search
Search BC geographical names by keyword
GET
/names/official/search
Search officially adopted BC names only
GET
/names/inside
Find names inside a bounding geometry
GET
/names/near
Find names near a coordinate
GET
/names/decisions/recent
List recent BC name authority decisions
GET
/names/{nameId}.{outputFormat}
Look up a single name by ID
GET
/features/{featureId}
Look up a feature by feature ID
GET
/names/search
Search BC geographical names by keyword
GET
/names/official/search
Search officially adopted BC names only
GET
/names/inside
Find names inside a bounding geometry
GET
/names/near
Find names near a coordinate
GET
/names/decisions/recent
List recent BC name authority decisions
GET
/names/{nameId}.{outputFormat}
Look up a single name by ID
GET
/features/{featureId}
Look up a feature by feature ID
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
B
BC Geographical Names Web Service - REST API
- Foundational (C)54/100
99
Foundational Compliance59
Developer Experience & Jentic Compatibility26
AI-Readiness & Agent Experience94
Agent Usability100
Security83
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
59
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
12%
Example Density
How richly the API is illustrated with examples.
79%
Example Validity
Percentage of examples that conform to their schemas.
43%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
26
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
54%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
83
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: ASignals: 1
83%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the BC Geographical Names Web Service by hand means choosing among its production, test, and delivery hosts and mapping the gazetteer search routes yourself, even though no credential is required. Through Jentic you install once, import the BC Geographical Names service from the API Directory, and your agent calls it through one consistent path.
Permission scoping
This service is read-only over the gazetteer, and even where a name or feature id appears in the path (/names/{nameId}, /features/{featureId}) no write exists, so limit the agent to the operations it needs, such as searching or looking up a named feature. You choose the operations it may call, so the agent cannot reach anything you have not included.
Credential isolation
This service needs no credential, so none is stored, and Jentic still routes each call through your own Jentic One instance so agent activity is logged consistently.
Intent-based discovery
Agents search Jentic by intent such as 'find a bc place name' or 'list named features inside a bounding box', and Jentic returns the matching BC Geographical Names operation with its parameters typed so the agent calls the right endpoint without reading the docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using BC Geographical Names Web Service - REST API through Jentic.
What authentication does the BC Geographical Names API use?
The OpenAPI spec defines no security schemes for this service, so requests are made anonymously over HTTPS. No bearer token or API key is required, and Jentic relays calls as-is without injecting credentials.
Can I find geographical names inside a bounding box with the BC Geographical Names API?
Yes. GET /names/inside accepts bounding geometry parameters and returns all named features whose geometry falls inside it. For radius-based queries against a point, use GET /names/near instead.
What are the rate limits for the BC Geographical Names API?
The spec does not declare specific rate limits. Because the service is shared public infrastructure, paginate large queries with the supplied page parameters and avoid issuing many parallel inside or near queries against wide regions.
How do I look up a BC place name through Jentic?
Search Jentic for 'find a bc geographical name', load the GET /names/search operation, and execute with the name query parameter. With pip install jentic, the call returns the official BC name records along with name IDs and feature classes.
Does the BC Geographical Names API return Indigenous and modern place names?
Yes. The service includes both officially adopted names - which now include many Indigenous place names - and not-official names. Use GET /names/official/search for officially adopted names only, and GET /names/decisions/recent to see recent adoption decisions.
Can I limit what my agent is allowed to do with the BC Geographical Names API?
Yes. Because you run Jentic One yourself, your own rules decide which BC Geographical Names operations the agent can call, so you can allow only what it needs, such as GET /names/search for keyword lookups or GET /names/inside and GET /names/near for spatial queries, while excluding the rest. The service is read-only over the gazetteer, and even the id-based paths GET /names/{nameId} and GET /features/{featureId} perform no writes, so the agent can never modify data. Any operation you leave out of the allowed set is simply unreachable to the agent.
GET STARTED