Gov Bc Ca Groundwater Wells, Aquifers and Registry API

Name: Groundwater Wells, Aquifers and Registry API
Brand: Groundwater Wells, Aquifers and Registry API
Availability: InStock

Browse all Gov Bc Ca APIs

✓ Official Vendor SpecData EnrichmentData TransformationapiKey24 Endpoints

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.

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 | sh

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 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

GET STARTED

Start building with Groundwater Wells, Aquifers and Registry API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

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.

Time to first call

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.