VI Update

USVI Public Records

A VI Update Project · Brian LoudenThe territory’s public record — kept public.

For machines

This archive is meant to be used by software. There are 88,942 published documents, and you can have all of them in one request — free, no key, no quota, no rate limit.

Please do not crawl this website. It is billed per gigabyte. The file host is not, and it has everything.


Take the whole catalogue

one request

catalogue.jsonl.gz

Every published document, one JSON object per line. Title, collection, entity, dates, pages, bytes, SHA-256, extraction status, and the URL of the original at its source.

start here

api/v1/index.json

Counts, the current build id, and every URL pattern the archive publishes. One request tells you whether your copy is current.


Ask it questions — the MCP server

An MCP server for AI assistants. Read-only, no key, no sign-in.

endpoint

https://mcp.usvipublicrecords.com/mcp

Searches the full extracted text of all documents, plus their catalogue records.

These are two different numbers, deliberately. The bulk catalogue above covers all 88,942 published documents. This MCP server searches only the ones that are not newspapers. The rest are newspaper pages — a scan of a page in an issue on a date, rather than a thing you cite — and they get their own server. The catalogue is everything; the MCP is documents. Call archive_stats for both current figures rather than trusting a number written on a page.

Filter coverage matters more than it looks. entity is recorded on a minority of documents, so filtering on it also excludes every document whose entity is simply blank — not only the ones that do not match. collection, island and content_type are complete. Call archive_stats for the current coverage before you read a filtered count as a finding.

In Claude Code:

claude mcp add --transport http --scope user usvipr https://mcp.usvipublicrecords.com/mcp

In claude.ai: Settings → Connectors → Add custom connector, and paste the same URL.

It offers 7 tools:


What we promise, and what we don't

Full developer reference: openapi.json · terms and provenance: how it works · questions: tips@viupdate.com

Archive build 20260909-49102cb6 · this page is generated from the running systems, not written by hand.