Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Data Enrichment / Gov Bc Ca / Groundwater Wells, Aquifers and Registry API
Groundwater Wells, Aquifers and Registry API logo

Gov Bc Ca Groundwater Wells, Aquifers and Registry API

Browse all Gov Bc Ca APIs
41
AI ReadinessFoundational (D-)41/100
See full scorecard
Official vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey24 EndpointsREST

For Agents

Look up British Columbia groundwater wells, mapped aquifers, and registered well drillers and pump installers along with the supporting code lists.

Use for: List all mapped aquifers in BC, Get the full record for aquifer ID 1234, Look up the BC aquifer materials code list, Find aquifer productivity codes used in BC well records

Not supported: Does not handle real-time water quality measurements, well permit issuance, or non-BC groundwater records - use for BC GWELLS aquifer and registry lookups only.

The Groundwater Wells, Aquifers and Registry (GWELLS) API exposes the British Columbia provincial register of groundwater wells, mapped aquifers, and qualified well drillers and pump installers. It serves codes for aquifer materials, productivity, vulnerability, and water use, plus listings and detail records for individual aquifers. Authentication is by JWT bearer token in the Bearer header for write operations, while many lookup endpoints are read-only over HTTPS. The dataset supports water security planning, drilling industry oversight, and applications that surface authoritative groundwater information to the public.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Groundwater Wells, Aquifers and Registry API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Groundwater Wells, Aquifers and Registry 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%2Fgwells" | sh
2

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%2Fgwells" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Groundwater Wells, Aquifers and Registry API.

List aquifer demand, materials, productivity, quality concerns, subtypes, vulnerability, and water-use codes used in BC groundwater records

List all mapped aquifers in the BC GWELLS register

Look up the names and IDs of mapped BC aquifers

Retrieve the full record for a single aquifer by aquifer ID

Browse the BC well driller and pump installer registry

Fetch supporting code values needed to interpret well records

Surface authoritative groundwater data into a downstream water-management tool

Use Cases

Patterns agents use Groundwater Wells, Aquifers and Registry API for, with concrete tasks.

★ Aquifer Discovery for Water Planning

A water-security planning team needs the inventory of mapped aquifers in a region. GET /aquifers/ lists every mapped aquifer and GET /aquifers/{aquifer_id}/ returns the full record for one. Pair with the aquifer code endpoints to interpret materials, productivity, and vulnerability classifications without re-deriving them.

Retrieve aquifer ID 1234 from GWELLS and return its name, materials classification, and vulnerability rating.

Well Driller Registry Lookup

Verify a contractor before hiring by checking the BC GWELLS registry of qualified well drillers and pump installers. The API surfaces registry data alongside the wells and aquifers endpoints, so a customer-facing tool can confirm registration without redirecting users to the BC government portal.

Retrieve the list of mapped BC aquifers and return the count along with the names of the first five.

Code List Hydration

Aquifer detail records reference codes for materials, productivity, water use, and vulnerability. GET /aquifer-codes/materials/, /aquifer-codes/productivity/, /aquifer-codes/water-use/, and /aquifer-codes/vulnerability/ return the canonical code lists so applications can hydrate human-readable labels at display time.

Fetch the BC aquifer materials code list and return each code value with its label.

AI Agent Groundwater Briefer

An AI research agent built on Jentic helps a journalist or analyst summarise BC groundwater conditions for a region. The agent searches Jentic for 'list bc aquifers', loads the GET /aquifers/ operation, and joins each aquifer record with the code lookups to produce a readable briefing without manual cross-referencing.

Use Jentic to search 'list bc aquifers' and return the names of all mapped aquifers along with their productivity codes.

Key Endpoints

24 endpoints — the groundwater wells, aquifers and registry (gwells) api exposes the british columbia provincial register of groundwater wells, mapped aquifers, and qualified well drillers and pump installers.

METHOD

PATH

DESCRIPTION

GET

/aquifers/

List all mapped BC aquifers

GET

/aquifers/names/

List aquifer names and IDs

GET

/aquifers/{aquifer_id}/

Retrieve a single aquifer record

GET

/aquifer-codes/materials/

List aquifer materials codes

GET

/aquifer-codes/productivity/

List aquifer productivity codes

GET

/aquifer-codes/vulnerability/

List aquifer vulnerability codes

GET

/aquifer-codes/water-use/

List aquifer water-use codes

GET

/aquifers/

List all mapped BC aquifers

GET

/aquifers/names/

List aquifer names and IDs

GET

/aquifers/{aquifer_id}/

Retrieve a single aquifer record

GET

/aquifer-codes/materials/

List aquifer materials codes

GET

/aquifer-codes/productivity/

List aquifer productivity codes

GET

/aquifer-codes/vulnerability/

List aquifer vulnerability codes

GET

/aquifer-codes/water-use/

List aquifer water-use codes

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.

G

Groundwater Wells, Aquifers and Registry API

- Foundational (D-)
41/100
71
Foundational Compliance
56
Developer Experience & Jentic Compatibility
20
AI-Readiness & Agent Experience
94
Agent Usability
50
Security
45
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
71

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
86%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

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.

56

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

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.

20

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
10%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

71%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

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.

50

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1
50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

45

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: DSignals: 1
45%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the GWELLS Groundwater Wells, Aquifers and Registry API by hand means setting the JWT header on protected operations while leaving anonymous reads untouched, and mapping the aquifer and code-list routes yourself. Through Jentic you install once, import GWELLS from the API Directory, store the token once for protected calls, and your agent calls it.

Permission scoping

GWELLS puts the aquifer id in the URL path (/aquifers/{aquifer_id}), so a rule can pin your agent to one aquifer for the read routes, and the aquifer-code lists are read-only lookups. You choose the operations it may call, so the agent cannot reach anything you have not included.

Credential isolation

Your GWELLS JWT is stored once, encrypted, by your own Jentic One instance and injected as the Bearer header on protected operations at execution time. It never enters the agent's prompt, logs, or context, and anonymous reads pass through unchanged.

Intent-based discovery

Agents search Jentic by intent such as 'list bc aquifers' or 'look up an aquifer', and Jentic returns the matching GWELLS operation with its parameters typed, including aquifer_id paths, so the agent calls the right endpoint without reading the docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

BC Data Catalogue API

→

Use the BC Data Catalogue to discover related water and environmental datasets

Pair when a groundwater workflow needs related published datasets (water quality, hydrology, etc.) discoverable by package_search

Complementary

BC Geocoder REST API

→

Use BC Geocoder to resolve well-site or aquifer addresses to coordinates

Pair when a groundwater record's location needs to be geocoded for mapping

Alternative

NOAA API

→

NOAA offers US environmental data rather than BC-specific groundwater records

Choose NOAA when the question is about US hydrology rather than British Columbia aquifers

FAQs

Specific to using Groundwater Wells, Aquifers and Registry API through Jentic.

What authentication does the BC GWELLS API use?

The OpenAPI spec defines a bearer-style scheme using a JWT in the Bearer header for protected operations. Many read endpoints are accessible without a token. When called through Jentic, the JWT is held in Jentic's encrypted vault and injected on the request when needed.

Can I list all mapped BC aquifers with the GWELLS API?

Yes. GET /aquifers/ returns the full list of mapped aquifers, GET /aquifers/names/ returns just the names and IDs for lightweight pickers, and GET /aquifers/{aquifer_id}/ returns a single aquifer's full record.

What are the rate limits for the BC GWELLS API?

Specific rate limits are not declared in the OpenAPI spec. The service is hosted on the BC Natural Resource Sector platform, so paginate large list calls and avoid issuing many parallel detail fetches against the aquifer endpoint.

How do I retrieve a single aquifer through Jentic?

Search Jentic for 'get a bc aquifer', load the GET /aquifers/{aquifer_id}/ operation, and execute with the aquifer_id path parameter. With pip install jentic the call returns the full aquifer record including its classification codes.

Does the GWELLS API include the meaning of aquifer classification codes?

Yes, indirectly. The aquifer detail endpoint returns code values, and the aquifer-codes endpoints (such as /aquifer-codes/materials/ and /aquifer-codes/vulnerability/) return the canonical code lists so applications can resolve each code to a human-readable label.

Can I limit what my agent is allowed to do with the BC GWELLS API?

Yes. Because you run Jentic One yourself, your own rules decide which GWELLS operations and credentials your agent may use, so you can allow only the read routes it needs, such as GET /aquifers/ or the /aquifer-codes/ lookup lists, and withhold everything else. Since the aquifer id lives in the URL path at GET /aquifers/{aquifer_id}/, you can pin the agent to a single aquifer for detail reads while the code lists stay read-only. Any operation you have not included is unreachable, and the JWT for protected calls is injected only at execution time and never exposed to the agent.

GET STARTED

Start building with Groundwater Wells, Aquifers and Registry API

Explore with Jentic One
View OpenAPI Document