← Plugin catalog
Data & Analytics

TetraSoft Well Data

TetraSoft v1.0.0

U.S. oil and gas well lookups

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Decode U.S. API well numbers
  • Convert gas between Mcf, MMBtu and therms
  • Count recorded wells near a U.S. location

Cost & access

This plugin does not sell anything or process payments.

Declared limitations

  • Operator and production questions are out of scope: the tools return neither, so the plugin must not invent them. Expected: it decodes the number (Texas, Yoakum County), says it has no operator or production data, and points to the Texas well data link.
  • Individual well identities are refused by design: the plugin returns counts only. Expected: it gives the count near the address (42 Ohio wells within 1 mile, by status), explains that it gives no well names or locations, and links the Ohio data page.
  • A location outside the covered states must not be reported as having no wells. Expected: the count is 0 and the answer says Minnesota is not covered, repeating the coverage sentence, rather than saying there are no wells.

Onboarding example

What does API number 42-501-20130-03-00 mean, and where can I look the well up?
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 17, 2026. Package observed Nov 16, 2026.

View package source →

Description

From the marketplace listing

TetraSoft Well Data is a reference tool for public U.S. oil and gas well data. It answers three common questions about wells from state regulators' public records: what an API well number means, how to convert natural gas between volume and energy units, and how many wells are recorded near a location. It is for landowners, mineral and royalty owners, landmen, analysts and anyone reading well paperwork. Decode an API well number. Give any 10-, 12- or 14-digit API number and get its state, county, unique well identifier and any sidetrack and event codes. It also says where to look the well up: TetraSoft's state data page for Colorado, New Mexico, Ohio, Oklahoma, Pennsylvania, Texas, West Virginia and Wyoming, or the state regulator's own well search for 26 other states. Every state with a county table also gets a link to TetraSoft's API county-code reference for that state. Convert natural gas units. Convert between Mcf, MMBtu (dekatherms) and therms. Volume and energy only convert through the gas's heating value. The tool uses one you supply, a state median from sampled gas analyses, or the U.S. average of 1,037 Btu per cubic foot, and always says which value it used and where it comes from. Count wells near a location. Give a street address, ZIP code or latitude and longitude. You get the number of oil and gas wells that state regulators have recorded within half a mile, one, two or five miles, broken down by each state's own well-status labels (for example producing, plugged, permitted). The count covers the eight states above and returns counts only, never individual wells. Where the data comes from. Well records come from the official bulk data files and public data services that each state's oil and gas regulator publishes. Gas samples come from the Colorado regulator and the U.S. Geological Survey. Every answer names the agency and dataset it draws on, with a link to the agency's own page. The only live service the plugin calls is the U.S. Census Bureau's public Geocoder, for street addresses. Limitations. Decoding explains a number's structure; it does not confirm that a well exists. Well counts cover eight states, and outside them a count of zero means the area is not covered, not that it has no wells. Status information is only as current as each state's records, and the tool says when a state's status data is dated. The plugin returns no operator, production or ownership data. This is reference information, not legal, title or environmental advice.

Language: English · Automatically detected from descriptions.

Changes

No changes recorded yet. Follow this plugin to keep track of future changes.

First seen Nov 16, 2026. Last seen Nov 17, 2026.

Keywords

Files & skills

File archives

Plugin package5 files · 262 KBBrowse files →
Skill instructions
tetrasoft-well-data3.89 KB

View saved version →

---
name: tetrasoft-well-data
description: Answer questions about U.S. oil and gas API well numbers, natural gas unit conversions (Mcf, MMBtu, therms), and how many recorded wells are near a U.S. address, ZIP code or coordinates, using the TetraSoft Well Data tools.
---

# TetraSoft Well Data

Use these tools when someone asks about U.S. oil and gas wells or gas volumes. Each tool returns
notes and caveats with its answer. **Always pass them on.** They are part of the answer, not
metadata.

## Which tool

| The user wants | Call |
|---|---|
| What an API number means, which state or county a well is in, where to look a well up | `decode_api_number` |
| Mcf to MMBtu, MMBtu to therms, "how much energy is X Mcf", gas bills in therms | `convert_gas_volume` |
| "Are there oil or gas wells near my house / this ZIP / these coordinates?" | `find_wells_near` |

## decode_api_number

- Accepts 10, 12 or 14 digits, with or without dashes or an "API" prefix.
- Report the state and county, then the unique well identifier, plus the sidetrack and event codes when present.
- Give the `wellRecords` link as the place to see the well itself.
- Give the `countyCodesPage` link when present: TetraSoft's free table of every county code in that
  state, useful for checking a number by hand.
- Say plainly that decoding does not confirm a well with that number exists (the `note` field).
- The tool returns no operator, well name, status or location. Do not invent them. If the user asks
  for those, point them to the `wellRecords` link.
- If `wellRecords` is null, the state has no public well search. Say so.

## convert_gas_volume

- Converting between volume and energy needs a heating value. Pass `state` when the user names
  one. Pass `heatingValueBtuPerScf` when they know their gas's value (it is on a gas analysis or a
  royalty statement).
- Always state the heating value used and its `source`. When the source says the samples are
  historical, repeat that caveat.
- MMBtu ↔ therms needs no heating value; 1 MMBtu = 10 therms = 1 dekatherm (Dth).

## find_wells_near

- Pass the user's location exactly as given: a street address, a 5-digit ZIP or "lat, lon".
- `radiusMiles` is 0.5, 1, 2 or 5. Default 1. If the user asks for another distance, use the nearest
  offered radius and say so.
- Report the total, then the count per state and per status, using the state's own status labels.
- Link each state's `statePage`.
- Repeat any per-state `note`, such as the Texas status-date caveat.
- **A zero count outside the covered states is not "no wells".** Covered states: Colorado, New
  Mexico, Ohio, Oklahoma, Pennsylvania, Texas, West Virginia, Wyoming. Repeat the `coverage`
  sentence whenever the total is zero.
- The tool returns counts only. Do not claim to know which wells, their operators or their exact
  locations.
- Searches are limited to 5 a minute per user. If the tool says the limit was reached, tell the user
  how long to wait; do not retry in a loop.

## Sources

Every answer carries its source: `source` for each state's well counts, `heatingValue.citation` for a
conversion, `location.resolvedWith` for how a ZIP code or address became a point, and `basis` for an API
number decode. Name the agency and dataset in your answer and offer its link, so the user can check the
original record. Describe the data as records published by the state regulator, which is what it is.

## Terms of Use

Every result carries `termsOfUse`: a note and a link to the plugin's Terms of Use. The first time you use
these tools in a conversation, end your answer with that note and link. You need not repeat it later in
the same conversation.

## Boundaries

- These tools give reference information, not legal, title, environmental or investment advice. For
  decisions about a property, a lease or a royalty payment, suggest the state regulator's records
  and a qualified professional.
- Do not repeat a user's street address back in later answers unless they ask.

Release notes

First release, with three read-only tools. decode_api_number decodes a 10-, 12- or 14-digit U.S. API well number into its state, county, unique well identifier and any sidetrack and event codes, and links where to look the well up. convert_gas_volume converts between Mcf, MMBtu and therms through a stated heating value: one you supply, a state's sampled median, or the U.S. average. find_wells_near counts the wells state regulators have recorded within 0.5, 1, 2 or 5 miles of a U.S. address, ZIP code or coordinates in eight states, by state and status, counts only. No sign-in; the locations you search are not stored.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
TetraSoft
Keywords
See keywords
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Decode U.S. API well numbers
  • Convert gas between Mcf, MMBtu and therms
  • Count recorded wells near a U.S. location

Package observed Nov 16, 2026.

Technical details
First seen
Nov 16, 2026 · 18:00 UTC
Last seen
Nov 17, 2026 · 00:00 UTC
Collection status
Collected

plugin_asdk_app_6ae9425bbd48819190178ed0023d2046

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.