Start here when you are evaluating property data APIs. Each link opens a deep guide — Realie vs a vendor, latency and pricing benchmarks, or best-for buyer situations. Realie published numbers only (Free, $50, $150, $350; ~20 ms average; 180M+ addresses with nationwide U.S. county coverage). Confirm competitor terms with each vendor directly.
Realie vs vendors
Side-by-side guides for teams evaluating Realie against established property data providers — including agent-first MCP/CLI on self-serve keys. Confirm competitor terms directly with each vendor.
When to read: When ATTOM is the incumbent — or you want agent-first MCP/CLI on self-serve keys vs enterprise REST.
Open guide →
When to read: When an enterprise CoreLogic contract is up for renewal or a self-serve pilot.
Open guide →
When to read: When parcel boundaries are covered but you also need assessor, tax, and recorder fields.
Open guide →
When to read: When BatchData pricing or skip-trace scope is on your shortlist — or you want agent-first MCP/CLI vs marketed MCP.
Open guide →
Performance & pricing
Benchmark and commercial pages — published Realie latency (~20 ms average), self-serve plans (Free, $50, $150, $350), and nationwide coverage (180M+ addresses, nationwide U.S. county coverage).
When to read: When latency decides whether property lookups can run inside a live request.
Open guide →
When to read: When published Realie latency (~20 ms average) and the separate Sept 2026 ATTOM benchmark inform architecture.
Open guide →
When to read: When month-to-month self-serve pricing (Free / $50 / $150 / $350) drives the decision.
Open guide →
When to read: When you need to confirm the free tier exposes the full dataset, not a sample.
Open guide →
When to read: When token allowances and overage math need a side-by-side with your projected volume.
Open guide →
Best for / buyer guides
Category listicles for common buyer situations — developers, parcel/GIS, AI agents, and free-tier evaluation.
When to read: When engineering or agent teams shortlist vendors — include agent-first MCP/CLI posture, not REST alone.
Open guide →
When to read: When you need agent-native public-records API access without BatchData contact-enrichment quotas.
Open guide →
When to read: When parcel geometry quality is the gating requirement before wider property fields.
Open guide →
When to read: When you need an agent-native property API — MCP + CLI as first-class surfaces, not a bolt-on.
Open guide →
When to read: When you must validate production fields on a free tier before procurement.
Open guide →
Data source comparisons
Guides that compare record types and sourcing models — public records vs listings, and what property APIs typically include.
When to read: When your product needs assessor/recorder fields and you are unsure whether MLS data belongs in scope.
Open guide →
When to read: When you need county owner of record and mailing address — not MLS listing agents or skip-trace contacts.
Open guide →