TitleMind.AI vs. the field — feature-by-feature breakdown
Updated March 2026 · Internal use only
What each platform actually does when you need to run title, verify ownership, or find money.
| Capability | TitleMind.AI | Tracts | Rowland.ai | Enverus Instant Analyst | Energy Domain |
|---|---|---|---|---|---|
| Primary Function | Full-stack AI title platform End-to-end: prospecting → title → GIS → monetization | Cloud title management — digital runsheets, flowcharts, ownership reports | AI document processing — classification, extraction, structured data output | AI document summarization layered onto Courthouse digital records | Mineral marketplace + data subscriptions (rig/permit/production alerts) |
| AI Title Examination | ★ Full chain-of-title AI Sovereignty-to-present, heirship computation, fractional interest calc, graph-based link tracing |
✗ No AI Manual data entry into electronic note cards; algorithm recalculates math only after human input |
◐ Document-level AI Classifies & extracts fields from individual docs; no chain assembly or interest computation |
◐ Summarization AI Reads/summarizes individual docs (deeds, leases, handwritten conveyances); no chain-of-title build |
✗ No title AI Marketplace + data; no document analysis or title work |
| Automated Runsheet Generation | ✓ Automated AI-generated mineral runsheets with fractional ownership from parsed deed chains |
◐ Semi-auto Runsheet updates after manual entry — "zero math" recalculation but human-driven input |
✗ No Extracts structured data; doesn't produce runsheets |
✗ No Summaries attach to individual records; no runsheet output |
✗ No |
| Heirship & Probate Analysis | ★ Automated pipeline Dense Heirship: PDF ingestion → entity extraction → state-specific descent rules → fractional allocation with confidence scoring |
✗ No Manual; landman interprets and enters |
✗ No May extract party names but no genealogical reasoning |
✗ No | ✗ No |
| Mineral Severance Tracking | ✓ Yes Reservation clause detection, surface/mineral split tracking through entire chain, mineral consolidation timeline |
◐ Manual User must identify and enter reservation language |
◐ Extraction only Can pull clause text; no chain-level tracking |
◐ Summarizes Flags restrictions/reservations in document summaries |
✗ No |
| Graph Knowledge Base | ★ Neo4j AuraDB Person → Document → Parcel nodes; relationship edges (CHILD, SPOUSE, GRANTED_FROM); queryable graph for chain traversal |
✗ No Relational database; flowchart visual only |
✗ No | ✗ No | ✗ No |
Where each platform gets its data, and how far it reaches.
| Data Dimension | TitleMind.AI | Tracts | Rowland.ai | Enverus Instant Analyst | Energy Domain |
|---|---|---|---|---|---|
| County Clerk Records | ✓ 47 TX counties via PublicSearch.us direct integration + scraper worker for doc images (7 counties live, expandable) | ✗ None No native courthouse integration — user manually enters data from external sources |
✗ None User uploads docs; no courthouse connectivity |
★ 150+ counties Courthouse product: 140 TX counties + NM; 350M+ records; sovereignty-depth in 29 counties |
◐ Via Clerk Records acq. Acquired ClerkRecords.com (Aug 2025); AI-enhanced courthouse data in development |
| RRC / State Commission | ★ Live API integration GIS Layer 1 (wells) + Layer 24 (surveys); spatial queries; automated HBP/shut-in/cessation analysis |
✗ No | ✗ No | ◐ Via Enverus data Production data in broader Enverus suite, but not in Instant Analyst product itself |
✓ Yes Rig, permit, production, completion data by basin/county subscription |
| NM Coverage (EMNRD / IPRA) | ★ Exclusive dataset IPRA full unclaimed property DB (1.2M records, 37K mineral, $4.15M value); EMNRD API (594 Oxy wells + production history); NMOCD GIS endpoints |
✗ No | ✗ No | ◐ NM courthouse Some NM county records in Courthouse |
◐ NM data Permian Basin subscriptions include NM Lea/Eddy |
| GLO / Patent Records | ✓ Integrated Land Grant Database lookup; pre-1895 patent = full mineral estate rule automated |
✗ No | ✗ No | ◐ In sovereignty records Historical records go to patent in some counties |
✗ No |
| Unclaimed Property / UCR | ★ Only platform with this TX ClaimItTexas integration + NM IPRA full database; mineral-type filtering; operator-lineage matching (Oxy/Anadarko/Kerr-McGee) |
✗ No | ✗ No | ✗ No | ✗ No |
| GIS / Spatial | ★ Full stack Vara GIS (MapLibre + D1 + MVT tiles); survey polygons; metes-and-bounds computation; timeline playback; satellite alignment verification |
◐ Basic "Elementary" mapping per user reviews; T&R only, not M&B |
✗ No GIS | ◐ Enverus maps GIS in broader Enverus suite; not in Instant Analyst |
✓ Good Mapping integrated with well/permit/production overlay in Data product |
What's under the hood matters when you're processing millions of records at scale.
| Technology | TitleMind.AI | Tracts | Rowland.ai | Enverus Instant Analyst | Energy Domain |
|---|---|---|---|---|---|
| Architecture | Edge-native Cloudflare Workers + D1 + R2 + KV; sub-50ms global latency; zero cold starts |
Cloud SaaS (traditional); Houston-based | Cloud API + SDK; enterprise deployment options | Monolith SaaS layered on Enverus Courthouse infrastructure | Cloud SaaS; Fort Worth-based |
| AI Model | Claude (Anthropic) — Opus/Sonnet/Haiku tiered; domain-tuned prompts + graph reasoning; Dense Heirship pipeline with state-specific legal rules | None — algorithm-based math recalculation only | Proprietary LLM fine-tuned for land documents; V2 "intelligent classification" | Proprietary GenAI trained on 100+ years of courthouse data; document summarization focus | AI via Clerk Records acquisition; implementation TBD |
| API / Developer Access | ✓ Full REST APIs (DataTree, RRC, EMNRD, OTLS, Vara); Workers endpoints; MCP tools for agent workflows |
✗ No public API | ✓ Yes Documents API, enterprise SDKs (Python, TypeScript, Go) |
✗ No Locked to Enverus Courthouse UI |
◐ Limited Data subscriptions; no programmatic access to marketplace |
| Document Image Retrieval | ✓ Automated PublicSearch scraper Worker → R2 storage; ~37s fresh, ~1s cached; multi-page capture with HMAC sig handling |
✗ No User manually accesses courthouse |
◐ Upload only User provides documents |
✓ Yes Courthouse product includes PDF viewing/printing of scanned records |
◐ In development |
| Multi-State Legal Rules | ✓ TX + NM live TX race-notice, homestead, idem sonans, mineral/royalty distinction, VLB rules; NM mineral owner type (Federal/State/Private) via EMNRD |
◐ TX focused No automated legal rule application |
◐ General "Industry-specific terminology" but no state-specific legal engine |
◐ TX + NM data Coverage in both states but no automated legal analysis |
✗ No |
The point of title work is finding money. Who actually helps you get paid?
| Revenue Path | TitleMind.AI | Tracts | Rowland.ai | Enverus Instant Analyst | Energy Domain |
|---|---|---|---|---|---|
| Unclaimed Royalty Recovery | ★ Core workflow 6-phase pipeline: prospect → verify → research → chain → map → monetize. Only platform that connects ClaimItTexas/IPRA hits to verified mineral chains. |
✗ No | ✗ No | ✗ No | ✗ No |
| Open Mineral Identification | ✓ Automated RRC well status + production history → lease expiry detection; shut-in/cessation risk scoring; re-lease opportunity flagging |
✗ No | ✗ No | ✗ No Could manually research, but no automated detection |
◐ Indirect Production data could support manual analysis |
| Mineral Acquisition Support | ✓ Yes Fractionated heir identification → consolidation opportunities; graph reveals ownership fragmentation across generations |
◐ Partial Ownership reports show current state but no acquisition intelligence |
✗ No | ✗ No | ✓ Marketplace 6,000+ verified buyers/sellers; auction/sealed bid; 30-day close average |
| Operator Lineage Tracking | ★ Deep genealogy OXY USA → Plains Marketing → Kerr-McGee → Anadarko → Oxy full lineage mapped; catches orphaned royalties across M&A chains |
✗ No | ✗ No | ◐ Some Historical data exists but no automated lineage logic |
✗ No |
Who they are, what they charge, and where they're headed.
| Dimension | TitleMind.AI | Tracts | Rowland.ai | Enverus Instant Analyst | Energy Domain |
|---|---|---|---|---|---|
| Founded / Stage | 2025 · Revenue-generating · Solo founder | ~2017 · Houston · Series A (Crunchbase) | ~2024 · V2 launched Aug 2025 · Energy Council "Disruptive Tech of Year" 2025 | Enverus subsidiary · $4B+ valuation · Courthouse product since ~2012; IA added May 2025 | ~2021 · Fort Worth · Acquired Clerk Records Aug 2025 |
| Pricing Model | SaaS subscription Per-seat or enterprise; title-as-a-service model |
SaaS subscription (pricing not public; per-seat) | API usage-based + enterprise seats (pricing not public) | Enterprise contract Add-on to Courthouse subscription; opaque pricing; long sales cycles |
Flexible geo-sub By basin or county; monthly/annual; marketplace listing fees; transparent pricing |
| Target Customer | E&P operators, mineral aggregators, royalty companies, title attorneys, acquisition teams | E&P land departments, brokers, field landmen, title attorneys | Land professionals, right-of-way teams, energy companies needing document processing at scale | Title researchers already on Enverus Courthouse; large E&P and land service companies | Mineral buyers/sellers, small-to-mid operators, individual mineral owners, data subscribers |
| Biggest Strength | Only platform connecting title intelligence to revenue generation (UCR, open minerals, acquisition) | Established brand in E&P land departments; runsheet workflow is familiar to landmen | Clean developer experience; enterprise SDKs; fast document classification | Unmatched courthouse record volume (350M+ docs, 150+ counties); backed by Enverus data moat | Marketplace liquidity (6,000+ users); transparent pricing; Energy Domain Data growing fast |
| Biggest Weakness | Newer entrant; county scraper coverage expanding (7 of 47 counties automated) | No AI; manual data entry; harsh user reviews ("outdated code", "rushed title opinions", "takes longer than traditional methods") | No courthouse data; no chain-of-title assembly; no GIS; no revenue pipeline — pure document processing middleware | Locked ecosystem; no API; no programmatic access; summarizes docs but doesn't build chains or compute ownership; enterprise pricing gates out smaller shops | No title work at all; marketplace-only; Clerk Records AI integration TBD; no chain-of-title capability |
Where each player sits relative to TitleMind and what to watch for.