The record of a water well, as data.
.well is an open JSON format for the whole record of a water well, from construction and lithology to pumping tests, operation, permits, water quality and history. These docs cover the format, its specification and the libraries that read, validate, analyze and draw it.
One file, one well, every stage of its life
A .well file starts as a drilling report and grows with the well: tests, permits, meters, analyses. Every field has one meaning and one unit, written down in a versioned specification.
Opens in any editor, parses in any language, diffs in git. Full field names, so a file reads without the spec.
Meters, millimeters, m³/h. The file never declares units, so two files of the same well hold the same numbers.
Unknown values are left out, never invented. A registry record with only its construction is a valid file.
TypeScript libraries, framework-free
The reference implementation of the format, published on npm under Apache 2.0. No UI framework required.
Docs your assistant can check against
Connect Claude, Cursor, VS Code or Gemini CLI to the docs MCP server. Your assistant searches the spec instead of guessing, and validates every .well file it writes with the same parseWell the libraries use.
claude mcp add --transport http welldot https://docs.welldot.org/mcp
# Tools your assistant gets:
# search_docs search the spec, guides and API docs
# get_page read any page as Markdown
# validate_well check a .well file, errors with paths