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 an add-on to a base dataset. Every API token you create on the API Tokens page carries one base data tier, Basic Property Data or Core Property Data (Tax Assessor), so a token cannot hold comps alone. On pay-as-you-go, comps adds $0.02 per record to the rate of the base tier, so the lowest-cost token for comparable analysis (the Basic Property Data tier plus the Comparable Properties dataset) bills $0.03 per record ($0.01 plus $0.02), about 3× lower than the $0.10 per record of a token with Core Property Data (Tax Assessor) alone. 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.

On pay-as-you-go, the per-record price follows the datasets your API token is provisioned for, and their rates are added together. The options.datasets array in a request selects which fields come back, and it does not change the price. A token provisioned for both core and comps bills $0.12 per record ($0.10 plus $0.02), which is more than core alone.

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 BatchData MCP server comparables tools comparable_property_preview and comparable_property_page request the basic and comps datasets by default, so MCP clients (Claude Desktop, IDE assistants, and custom integrations) get the slim comp record. The lower comps price is not automatic, because the price follows the token and not the datasets that the tools request. An MCP OAuth sign-in grants core and comps by default, which on pay-as-you-go bills $0.12 per record. To bring pay-as-you-go MCP comp pulls down to $0.03 per record, an account owner or admin opens API Tokens, selects the MCP Server Datasets tab, chooses the Basic Property Data tier, checks Comparable Properties, and selects Save Configuration. Saving ends the MCP sessions that are connected for the account, so users reconnect after the change.