June 2026

We've added a new low-cost dataset built specifically for comparable-property analysis: comps. It gives you the attributes you need to compare properties — beds, baths, living area, lot size, last sale, and valuation range — without paying for a full property record.

The comps dataset returns 24 comp-analysis attributes per property, spanning building characteristics, lot size, classification, ownership status, last-sale detail, listing status, and valuation range. That's roughly 91% fewer attributes than a full core record — just the fields that matter for a CMA.

comps is priced at $0.02 per record on pay-as-you-go — about 5× lower than the $0.10/record cost of fetching a full core record. For subscription customers, the comps add-on mirrors the base *-Basic tiers and shares your base subscription's monthly record quota, so there's no separate allocation to manage.

Pay-as-you-go pricing applies to accounts without a property data subscription. If you're on a subscription, comps is accessible only after you add the Comparable Properties add-on to your plan — the API does not revert to per-record pricing for datasets your subscription doesn't include. Without the add-on, a comps request returns the intersection of comps with your token's base dataset (basic or core) rather than the full comp projection. The same applies to the MCP comparables tools. See the developer guide for the full access and pricing rules.

The biggest beneficiaries are the BatchData MCP server comparables tools. MCP clients — Claude Desktop, IDE assistants, and custom integrations — that use comparable_property_preview and comparable_property_page automatically request the low-cost comps dataset by default. That means your existing MCP-driven CMA workflows get the lower per-comp cost with no configuration changes: counting, previewing, and paging through comparables now run at roughly 5× lower cost than the equivalent core workflow.