The identity and property data layer behind TruBase, available as an API.
Send whatever identifiers you have: a name, an email, a phone, a license or MLS ID. You get back the matched agent with a confidence score and an explicit list of which fields matched. Built for automated workflows that need to know when not to trust a match.
Most matching APIs return a match. This one tells you how much to believe it.
Every response carries a 0–100 score and the fields that produced it, with documented bands so you can wire the decision into a workflow instead of eyeballing results.
Safe for unattended automation.
Automate, but keep a sample under review.
Route to a person before acting.
Treat as unmatched.
Capabilities
Agent identity resolution
Match on any combination of name, email, phone, license number, MLS ID, and state. Any single field can find a candidate; more fields sharpen the result.
Real-world name handling
Nickname expansion, middle-name tolerance, and fuzzy similarity, with word boundaries that stop false positives like Dan matching Jordan.
Name recovery from email
Given only an address, the API derives the likely name and searches on it.
Explainable scoring
Every match returns a score plus the exact fields that matched, with documented thresholds for accept, review, and reject.
Built-in guardrails
A match always requires a real identity field; state alone is never enough. When a supplied name doesn’t match, the score is halved, which catches reassigned phone numbers and shared office emails.
Property assessment data
Nationwide assessment records, served from a column store built for analytical query volume.
Built for partner engineering teams and internal services that need agent matching or property enrichment as a building block.