Skip to content
Get started

Open format v1.0Workbench appAgents over MCPImport and export adapters

The standard format
for title plants.

titlebase is the open format and the workbench for teams that build, convert and maintain title plants, across every system and format they come in.

Get startedAbout the format
  1. 01

    The format

    An open, versioned standard for exporting, creating and changing title plants. One file per plant.

    plant.titlebase
  2. 02

    Workbench app

    Native and GPU rendered. Views, an inspector and Activity, for plants of millions of documents.

    tbase open plant.titlebase
  3. 03

    Agents

    Agents do the work over MCP. The app updates live, and every change can be undone.

    tbase mcp
  4. 04

    Command line

    Headless, for scripts and batch runs. JSON out, and nothing ever prompts.

    tbase docs search --type WD
The titlebase workbench in the night theme. The Deeds view of a 291,021 document sample plant, filtered by type and addition, three rows selected, and the inspector showing one warranty deed with its parties, legal description and related documents.

01 Speed

Six million documents.
Twenty-five seconds.

We read every row of a 6.3 million document plant, parsed it and wrote it back with titlebase's own writers. Every row came back byte-identical. It took 25 seconds on one Mac Studio.

Documents in one file
6,298,723
File size
16GB
Every row rewritten
25.1s
Rows byte-identical
100%

Index it once. Search it in milliseconds.

titlebase builds a search index beside the plant, never inside it. On the same 6.3 million document plant, every indexed filter and sort we measured returned its first page in 42 ms or less.

Index 6.3M documents
79s
Indexed searches, first page
0.3to42ms
Whole plant by filed date, first page
0.3ms

Round trip on eight real plants

Release build, files opened read only. Plant names withheld.

PlantSizeDocumentsDocuments, to scaleRe-emitIdentical
Plant 1579 MB138,9451.4 s100%
Plant 2769 MB231,6982.4 s100%
Plant 3762 MB290,3811.8 s100%
Plant 41.4 GB291,0213.3 s100%
Plant 51.1 GB311,7832.5 s100%
Plant 61.6 GB695,0423.8 s100%
Plant 78.4 GB3,332,71314.2 s100%
Plant 816 GB6,298,72325.1 s100%

A second check writes a whole new file and compares every row and the schema. It came back identical on every plant it ran on.

Targets, met

Set on the 6.3M document plant before we wrote the code.

  • Build the search indexTarget under 2 min79 s
  • Any indexed filter or sort, first pageTarget under 100 ms42 ms worst
  • Unindexed sort, first pageTarget under 1 s232 ms

02 Agents

Agents do the work.
You watch it land.

Connect Claude, or any agent that speaks MCP, with one command. It searches, fills and fixes records while the app updates live. Every change is logged in Activity under the agent's name, and any edit or whole run can be undone.

The titlebase workbench in the day theme while Claude edits over MCP. A badge reads Claude is editing, 12 changes. Rows Claude just changed are tinted, the edited grantee cells are highlighted, and the inspector marks the grantee field as changed by Claude just now.
Live in the grid. Rows an agent changes light up as they land, and the inspector marks the exact field it edited.

  • Ask in plain words

    The agent works through the same commands the app uses. Every tool has a JSON Schema, so it knows exactly what to send.

  • Watch it happen

    With the plant open in titlebase, agents write through the app. You see each change in the grid and in Activity as it lands.

  • Undo anything

    Undo one edit, one document or a whole run. The plant file is untouched until you save or export a change batch.

Every change,
in one timeline.

Activity shows what changed, who changed it and how: an agent over MCP, a script on the CLI, or you in the grid. A running agent shows its progress and each edit it made. Stop it, undo a single edit or undo the whole run.

  • Filter by agents, CLI or you
  • Before and after for every field
  • Save, or export only the changes as a batch
The Activity panel beside the grid, which shows tinted grantee cells Claude just filled. Claude is running Fill missing grantees from deed text, 5 of 40 documents, with Stop and Undo Run buttons and each edit listed with its before and after. Below it, a CLI edit, an edit made in the grid, and an earlier finished Claude run.
Add titlebase to Claude Code
claude mcp add titlebase -- tbase mcp
# or bind it to one plant, so every tool knows the file
claude mcp add titlebase -- tbase mcp --file ~/plants/sample.titlebase

# then your agent calls tools. A real call and its result, trimmed:
→ docs_search {"instrument_type": "WD", "party": "DOE",
                "addition": "SAMPLE ADDITION 5", "limit": 3}
← {"indexed": true, "engine": "index",
   "documents": [
     {"id": 5, "instrument_number": "1994-001288", "instrument_type": "WD",
      "filed_date": "1994-11-02", "grantors": ["DOE, JANE"],
      "grantees": ["FIRST SAMPLE BANK"], "additions": ["SAMPLE ADDITION 5"]},
     ...
   ],
   "next_after_id": 80}

Read

10 tools
  • file_info
  • index_status
  • docs_get
  • docs_list
  • docs_search
  • docs_related
  • ac_list
  • lv_list
  • changes_list
  • check_roundtrip

Write, logged and undoable

16 tools
  • docs_create
  • docs_update
  • docs_delete
  • docs_image
  • ac_create
  • ac_update
  • ac_delete
  • lv_create
  • lv_update
  • lv_delete
  • changes_undo
  • changes_redo
  • changes_revert
  • changes_export
  • file_save
  • index_build

Plan and apply across a plant

4 tools
  • ops_plan
  • ops_apply
  • ops_undo
  • lv_from_plat

03 Workbench app

A native workbench
for very large plants.

Written in Rust on GPUI, the GPU rendered UI framework behind the Zed editor. No browser and no web view. It opens a plant of millions of documents in about a second and shows rows before the index is built.

The titlebase workbench in the day theme. The sidebar lists preset and saved views with counts: All, Deeds, No grantee, Recent filings, Lots missing, Deeds 2010 to 2026. The search bar holds filter tokens for type and addition, and the inspector shows the selected warranty deed.
Views, not queries. Preset and saved views in the sidebar, each with a live count. Filter tokens in the search bar narrow any view.
The titlebase start screen. The app icon and an Open a Plant button on the left with a drop zone. Recent plants and downloaded plant exports on the right, and a Connect an agent line with the MCP command at the bottom.

Open any plant.
Start working.

Open a .titlebase file or a plant export, or drop one on the window. Recent plants and downloaded exports are one click away, and an agent connects from the start screen with one command.

  • Views and filters

    Preset views like Deeds, No grantee and Recent filings, plus your own saved views. Search with filter tokens for type, party, addition, lot and block, dates and book and page. An optional SQL drawer is there for advanced work.

  • Documents grid

    Every column of a multi-million row plant, keyboard first. Sort, pin and hide columns. Multi-select and copy as TSV.

  • Inspector

    Every field, every legal description, parties and related documents with click through, plus the raw JSON.

  • Auto completes and land validations

    Browse and fix the plant's vocabulary and plat validations next to the documents that use them.

  • The source stays safe

    The file you open is never changed until you save. Edits are journaled beside it, and saving in place keeps a backup.

  • Day and night

    A calm light theme for long keying days and a dark one for late nights.

04 Import and export adapters

Plants in.
Plants out.

titlebase includes import and export adapters for PropertySync and a host of other industry standard formats. Bring a plant in from one system, clean it up, and send it out to another, all through one standard format.

Open plant exports as they are

A PropertySync plant export opens directly. Nothing to convert first.

Change batches

Save a clean, verified plant, or export a batch of only what changed: documents, auto completes, land validations, deletions and images.

Build new plants

Create an empty plant, inject records from a conversion source, and dump any table back to JSON.

Clerk index mapping

Map a clerk's index to the plant's own codes before records go in.

Snapshot compare

Compare two snapshots of the same plant, document by document.

PropertySync client

Sign in with your own account to download exports, look up live records and push batches.

05 The format

Open format.
Written down.

A titlebase file holds one whole title plant. The format is written down, versioned and open, so any team or tool can read and write it. Version 1 is PropertySync compatible: every PropertySync plant export opens as it is.

About the formatRead the spec v1.0
plant.titlebase
  • DocumentsEvery recorded instrument, field for field
  • PartiesGrantors and grantees, as recorded
  • Legal descriptionsBy standard type: subdivision, PLSS, abstract, acreage, parcel
  • Auto completesThe plant's vocabulary
  • Land validationsPlats, replats and vacates by addition
  • Change historyEvery edit journaled beside the file
  • One file per plant. Copy it, back it up, hand it over.
  • Byte faithful. An edited row looks exactly like the original. A row you did not touch is never rewritten.
  • Room to grow. Extensions live in reserved, optional tables. Indexes and the journal live beside the file.
  • Toolkits for developers. A Rust library reads and writes the format. The CLI and MCP server script it.

06 Mass updates and land validations

Change a whole plant.
Undo any run.

Start from any view or selection, or ask an agent. titlebase plans the change and shows counts and a before and after for sample documents. Apply runs in one transaction, and every run is logged in Activity, so you can undo it later.

Plan

Rename addition

"SAMPLE ADD 5" → "SAMPLE ADDITION 5"

Documents
141
Auto completes
0
Land validations
0
2019-007707addition "SAMPLE ADD 5"
addition "SAMPLE ADDITION 5"
2021-003318addition "SAMPLE ADD 5"
addition "SAMPLE ADDITION 5"
One transaction. Logged as run 15.Apply

  • Reindex and reformat

    Normalize case, spacing, dates and instrument number formats across every document.

  • Legal structure changes

    Move and restructure legals into standard types: subdivision, PLSS, abstract, acreage and more. Define your own with the legal builder.

  • Find and replace

    Rename a value, set or clear a field, or run a regex on any path. Split, merge and flatten parties.

  • Auto complete cleanup

    Merge, rename and dedupe vocabulary, and see every document a change touches.

  • Land validations from the plant

    Generate land validations from plat documents and the lot and block usage across an addition. Review, adjust, then apply.

  • Recipes

    Save a set of changes and run it again on the next snapshot of the same plant.

07 Command line

Every action,
from a script.

tbase runs headless. Every command takes the plant file first. Add--json and you get one JSON document on stdout and nothing else. Every edit is journaled beside the plant and can be undone. Nothing ever prompts.

CLI reference
  • tbase file infoSize, page size and row counts
  • tbase index buildBuild the sidecar search index
  • tbase docs searchInstrument, type, dates, parties, legals, book and page
  • tbase docs updateSet or remove any field, journaled
  • tbase ac, tbase lv
    Auto completes and land validations
  • tbase changes listEverything changed since you opened it
  • tbase undo, tbase redo
    By run or by operation
  • tbase saveA clean, verified plant file
  • tbase changes exportA change batch of only the changes
  • tbase check roundtripProve a byte-identical rewrite
tbase on a made-up sample plant. Real output.
tbase index build sample-county-tx.titlebase
built sample-county-tx.titlebase.tbase/index.db
  documents  2400 (88166/s)
  parties    4800
  legals     2400

tbase docs search sample-county-tx.titlebase --addition "SAMPLE ADDITION 5" --lot 4 \
    --sort filed_date --direction desc --limit 3 --count
   142  2026-000982    WD          727/573    2026-07-16  DOE, JANE -> GARCIA, ANA  [SAMPLE ADDITION 5]
   949  2026-001815    MTG        1004/361    2026-05-28  NGUYEN, KIM -> SMITH, ALEX  [SAMPLE ADDITION 5]
  1558  2022-000359    DT          519/010    2022-07-17  DOE, JANE -> SMITH, ALEX  [SAMPLE ADDITION 5]
3 documents
31 matches in all
(indexed: answered from the sidecar index sample-county-tx.titlebase.tbase/index.db)

tbase docs update sample-county-tx.titlebase 75 --set 'grantees.0.nameFirst=RICHARD A'
updated document 07e58eaf-5e22-04da-6941-01d32e8b3ec8 (row 75): /grantees/0/nameFirst
run 1, op 1
undo: tbase changes undo sample-county-tx.titlebase --run 1

tbase save sample-county-tx.titlebase --out sample-county-tx-edited.titlebase
saved sample-county-tx-edited.titlebase
  documents       2400 rows: 2399 unchanged, 1 updated, 0 deleted, 0 created
  landvalidations 4 rows: 4 unchanged, 0 updated, 0 deleted, 0 created
  autocompletes   11 rows: 11 unchanged, 0 updated, 0 deleted, 0 created
  verified        true

08 Release notes

What’s new,
every version.

Every release gets a note, newest first. Follow along by RSS or JSON feed.

Release notesRSSJSON feed
Release notes

Release notes appear here with each version.

Each note says what changed and what it means for your plants, in plain words. Subscribe to the feed to hear about every release.