VALORDB
pip install valordb v0.5.0 · on PyPI macOS · Linux · Windows Sovereign · local-first AI

VALORDB, in your terminal.

A sovereign, grounded CLI + Python client over every published Board of Veterans' Appeals decision (1992–present, ~1.86M), wired to Title 38 (38 U.S.C. + 38 CFR). Ask corpus-locked questions, pull outcome rates, and read the law — without leaving the shell. The grounded analyst runs on your Ollama; nothing leaves your machine.

$ pip install valordb && valordb

Why it's different

The model is never the source of a fact.

Most "AI for veterans" tools let a language model invent numbers and citations. VALORDB inverts that: statistics are computed by the corpus and locked, citations are checked against the real Title 38 store, and inference is yours to run.

Corpus-locked statistics

Every rate is computed by querying the actual corpus and injected as a locked VERIFIED_FACTS block. Any number the model emits that isn't traceable to that block is struck after generation — it cannot pass off a guess as data.

Verified citations

Every 38 U.S.C. / 38 CFR citation the model emits is resolved against the ingested Title 38 store. Citations that don't resolve are flagged — so you never chase a phantom regulation.

Sovereign by default

The grounded ask runs entirely on your own Ollama (localhost or LAN). Your question and the corpus context never leave your machine — no third-party AI provider sees a thing.

In practice

What it looks like in a terminal.

Four moves cover most of it: install, ask a grounded question, pull the headline rates, and read the controlling law. Each block below is a representative valordb session — the exact commands you'll run and the shape of the output (figures shown are illustrative).

① Install & launch

zsh — valordb
$ pip install valordb
Successfully installed valordb-0.5.0
$ valordb

  __   ____  _    ___  ____  ____  ____
 / / / / _ |/ /  / _ \/ __ \/ __ \/ __ )
 \ \/ / __ / /__/ // / /_/ / /_/ / /_/ /
  \__/_/ |_\___/____/_____/_____/_____/
  VALORDB CLI — valordb.org

Type a command, or `help`. `quit` to exit.
valordb> _

First run: the install line, then the VALORDB CLI banner.

② Ask a grounded question

valordb — interactive
valordb> ask PTSD and sleep apnea claimed together, under Title 38
# grounding on local Ollama · corpus-locked stats injected…

When obstructive sleep apnea is claimed secondary to service-connected
PTSD, the Board's any-grant rate for the sleep-apnea issue is 37.1%
(N=12,480), versus 29.3% corpus-wide. Secondary service
connection turns on a medical nexus under 38 CFR 3.310 ✓ verified.

Sources: VERIFIED_FACTS (corpus) · 38 CFR 3.310 · 38 U.S.C. 1110
valordb> _

A grounded answer — every figure traced to the corpus, every citation verified.

③ Pull the numbers

④ Read the controlling law — free

zsh — valordb law
$ valordb law cfr-38-3.310
38 CFR § 3.310 — Disabilities that are proximately due to,
or aggravated by, service-connected disease or injury.

  (a) General. …a disability which is proximately due to or
  the result of a service-connected disease or injury shall be
  service connected.…

# reading the law is FREE — no key required
$ _

Verbatim Title 38 — reading the law is free, no key required.

Quick start

Three ways to drive it.

Run it as an interactive REPL, fire one-shot scriptable commands, or import the Python client. Install once: pip install valordb.

Interactive REPL

Run valordb with no arguments. You get an ASCII-art banner and a valordb> prompt.

$ valordb
# then, at the valordb> prompt:
valordb> ask PTSD and sleep apnea claimed together, under Title 38
valordb> conditions sleep apnea
valordb> law usc-38-1110
valordb> upgrade

One-shot / scriptable

Every command works as a single shell invocation — pipe --json output straight into jq.

$ valordb ask "overview of Sleep Apnea + PTSD claims" --mode attorney
$ valordb kpi --json | jq .rates
$ valordb conditions "sleep apnea"
$ valordb dimension judge
$ valordb law cfr-38-3.310
$ valordb search tinnitus

Python library

Import the client for notebooks, pipelines, and apps. Optional HTTP extra: pip install valordb[httpx].

from valordb import VALORDB

db = VALORDB(api_key="vk_firm_…")
db.kpi()["rates"]
db.conditions().rate("sleep apnea")
db.conditions().together("PTSD", "sleep apnea")
db.law("usc-38-1110")["heading"]

Reference

Commands.

Reading Title 38, M21, and CAVC is free. Grounded AI, analytics, search, and the API/CLI are paid (Firm+).

CommandWhat it does
ask <q> [--mode veteran|attorney]Grounded analyst on your local Ollama — corpus-locked stats, verified citations.
kpiHeadline outcome rates (any-grant / grant / remand / deny). --json for scripting.
conditions [name]Per-condition any-grant + N, AMA-vs-Legacy split, co-occurrence.
dimension <dim>Breakdown by judge, regional_office, condition, rep_type, …
law <id>A Title 38 section, verbatim. FREE (e.g. usc-38-1110, cfr-38-3.310)
m21 <id>An M21 manual section. FREE (sub-regulatory; partial mirror)
search <q>Search Title 38 + M21 + CAVC by keyword / citation. FREE (full-text + layman synonyms; decision-corpus search is Firm+)
setupGuided local-AI install — offers to install Ollama + pull a tiny model.
configConfigure the AI engine — Ollama (localhost/LAN), BYOK cloud, or Claude Code CLI.
infoYour key: tier + quota.
key / login / logoutShow / set / paste / remove your license key.
upgradeSubscribe / upgrade — purchase through the CLI (Firm+ for the API). FIRM+
site / help / quitOpen the site · reference · exit.

Access

Free to read the law. The CLI + API ship with Firm.

The Title 38 + M21 + CAVC law is free to read — no key. Analytics, search, grounded AI, and the API/CLI are paid. valordb upgrade runs a Paddle checkout right in the terminal and saves your key.

TierPriceWhat you get
VeteranFreeRead the complete Title 38 + M21 + CAVC (no key).
Professional$49/moWeb analytics dashboard + Attorney-grade AI.
Firm$149/moREST API + this CLI + bulk export + team (5 seats).
Enterprise$499/moFull API + white-label + SLA + sovereign on-site appliance.

Veterans & non-profits — contact us about custom arrangements: joseph@resilientmindai.com. See the full pricing page.

Configuration

Env var → config file. Keys never logged.

Precedence: an environment variable wins, otherwise ~/.valordb/config.toml. Your license key is stored at that path (chmod 600) and is never logged.

SettingEnv varconfig.tomlDefault
License keyVALORDB_API_KEY[auth] api_key
API baseVALORDB_URLhttps://valordb.org
Ollama hostVALORDB_OLLAMA / OLLAMA_HOST[ai] ollama_hosthttp://localhost:11434
Ollama modelVALORDB_MODEL[ai] modelfirst installed
# ~/.valordb/config.toml
[auth]
api_key = "vk_firm_…"

[ai]
ollama_host = "http://localhost:11434"
model = "llama3.2:3b"

Sovereignty & privacy

Your data does not have to leave the box.

The grounded ask runs entirely on your Ollama (localhost or LAN). Your question and the corpus context never leave your machine — no third-party AI provider is involved. Run valordb setup to install Ollama and pull a tiny model in one guided step.

Local-first inference

Point the CLI at your own Ollama with VALORDB_OLLAMA or [ai] ollama_host. Cloud/BYOK is an opt-in convenience — local is the default, and the privileged path.

Keys stay on disk

Your license key lives in ~/.valordb/config.toml at chmod 600 and is never written to logs. Reading the law needs no key at all.

Optional HTTP extra

Install the faster transport when you want it: pip install valordb[httpx]. Everything else works with the standard library.

Legal information, not legal advice. VALORDB surfaces public decisions, statutes, and regulations — and how the Board has historically ruled — but is not a law firm, does not provide legal advice, and is not a substitute for an accredited Veterans Service Officer, claims agent, or attorney. VA claims carry hard deadlines and one-shot effective-date consequences. Verify everything against controlling law (va.gov/ogc) and an accredited representative. Per-judge / per-office rates reflect docket and case mix, not adjudicator favorability. See the Terms and Privacy Policy.