Home Sign In Talk to Sales
High Performer  •  Best Support  •  Easiest To Do Business With

February Already? Only right we show you love...

January was a month about depth, not breadth.

Less “shipping for the sake of shipping.”
More getting closer to how real decisions actually get made in the field—and letting that shape what we build.

Below is a snapshot of what we shipped, why it matters, and a couple of operator voices that helped sharpen our thinking along the way.…

Property Data Is Only Useful If It Has Memory

One of the clearest themes we’ve been hearing—especially from investors and developers building underwriting or acquisition workflows—is that snapshots lie.

Properties don’t exist at a single moment in time. They accumulate intent.

So in January, we leaned harder into property history and transaction context, including:

  • Prior owner fields in Property Search
    (priorOwner, priorOwnerSalePrice, priorOwnerSaleDate, priorOwnerAddress)

  • Arms-length vs non–arms-length transactions as both filters and response fields

  • “Prior months owned” now allowing 0 as a minimum value — making it much easier to surface quick flips

This isn’t about adding more fields.
It’s about making it easier for your product to answer questions like:

Is this a real comp?
Was this transaction informative—or noise?
What’s the story behind this asset?

If you’re building anything related to residential development, underwriting, or capital allocation, Brandon Riddick-Seals articulates this better than we ever could.

He’s the former head of the Atlanta Housing Authority. And on the latest episode of Ground Truth, Brandon breaks down why surface-level data fails, how incentives shape the built environment, and why historical context matters more than most software admits.

👉 Listen to Brandon Riddick-Seals on Ground Truth
 (Especially relevant if you’re building investor or development workflows.)

Skip Trace Data Is Only Useful If You Knows Who's Who

Historically, skip trace data has been returned as a loose collection of phones, emails, and addresses — leaving teams to figure out who belongs to which record.

Over the past month, we’ve been reworking Skip Trace to be person-first.

In v2 Skip Trace, results are returned as a clean persons[] structure — making it explicit which phones, emails, and attributes belong to which individual. The response also now includes marital status and other new demographic data. This lays the groundwork for better CRM ingestion, cleaner enrichment workflows, and fewer downstream assumptions.

(If you’ve noticed personId fields appearing recently, that was an early step toward this larger change.)

Side note: If you’re building CRMs, loan origination tools, or anything workflow-heavy, Aaron Chapman’s episode on the pod is worth your time.

Aaron has a sharp take on where automation helps, where it quietly hurts, and why human judgment still matters—especially as AI gets layered into tools that were already fragile.

👉 Listen to Aaron Chapman on Ground Truth
 (Highly relevant if you’re building CRM workflows or LO-facing products.)

Quick Note On The New DIY Customer Experience (CX)

As you may have seen in our last edition, we launched CX just before Christmas. You can now sign up for a free trial or start a paid subscription (month to month or annual), all without a sales call. You can also see granular usage metrics and manage API keys.

Sign up for a free trial. No sales call required.

The new console isn’t a “launch-and-forget” moment for us. It’s an experiment we’re watching closely.

Completion vs abandonment rates.
Time-to-first-success.
Where people get stuck.

The good news: nearly 500 people have already tried the new flow, which feels awesome. The learning: We’ve got work to do to make sure you can get all your questions answered without breaking stride while building. We’ve got some whizz bang ideas on the board for how to make the experience truly seamless.

We’ll keep iterating in public, and we’ll keep being honest about what’s working and what isn’t.


Speaking of making things seamless: we also embedded a Context7-trained documentation assistant directly in our docs. Ask questions in natural language, get code examples, troubleshoot errors. Access it here.

Why We’re Doing It This Way

The best product teams don’t guess what users want.
They listen to operators who live with the consequences.

Ground Truth isn't content marketing for us—it's field research. The features above are what we heard.

And if the pattern holds, February's conversations will shape what we ship in March.

If you're building something interesting with this stuff—or struggling with something that should be easier—let us know. We're listening.

Lastly, if you’re attending Inman in NYC this week, let me know. I’ll be there, and I’d love to grab a coffee and hear what you’re up to.

💜
 Vince

Why REAPI?

Do more. Build faster. Spend less.

performance

Enterprise Grade Performance

Retrieve tens of thousands of records with sub 1 second response times. 99.9% uptime.

performance

A.I. enablement

When you're ready to leverage A.I. for deeper analysis, train your models against our datasets to derive your own proprietary insights.

performance

Developer Support

Need help thinking through your architecture? Hit us up directly. Or pop into our Discord. We love to nerd out on this stuff.

performance

Stretch your budget

Half the price and 10x as powerful as any solution from a big box data provider.