Important property decisions are slowed down by fragmented records and hard-to-interpret legal signals.
PropOps
An open-source research agent that joins government property records into an inspectable diligence workflow.
At a glance
Nineteen agent workflows combine registry, RERA, and court data with entity resolution, risk checks, and batch evaluation.
The output keeps sources, gaps, and judgment visible instead of hiding them behind one score.
System sketch
Collect registration prices, project records, complaints, litigation, and listing context from public sources.
Resolve builder identities across legal entities, naming variants, contact details, directors, and addresses.
Flag missing records, conflicting claims, delayed projects, litigation, contract clauses, and financial stress.
Preserve the source trail and reserve outreach, negotiation, legal review, and purchase decisions for the buyer.
Design notes
A project-level lookup misses history when one builder operates through multiple legal entities and name variants.
Every summary is more useful when a buyer can inspect the records, limitations, and unresolved gaps behind it.
The agent gathers, compares, and drafts. The human controls outreach, legal review, negotiation, and purchase.
Question
Indian property records are public, but the useful evidence sits across registration portals, state RERA systems, court databases, builder entities, and listing sites.
PropOps turns that fragmented search into a repeatable research workflow while preserving the source trail and known limitations.
Approach
- Route a question through 19 modes covering discovery, evaluation, builder research, litigation, finance, agreement review, and post-purchase checks.
- Cross-reference IGRS, state RERA portals, the MoHUA aggregator, and eCourts using dedicated scrapers and fallbacks.
- Resolve related builder entities before aggregating project history, complaints, and litigation.
- Run batch evaluations with parallel agents while leaving high-impact actions with the buyer.
Open questions
- How can scraper failures and portal changes be detected before they create false confidence?
- Which evidence model makes missing and contradictory records easy to review?
- How far can entity resolution go before a probable match needs explicit human confirmation?