Property data and intelligence, on tap.

API access to the same canonical record of every property, owner, and transaction that powers Tortus — deeds, mortgages, AVM, ownership, and distress signals, normalized and ready to query.

44Endpoints
1Canonical record per property
REST + MCPAccess
The challenge

Property data is scattered across a dozen vendors.

Teams stitch together deeds, tax, valuations, and ownership from separate feeds — each with its own schema, refresh cadence, and gaps. Reconciling them into one trustworthy record is the hard part.

Fragmented sources

Deeds from one vendor, AVM from another, ownership from a third — none of them agree on keys or formats.

Stale and incomplete

Feeds lag the public record by weeks, and coverage drops off outside the markets a vendor cares about.

No single identity

Without one canonical property and owner identity, joining the data is a project of its own.

What you get

One canonical record, every way you want to reach it.

The same normalized data spine behind Tortus, exposed through a clean API, typed SDKs, an MCP server, and webhooks.

REST API

Query properties, owners, deeds, mortgages, AVM, distress, and markets through one consistent, versioned API.

  • 44 endpoints across properties, AVM, deeds, distress, owners, markets, and webhooks
  • One canonical property and owner identity to join on
  • Credit-based metering with transparent usage

Tortus REST API endpoint reference

Typed SDKs

A TypeScript SDK with complete type definitions for every request and response, so integration is autocomplete the whole way.

  • Full request/response types for all endpoints
  • First-class errors and pagination helpers
  • Drop-in client with sensible defaults

Tortus TypeScript SDK code sample

MCP server & webhooks

Bring the property record straight into your AI agents over MCP, and subscribe to changes with webhooks.

  • MCP server so agents can query the record as a tool
  • Webhooks for new deeds, ownership changes, and distress signals
  • Changelog and stable, versioned contracts

Tortus MCP server and webhook configuration

44
API endpoints
1
Canonical record per property
REST + MCP
Ways to integrate
Webhooks
Real-time change feeds

Build on the property record.

Talk to the team about API access, coverage, and pricing for your use case.