Property Data API

Query 150M+ U.S. property records by address or APN. Returns assessor data, taxes, deeds, mortgages, permits, and comps in real-time JSON for your product or AI agents.

View API plans Developer docs

GET /v1/properties/{property_id}

{  "property_id": "12276B6",  "apn": "451-492-10-00",  "alternate_apn": "4514921000",  "fips": "06073",  "county": "San Diego County, California",  "property_address": "3352 Goldfinch St, San Diego, CA 92103",  "property_street": "3352 Goldfinch St",  "property_city": "San Diego",  "property_state": "CA",  "property_zipcode": "92103",  "latitude": 32.740421,  "longitude": -117.171596,  "source_last_updated": "2026-05-18",  "last_updated": "2026-06-27",  "owner_1_full_name": "Morgan Family Trust",  "owner_2_full_name": null,  "mailing_full_address": "PO Box 3352, San Diego, CA 92103",  "mailing_city": "San Diego",  "mailing_state": "CA",  "mailing_zip_code": "92103",  "occupancy": "Owner Occupied",  "land_market_value": 130000,  "structure_market_value": 375000,  "total_market_value": 505000,  "assessed_land_value": 112294,  "assessed_structure_value": 397517,  "assessed_value": 509811,  "tax_year": "2025",  "annual_tax_amount": 5735.48,  "tax_rate": 0.01125,  "is_tax_exemption": true,  "exemption_type": "Homeowner",  "delinquent_year": null,  "last_sale_date": "2018-05-01",  "last_sale_amount": 454000,  "is_listed": false,  "is_listed_date": null,  "is_pre_foreclosure": false,  "pre_foreclosure_status": null,  "pre_foreclosure_date": null,  "land_use_code": "1001",  "land_use_category": "Single Family Home",  "zoning": null,  "year_built": "2004",  "year_built_effective": "2004",  "beds": 4,  "bedrooms": 4,  "baths": 3.5,  "full_bathrooms": 3,  "half_bathrooms": 1,  "total_rooms": 8,  "sqft": 2594,  "living_area_sqft": 2594,  "lot_size_sqft": 10392,  "lot_size_acres": 0.239,  "basement_sqft": null,  "cooling_type": "Central",  "heating_type": "Central",  "fireplace_ind": true,  "exterior_wall_type": "Stucco",  "roof_type": "Composition Shingle",  "pool_ind": true,  "pool_type": "Pool & Spa (both)",  "sewer_type": "Public Sewer",  "water_type": "Public Water",  "garage_type": "Garage",  "garage_parking": 3,  "legal_description": "BLK 400 LOT K TR DB0013PG522",  "municipality": "CITY OF SAN DIEGO",  "subdivision": "HORTONS ADD LOCKLING",  "neighborhood": "HORTONS ADD LOCKLING",  "census_tract": "006100",  "census_block": "1003",  "tract_num": null,  "legal_lot": "28",  "legal_block": null,  "hoa_name": "PARK CENTRAL TOWERS OWNERS",  "hoa_type": "Mandatory",  "hoa_annual_fee": 420,  "estimated_market_value": 584205,  "avg_rent_estimate": 2685,  "gross_yield_percentage": 5.52,  "cap_rate_percentage": 3.03,  "combined_estimated_loan_balance": 320668,  "estimated_equity": 263537,  "estimated_ltv": 54.89}

Query Modes

Three ways to query property data

Resolve addresses or parcel APNs in a single request, with specialized endpoints for deep transaction history and comps.

1 Credit on Match

Query by Street Address

Send any U.S. street address. The endpoint parses, normalizes, and returns the complete 80+ field core property record in a single request.

GET /v1/properties
  ?address=3352+Goldfinch+St
  &city=San+Diego&state=CA
-> 80+ Core Fields (1 credit)

1 Credit on Match

Query by APN & County

Query with a parcel number and 5-digit county FIPS code when your product or database already stores county parcel identifiers.

GET /v1/properties
  ?apn=451-492-10-00
  &fips=06073
-> 80+ Core Fields (1 credit)

3 Credits on Rows

Deeds, Mortgages, & Comps

Use the returned property ID to fetch deep historical transaction records, mortgage and lien rows, building permits, and comps on demand.

GET /v1/properties/12276B6/mortgages
GET /v1/properties/12276B6/permits
GET /v1/properties/12276B6/sale-comps
-> Deep History (3 credits)

Use cases

What teams build with the Property Data API

Four high-impact ways developers, PropTech platforms, and automated agents use our data.

CRM & Inbound Lead Enrichment

When an inbound lead enters a street address, instantly populate contacts with verified owner names, mailing addresses, assessed values, and estimated equity.

Owner IdentityMailing AddressAssessed ValueEquity

In-App Property & Parcel Search

Embed real-time address and APN lookup directly into your real estate portal, valuation tool, or SaaS product without maintaining county pipelines.

APN & FIPSBed / Bath / SqftYear BuiltZoning

Ownership & Lien Underwriting

Verify property legal descriptions, recorded deed transfers, open mortgage balances, and tax payment history for automated underwriting workflows.

Deed RecordsOpen MortgagesLegal DescriptionTaxes

MCP Ready

AI Agents & Autonomous Research

Equip Claude, ChatGPT, Gemini, or Cursor with live property data via our official MCP server, or execute headless research agents via REST API.

Streamable HTTPOAuth 2.0 PKCEJSON Response

API field catalog

Every field the API can return

The core property response includes 86 fields. Five add-on endpoints include 73 row fields for mortgages, deeds, permits, sale comps, and rental comps. Open a group to see the exact JSON name, type, example value, and meaning. Values can be null when a county or source does not publish that field.

Core record JSON Field dictionary CSV

Core · 1 creditIdentifiers & address14 fieldsCore record object. Property IDs, parcel numbers, situs address, county, coordinates, and update timestamps.

Identifiers & address API response fields
JSON field	Type	Example	Description
`property_id`	string	`12276B6`	AssessorSearch property identifier.
`apn`	string \| null	`451-492-10-00`	County parcel number or assessor parcel number.
`alternate_apn`	string \| null	`4514921000`	Alternate parcel number format reported by the county.
`fips`	string \| null	`06073`	Five-digit county FIPS code.
`county`	string	`San Diego County, California`	County name.
`property_address`	string \| null	`3352 Goldfinch St, San Diego, CA 92103`	Full situs address when available.
`property_street`	string \| null	`3352 Goldfinch St`	Street address portion of the situs address.
`property_city`	string	`San Diego`	Situs city.
`property_state`	string	`CA`	Situs state abbreviation.
`property_zipcode`	string	`92103`	Situs ZIP code.
`latitude`	number \| null	`32.740421`	Parcel or address latitude when geocoded.
`longitude`	number \| null	`-117.171596`	Parcel or address longitude when geocoded.
`source_last_updated`	date string \| null	`2026-05-18`	Source-system update date shown on property detail.
`last_updated`	date string \| null	`2026-06-27`	AssessorSearch record update date when present.

Core · 1 creditOwner & mailing7 fieldsCore record object. Owner names, mailing address, and occupancy signal from public property records.

Owner & mailing API response fields
JSON field	Type	Example	Description
`owner_1_full_name`	string	`Morgan Family Trust`	Primary owner name from public property records.
`owner_2_full_name`	string \| null	`null`	Secondary owner name when one is present.
`mailing_full_address`	string \| null	`PO Box 3352, San Diego, CA 92103`	Owner mailing address from public records.
`mailing_city`	string \| null	`San Diego`	Mailing city.
`mailing_state`	string \| null	`CA`	Mailing state abbreviation.
`mailing_zip_code`	string \| null	`92103`	Mailing ZIP code.
`occupancy`	string	`Owner Occupied`	Owner-occupied or non-owner occupied signal.

Core · 1 creditTax & value12 fieldsCore record object. Assessed value, market value, annual tax amount, tax year, rate, exemption, and delinquency fields.

Tax & value API response fields
JSON field	Type	Example	Description
`land_market_value`	number \| null	`130000`	Land market value reported or normalized from source records.
`structure_market_value`	number \| null	`375000`	Improvement market value reported by the county.
`total_market_value`	number \| null	`505000`	Total market value reported or normalized from source records.
`assessed_land_value`	number \| null	`112294`	Land assessed value.
`assessed_structure_value`	number \| null	`397517`	Improvement assessed value.
`assessed_value`	number \| null	`509811`	Total assessed value reported by the county.
`tax_year`	string \| null	`2025`	Tax year associated with the tax fields.
`annual_tax_amount`	number \| null	`5735.48`	Annual property tax amount normalized to a number.
`tax_rate`	number \| null	`0.01125`	Effective or normalized tax-rate value when available.
`is_tax_exemption`	boolean	`true`	Whether a tax exemption is indicated in the record.
`exemption_type`	string \| null	`Homeowner`	Exemption type, if reported.
`delinquent_year`	string \| null	`null`	Tax delinquency year when reported by the source.

Core · 1 creditSale & status7 fieldsCore record object. Latest sale, listing signal, and pre-foreclosure indicators shown on property detail.

Sale & status API response fields
JSON field	Type	Example	Description
`last_sale_date`	date string \| null	`2018-05-01`	Most recent sale date available in the indexed record.
`last_sale_amount`	number \| null	`454000`	Most recent sale amount available in the indexed record.
`is_listed`	boolean	`false`	Listing signal when available.
`is_listed_date`	date string \| null	`null`	Date associated with the current listing signal.
`is_pre_foreclosure`	boolean	`false`	Pre-foreclosure signal when available.
`pre_foreclosure_status`	string \| null	`null`	Pre-foreclosure status text from the source.
`pre_foreclosure_date`	date string \| null	`null`	Pre-foreclosure filing or status date when available.

Core · 1 creditProperty characteristics16 fieldsCore record object. Land use, zoning, year built, room counts, living area, building area, lot size, and basement fields.

Property characteristics API response fields
JSON field	Type	Example	Description
`land_use_code`	string \| null	`1001`	Source land-use code.
`land_use_category`	string	`Single Family Home`	Normalized land-use category.
`zoning`	string \| null	`null`	Zoning code or zoning label when available.
`year_built`	string \| null	`2004`	Year built as reported by the source.
`year_built_effective`	string \| null	`2004`	Effective year built or renovation year when reported.
`beds`	number \| null	`4`	Bedroom count used in the property header.
`bedrooms`	number \| null	`4`	Alternate bedroom count field when supplied by the source.
`baths`	number \| null	`3.5`	Bathroom count used in the property header.
`full_bathrooms`	number \| null	`3`	Full bathroom count.
`half_bathrooms`	number \| null	`1`	Half bathroom count.
`total_rooms`	number \| null	`8`	Total room count when reported.
`sqft`	number \| null	`2594`	Building area in square feet.
`living_area_sqft`	number \| null	`2594`	Finished living area in square feet.
`lot_size_sqft`	number \| null	`10392`	Parcel area in square feet.
`lot_size_acres`	number \| null	`0.239`	Parcel area in acres.
`basement_sqft`	number \| null	`null`	Basement area in square feet when reported.

Core · 1 creditBuilding features11 fieldsCore record object. Heating, cooling, exterior, roof, pool, utility, garage, and parking fields.

Building features API response fields
JSON field	Type	Example	Description
`cooling_type`	string \| null	`Central`	Cooling type.
`heating_type`	string \| null	`Central`	Heating type.
`fireplace_ind`	boolean	`true`	Fireplace indicator.
`exterior_wall_type`	string \| null	`Stucco`	Exterior wall material or type.
`roof_type`	string \| null	`Composition Shingle`	Roof type.
`pool_ind`	boolean	`true`	Pool indicator.
`pool_type`	string \| null	`Pool & Spa (both)`	Pool type when reported.
`sewer_type`	string \| null	`Public Sewer`	Sewer utility type.
`water_type`	string \| null	`Public Water`	Water utility type.
`garage_type`	string \| null	`Garage`	Garage type when present.
`garage_parking`	number \| null	`3`	Garage parking spaces when present.

Core · 1 creditLegal, community & HOA12 fieldsCore record object. Legal description, subdivision/community identifiers, census identifiers, and HOA fields.

Legal, community & HOA API response fields
JSON field	Type	Example	Description
`legal_description`	string \| null	`BLK 400 LOT K TR DB0013PG522`	Legal description from the county record.
`municipality`	string \| null	`CITY OF SAN DIEGO`	Municipality or local jurisdiction when available.
`subdivision`	string	`HORTONS ADD LOCKLING`	Subdivision name from the property record.
`neighborhood`	string	`HORTONS ADD LOCKLING`	Neighborhood label when reported.
`census_tract`	string \| null	`006100`	Census tract identifier when matched.
`census_block`	string \| null	`1003`	Census block identifier when matched.
`tract_num`	string \| null	`null`	Subdivision or legal tract number.
`legal_lot`	string \| null	`28`	Legal lot identifier.
`legal_block`	string \| null	`null`	Legal block identifier.
`hoa_name`	string \| null	`PARK CENTRAL TOWERS OWNERS`	HOA name when reported.
`hoa_type`	string \| null	`Mandatory`	HOA type when reported.
`hoa_annual_fee`	number \| null	`420`	Annual HOA fee when reported.

Core · 1 creditMarket & rental estimates4 fieldsCore record object. AssessorSearch market value, rent, yield, and cap-rate estimates shown on property detail.

Market & rental estimates API response fields
JSON field	Type	Example	Description
`estimated_market_value`	number \| null	`584205`	AssessorSearch estimated market value.
`avg_rent_estimate`	number \| null	`2685`	Estimated monthly rent from comparable rental context.
`gross_yield_percentage`	number \| null	`5.52`	Estimated annual gross rental yield percentage.
`cap_rate_percentage`	number \| null	`3.03`	Estimated cap-rate percentage when available.

Core · 1 creditMortgage summary3 fieldsCore record object. Estimated loan balance, equity, and loan-to-value fields.

Mortgage summary API response fields
JSON field	Type	Example	Description
`combined_estimated_loan_balance`	number \| null	`320668`	Estimated combined open mortgage balance.
`estimated_equity`	number \| null	`263537`	Estimated owner equity derived from value and loan balance.
`estimated_ltv`	number \| null	`54.89`	Estimated loan-to-value ratio.

3 credits when rows returnMortgage & lien detail12 fieldsMortgage detail response. Mortgage and lien rows returned from a specific mortgage/lien endpoint.

Mortgage & lien detail API response fields
JSON field	Type	Example	Description
`property_id`	string	`12276B6`	Subject property ID for joining this add-on row to the core property record.
`id`	string \| null	`mtg_20190509_1`	Mortgage or lien row identifier when available.
`amount`	number \| null	`350000`	Mortgage or lien amount.
`lender`	string \| null	`Sample National Bank`	Mortgage lender.
`interest_rate`	number \| null	`7.03`	Interest rate when available.
`recording_date`	date string \| null	`2024-07-10`	Mortgage or lien recording date.
`date`	date string \| null	`null`	Alternate mortgage or lien date when supplied.
`type`	string \| null	`conventional loan`	Mortgage or lien type.
`payment`	number \| null	`2719.85`	Estimated or reported payment when available.
`term`	string	`30 years`	Loan term.
`loan_to_value`	number \| null	`null`	Loan-to-value ratio at origination when available.
`position`	number \| null	`1`	Lien position.

3 credits when rows returnDeed & transaction history16 fieldsTransaction detail response. Recorded deed and transaction rows returned from a specific transaction endpoint.

Deed & transaction history API response fields
JSON field	Type	Example	Description
`property_id`	string	`12276B6`	Subject property ID for joining this add-on row to the core property record.
`recording_date`	source date string \| null	`05/01/2018`	Recording date for the deed or transaction document.
`sale_date`	source date string \| null	`05/01/2018`	Sale date when reported separately from recording date.
`document_type`	string \| null	`Grant Deed`	Recorded document type.
`document_number`	string \| null	`2018.143821`	Recorder document number.
`transaction_type`	string \| null	`Arms Length`	Normalized transaction type when available.
`transaction_amount`	number \| null	`454000`	Transaction amount from the recorded document.
`buyer_name`	string \| null	`Morgan Family Trust`	Buyer or grantee name.
`buyer_is_corporate`	boolean	`false`	Corporate buyer indicator.
`seller_name`	string \| null	`Park Place Homes LLC`	Seller or grantor name.
`seller_is_corporate`	boolean	`true`	Corporate seller indicator.
`lender_name`	string \| null	`Valley Community Bank`	Lender named on the transaction when available.
`title_company_name`	string \| null	`San Diego County Title Co.`	Title company named on the transaction when available.
`sort_order`	number \| null	`1`	Sort order supplied by the transaction source.
`transaction_details`	object \| null	`null`	Source-specific transaction detail object.
`formatted_date`	string \| null	`2018-05-01`	Backend-computed display date when supplied.

3 credits when rows returnPermit history10 fieldsPermit detail response. Permit rows returned from a specific permits endpoint where county coverage is available.

Permit history API response fields
JSON field	Type	Example	Description
`property_id`	string	`12276B6`	Subject property ID for joining this add-on row to the core property record.
`permit_number`	string \| null	`BLD-21-00842`	Permit number from the permitting source.
`permit_type`	string \| null	`Residential pool and spa`	Permit category or permit type.
`permit_date`	date string \| null	`2021-06-14`	Permit issue, application, or status date as reported.
`status`	string \| null	`Final`	Permit status.
`contractor_name`	string \| null	`Central Valley Pools`	Contractor name when reported.
`estimated_job_value`	number \| null	`65000`	Estimated project value.
`estimated_fees`	number \| null	`1420`	Estimated permit fees.
`description`	string \| null	`Install in-ground pool, spa, and code-compliant safety barrier.`	Permit work description.
`sort_order`	number \| null	`1`	Sort order supplied by the permitting source.

3 credits when rows returnComparable sales15 fieldsComparable sales response. Sale comparable rows returned from a specific comparable-sales endpoint.

Comparable sales API response fields
JSON field	Type	Example	Description
`property_id`	string	`12276B6`	Subject property ID for joining this add-on row to the core property record.
`address`	string \| null	`1810 W Sample Ct, San Diego, CA 92103`	Comparable sale property address.
`sale_date`	date string \| null	`2025-06-09`	Comparable property sale date.
`sale_price`	number \| null	`545000`	Comparable property sale price.
`beds`	number \| null	`4`	Comparable bedroom count.
`baths`	number \| null	`3`	Comparable bathroom count.
`sqft`	number \| null	`2388`	Comparable living area in square feet.
`year_built`	number \| null	`2005`	Comparable year built.
`price_per_sqft`	number \| null	`228.22`	Comparable sale price per square foot.
`comparable_property_id`	number \| string	`2712968`	AssessorSearch property ID for the comparable property.
`distance_miles`	number \| null	`0.33`	Distance from the subject property in miles.
`lot_acres`	number \| null	`0.46`	Comparable lot size in acres.
`comp_rank`	number \| null	`2`	Comparable ranking returned by the matching model.
`similarity_score`	number \| null	`3.25`	Similarity score returned by the matching model.
`formatted_comparable_property_id`	string \| null	`296588`	Display-ready comparable property ID when supplied.

3 credits when rows returnComparable rentals20 fieldsComparable rentals response. Rental comparable rows returned from a specific comparable-rentals endpoint.

Comparable rentals API response fields
JSON field	Type	Example	Description
`property_id`	string	`12276B6`	Subject property ID for joining this add-on row to the core property record.
`address`	string \| null	`1918 W Sample Ln, San Diego, CA 92103`	Comparable rental property address.
`rental_date`	date string \| null	`2026-04-27 01:40:09.871`	Rental comp date.
`effective_date`	date string \| null	`null`	Alternate rental effective date when supplied.
`rental_price`	number \| null	`2650`	Monthly rental price.
`rent_price`	number \| null	`null`	Alternate monthly rent field when supplied.
`beds`	number \| null	`4`	Comparable bedroom count.
`baths`	number \| null	`3`	Comparable bathroom count.
`sqft`	number \| null	`2400`	Comparable living area in square feet.
`year_built`	number \| null	`2008`	Comparable year built.
`comparable_property_id`	number \| string	`2674852`	AssessorSearch property ID for the comparable property.
`distance_miles`	number \| null	`1.92`	Distance from the subject property in miles.
`lot_acres`	number \| null	`0.5`	Comparable lot size in acres.
`comp_rank`	number \| null	`1`	Comparable ranking returned by the matching model.
`rank`	number \| null	`null`	Alternate comparable ranking field when supplied.
`similarity_score`	number \| null	`15`	Similarity score returned by the matching model.
`adjusted_rent`	number \| null	`2685`	Adjusted monthly rent estimate when supplied.
`avm_value`	number \| null	`552000`	AVM value associated with the rental comparable.
`url`	string \| null	`null`	Source URL when available.
`formatted_comparable_property_id`	string \| null	`28D0A4`	Display-ready comparable property ID when supplied.

Endpoints

Public API endpoints and credits

Start with an address or APN, then use the returned property ID for the core record or deeper history endpoints. Detail endpoints charge only when they return rows.

Developer docs Detail samples

Property Data API endpoints and credit costs
Endpoint	Credits	Use case
GET`/v1/properties`	1	Resolve address or APN input. Charges only when status is matched and the core property record is returned.
GET`/v1/properties/{property_id}`	1	Fetch the core parcel, owner, tax, valuation, facts, location, and mortgage summary fields for a known property ID.
GET`/v1/properties/{property_id}/mortgages`	3	Retrieve mortgage and lien rows, including lender, amount, rate, recording date, term, payment, and lien position when available.
GET`/v1/properties/{property_id}/transactions`	3	Retrieve recorded deed and transaction rows with buyer, seller, document, title-company, lender, and amount fields when available.
GET`/v1/properties/{property_id}/permits`	3	Retrieve permit rows where county coverage is available, including type, status, permit number, date, contractor, fees, and description.
GET`/v1/properties/{property_id}/comparable-sales`	3	Retrieve comparable sale rows with address, price, date, facts, distance, rank, similarity score, and comparable property ID.
GET`/v1/properties/{property_id}/comparable-rentals`	3	Retrieve comparable rental rows with rent, effective date, facts, distance, rank, adjusted rent, AVM value, and comparable property ID.

Bulk Downloads

Offline Datasets

Need whole counties or statewide database dumps?

If you are training ML models, warehousing parcel records, or running offline analytics, download complete county parquet and CSV files instead of calling the API one property at a time.

Explore bulk data files

MCP Ready

AI Assistant Integration

Connect Claude, ChatGPT, Gemini, & Cursor

Prefer working directly inside your AI assistant or IDE? Connect our official Model Context Protocol (MCP) server with one prompt, OAuth 2.0 PKCE auth, and shared credit allowance.

Set up MCP Server

Pricing

API plans

Pick a monthly credit allowance for the number of property records you expect to pull. Address and APN searches are free, core property records are 1 credit, and add-on history endpoints are 3 credits when they return rows.

Pro + API

Unlimited web views plus starter API access for AI tools and light workflows.

$50/month

Monthly credits: 500/month
Overage rate: $0.08/credit
Core lookup: 1 credit each
MCP Server: Included

API Growth

Small production integrations, internal review tools, and appraisal QA pilots.

$150/month

Monthly credits: 2,000/month
Overage rate: $0.06/credit
Core lookup: 1 credit each
MCP Server: Included

API Scale

Higher-volume validation, enrichment, and workflow automation.

$500/month

Monthly credits: 10,000/month
Overage rate: $0.04/credit
Core lookup: 1 credit each
MCP Server: Included

API Enterprise

Large-volume API access with room for procurement and custom support.

Monthly credits: 100,000/month
Overage rate: $0.024/credit
Core lookup: 1 credit each
MCP Server: Included

All plans include full access to the official AssessorSearch MCP Server for Claude, ChatGPT, Gemini, Grok, and Cursor. Overages are on by default at the rate shown for each plan. The monthly budget is $250 for Pro + API and Growth, $1,000 for Scale, and $5,000 for Enterprise. Lower the budget or turn overages off in your dashboard at any time.

Policy & Governance

Transparent billing, rate limits, and compliance

Clear billing rules with zero hidden costs, automatic overage caps, and explicit public-record data boundaries.

Usage & Billing

Pay for verified records, not dead ends

Address and APN validation is built into the resolution flow. You only spend credits when a verified core property record or add-on history rows are delivered.

0 credits on misses: Lookups that do not resolve to a property record never deduct credits.
0 credits on empty details: Add-on endpoints (mortgages, deeds, permits, comps) only charge when rows exist.
Monthly allowances & overage caps: Included credits reset monthly. Overages continue at your plan rate up to the budget cap you set in your dashboard.
Standard HTTP status codes: Returns 402 credit_limit_exceeded when budget is exhausted and 429 with a Retry-After header during rate spikes.

Data Governance

Public record boundaries & permissible use

Our datasets are standardized directly from 3,000+ county assessors, recorders, and tax collectors nationwide.

County-level variance: Some jurisdictions publish richer deed, tax, or permit rows than others. Contact us to confirm field coverage for specific target counties.
Non-FCRA compliance: AssessorSearch is not a consumer reporting agency. API data cannot be used for FCRA-governed decisions such as tenant, credit, or employment screening.
Public record truth: Built for property research, market valuation, and workflow automation. Certified decisions require official county recorder or assessor copies.
Not title or legal advice: The API provides standardized public assessor records, not an insured title search or legal opinion.

FAQ

Questions before you build

The practical things teams usually need to know before wiring property records into a product, workflow, or AI tool.

Can I submit either an address or an APN?

Yes. Send a street address with city and state, or send an APN plus 5-digit county FIPS code when your product already tracks parcel identifiers. Both resolve in a single request.

What property data comes back in the core record?

The core property record delivers 80+ public-record fields: parcel APN and FIPS, owner identity and mailing addresses, assessed and market values, annual taxes, building specs (beds, baths, sqft, year built, stories), lot characteristics, and mortgage summary metrics.

Can I get deeds, mortgages, permits, and comps too?

Yes. Use the returned property ID with our add-on endpoints to query deep recorded deeds, open mortgages and liens, building permits, and comparable sale/rental records. Detail endpoints only charge credits when real rows exist.

What if I do not know how to code with APIs?

Connect ChatGPT, Claude, Gemini, Grok, or Cursor directly through our official Model Context Protocol (MCP) server to query properties via plain English prompts. If you are developing an app, paste our developer docs into your AI assistant to generate API requests in any language.

Should I use the API or bulk property data?

Use the API when your product needs on-demand property intelligence one parcel at a time. Use bulk property data when you need complete county, state, or nationwide database dumps in Parquet or CSV for data warehousing, ML training, or offline analytics.

How do API credits and overages work?

Searches that do not match a parcel cost 0 credits. Each matched core property record costs 1 credit. Add-on history endpoints cost 3 credits per request only when rows return. You can set a monthly overage spend cap in your dashboard or disable overages entirely.

Next step

Start building with the API

Open the docs, copy the endpoint you need, and test it against an address or APN. If you are building with AI, paste the docs and ask it to generate the request for your app.

View API docs Choose a plan