how we compare

How TierraLens compares

We like our competitors. Here's where we're different, where we're not, and when you should pick them instead.

Transect is the category leader for renewable-siting due-diligence reports, with strong coverage of species, wetlands, and transmission — the same analysts they serve are our users' colleagues. Urbint is the leader for utility operational risk — dig-ins, storms, and wildfire on existing infrastructure — which is a different problem from pre-development screening.

There is also a long tail of GIS consultancies and ArcGIS-based workflows, plus adjacent environmental-data platforms, that deliver custom maps and memos per engagement. We respect all of them. This page is about when the API-first shape we've chosen matters, and when it doesn't.

At a glance

one row per company
CompanyPrimary outputPricingStrongest atWeakest atWhen to pick
TransectOnline due-diligence report (viewer + PDF export)Enterprise seats; free mini-report on KML uploadRenewable-siting breadth; species, wetlands (Ghost Waters), transmission; published case studies with developersReport-first workflow — limited public evidence of a self-serve developer APIYou need a polished, buildable-area report for a siting team and don't need programmatic access.
UrbintSaaS dashboard + risk scores + alerts (Urbint Lens)Enterprise contractsOperational resilience for utilities — 811 dig-in risk, storm / wildfire impact prediction (StormImpact acquisition)Not built for pre-development parcel screening or land-use regulation depthYou're a utility protecting existing infrastructure from dig-ins, storms, or wildfire.
GIS consultancies & ArcGIS workflowsCustom maps, shapefiles, memo PDFs from an in-house teamPer-seat software + analyst hoursTotal flexibility; anything you can draw on a map, you can analyseNo turnkey regulatory intelligence — you bring the statute knowledgeYou already have GIS analysts and prefer bespoke layers over opinionated regulatory data.
TierraLensStructured JSON API + MCP server (no PDF required)$35 / report · cost + 15% for volume API accessRegulation-as-data; typed Regulation objects with statute + agency-portal citations; 2 states deep (TX, NY)Not all 50 states yet; no community-sentiment / moratorium layer yetYou're building a product, underwriting at volume, or wiring regulations into an agent.

Claims about Transect and Urbint are drawn from their public marketing and press as of April 2026. If we got something wrong, email us and we'll fix it.

Dimension by dimension

Output

Report-first incumbents
A report — PDF, or a web viewer that exports to PDF. Designed to be attached to a memo.
TierraLens
JSON. Every regulation, citation, and timeline is a field you can read, diff, or join against your own data.

Report shapes workflows: email → DMS → copy-paste. JSON shapes workflows: request → render → decide.

Latency

Report-first incumbents
Minutes per parcel, sometimes with staff review before delivery.
TierraLens
Under 3 seconds per parcel, programmatic, idempotent.

Pricing

Report-first incumbents
Enterprise seats, annual commits, usage minimums.
TierraLens
$35 per report, or cost + 15% margin for API volume. No seat tax.

Citations

Report-first incumbents
Paraphrased regulatory narrative written by analysts; the statute is implied, not linked.
TierraLens
Every rule carries the statute code, rule number, and agency-portal URL. Citations are first-class fields.

State depth

Report-first incumbents
Nationwide breadth — every state at roughly the same (shallow) resolution.
TierraLens
Two states deep today (Texas, New York). California, Florida, and Colorado on the roadmap for Q3.

If you need Oklahoma tomorrow, buy Transect. If you need Texas at the rule level, buy us.

Integration

Report-first incumbents
Email delivery → upload to a document management system → copy into memo.
TierraLens
curl, MCP server, webhooks. Wired directly into your stack or your agent.

AI-native

Report-first incumbents
Marketing copy mentions AI — usually internal classification or ML risk scoring.
TierraLens
A real MCP server endpoint. Claude, Cursor, and agent frameworks can call us as a tool.

What “regulation-as-data” actually looks like

The difference between a report and an API is this TypeScript interface. Every rule we return — state, federal, county — hydrates these fields, with a statute or agency-portal URL in source_url. You can filter, diff, and join it like any other row in your warehouse.

interface Regulation {
  code: string;
  title: string;
  summary: string;
  authority: string;
  citation: string;
  triggered_by: string;
  permit_path?: string;
  risk?: "low" | "medium" | "high";
  source_url?: string;
  typical_cost?: string;
  typical_timeline?: string;
}

Source: /docs · see also /texas and /new-york for live payloads.

When you should not pick TierraLens

A short list is more useful than a long one. If any of these sound like you, we're probably not the right tool today.

If you've made it this far, we probably built this for you.

Regulation-as-data, per-parcel in under three seconds, with statute URLs attached. Texas and New York today; more states shipping through 2026.