Skip to content
LegiScore logo

LegiScore

Generates property title risk scores and legal due diligence reports for lenders by analyzing government records and court databases.

LegalAPIAnalyticsData extraction
legiscore.in ↗WikidataInstagramFacebookXProduct HuntLaunched on Product Hunt · 2026-04-12
At a glanceswept 2026-09-19
Price
Price not read
Use
Emerging≈ 64 visits a month · estimate, 2026-09
Activity
Actively maintainednothing dated on the site
Company
founding year not on record
Runs as
API
Alternatives in Legalby use, among tools still maintained
  • EvisortManages contract data and provides contract intelligence for legal operations.

    Established

    ≈ 210 visits/mo
  • NC DataSearches company registries and documents to extract evidence, screen sanctions, and produce due diligence reports with analyst oversight.

    EmergingActively maintained

    ≈ 1 visits/mo
  • QubeSearches patent databases and analyzes intellectual property landscapes using semantic search and visualization tools.

    Emerging

    ≈ 1 visits/mo
  • IroncladManages contract lifecycle from creation through execution and analysis with AI-assisted review and negotiation.

    Widely used

    ≈ 131k visits/mo
  • LawGeexAutomatically reviews and redlines contracts according to company policies using machine learning.

    Established

    ≈ 170 visits/mo
  • Speed.aiMonitors legal intake calls to identify lost cases, flag missed leads, and coach staff on conversion improvements.

    EmergingActively maintained

    ≈ 438 visits/mo

All Legal tools →

Questions this page answers
  • What is LegiScore?

    Generates property title risk scores and legal due diligence reports for lenders by analyzing government records and court databases.

  • Do people use LegiScore?

    Emerging: ≈ 64 visits a month · estimate, 2026-09.

  • Is LegiScore still maintained?

    Actively maintained.

  • What are alternatives to LegiScore?

    In Legal, by use: Evisort, NC Data, Qube, Ironclad, LawGeex, Speed.ai.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one row at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.