Skip to content

Token costs

Every billable request consumes tokens. The cost is fixed per endpoint and identical whether you call it over the REST API or as an MCP tool. Each response reports its exact cost in the X-Tokens-Used header.

EndpointMCP toolToken cost
Market statsget_market_stats10
Property detailsget_property10
AI comp valueget_property_ai_comp_value10
Property searchsearch_properties10
Parcel filterfilter_properties30
Compslist_comps1 per returned comp
Skip trace by propertyskip_trace_property_owner20 per matched trace
Skip trace by nameskip_trace_owner20 per matched trace
Saved markets — listlist_saved_markets0
Saved markets — savesave_market0
Saved markets — removeunsave_market0
Usageget_usage0
Usage breakdownget_usage_breakdown0

Empty results and errors cost 0 tokens. A search that matches nothing, a 404, a validation error, or a rate-limit 429 all report X-Tokens-Used: 0.

For list_comps, cost scales with the number of comps actually returned — a page of 50 comps costs 50 tokens, an empty page costs 0.

The skip trace tools (skip_trace_property_owner and skip_trace_owner) follow the same rule: a trace that finds no contact information returns matched: false and costs 0 tokens — you only pay the 20 tokens when contact information is found.

This page covers token costs, not dollars. How many tokens your API add-on includes, overage rates, and plan pricing live in the Land Insights app:

  • Plans & billing — your subscription, API add-on, included tokens, and pricing.

To see tokens you’ve already spent this period, use the free usage endpoints.