Skip to main content
Retrieve granular land, structure, and ownership data across the United States. Use this tool to perform collateral valuations, automate underwriting checks, and assess hazard risk profiles for any residential or commercial property. Once you have one or more CLIPs from the CLIP tools, pass them here to retrieve the full characteristics profile for each property.

Industry solutions and use cases

This tool is designed to support specific persona workflows. Choose your path to understand how property data maps to your business outcomes:
Automate valuation and collateral review
  • Comparable matching — Filter properties using livingSquareFootage and actualYearBuilt to locate geographic comparables for appraisal reviews
  • MISMO compliance — Ensure structural characteristics align with FHFA appraisal datasets and MISMO v3.x container mappings
  • Accessory units — Iterate through the structure array to identify multiple structures (ADUs, guest houses) on the parcel using buildingSequenceNumber
See the full mortgage and valuation solutions guide →

Industry standards alignment

Cotality property data conforms to the dominant industry standards used across mortgage, insurance, and real estate:
  • MISMO residential XML (v3.x) — The nested structure elements map directly to the VALUATION_RESPONSE/VALUATION_ANALYSIS/PROPERTY/STRUCTURE container. livingSquareFootage maps to MISMO’s GrossLivingAreaSquareFeet attribute
  • ACORD P&C standardsuniversalConstructionTypeCode maps to the ACORD ConstructionCode standard; universalExternalWallCode and universalRoofCoverCode map to ACORD structural rating standards for risk underwriting
  • USPS publication 28 — Address fields (streetNamePrefixDirection, streetNameSuffix, unitType) are pre-standardized using USPS postal addressing standards
  • OGC well-known text (WKT) — Building footprint geometry in the footprint object is returned in WKT format, compatible with ArcGIS, QGIS, PostGIS, and Leaflet

AI agent onboarding guidelines

When integrating this tool into LLM-powered agents or AI workflows, configure your agent’s system instructions with the following rules:
Address fuzzy matching — If a user queries by address, always invoke clip-find_property_by_full_address first. Use the returned clip to call pc-characteristics_by_clips_tool.Structure loop — Parcels can contain multiple structures. If the user asks about “the building,” check whether summaryNumberOfBuildings > 1. If so, iterate through the structure array and ask the user to clarify which building sequence they want.Modeled vs. recorded data — Check yearBuiltModeledIndicator before responding. If it is 1, state that the construction year is a statistical estimate, not a county record.

pc-characteristics_by_clips_tool

Retrieve comprehensive property characteristics data from Cotality for residential and commercial properties using CLIP identifiers. When to use:
  • You need detailed land, structure, or attribute data for one or more properties
  • Performing property valuation or appraisal workflows
  • Conducting real estate market analysis or comparables research
  • Looking up owner information, tax assessments, or zoning details
  • Verifying building specifications, construction details, or amenities
Examples:
  • “Compare characteristics of properties with CLIPs 111111111 and 222222222”
  • “Find building square footage and year built for CLIP 555555555”
  • “Retrieve owner information and land use for CLIP 999999999”

Input schema

Each CLIP must be a non-empty string consisting only of numeric characters (e.g. ["123456789", "987654321"]). The tool supports batch queries with multiple CLIPs.

Example request

Output schema

The response contains a standard envelope wrapping an array of Property objects. See Response envelope and the field references below.

Response envelope

All four fields are always present in every response.

Property object

Each object in the data array is a Property record. Both fields are optional, nullable, and default to null.

PropertyCharacteristics

All three fields are optional, nullable, and default to null.

Land fields

The land object contains parcel-level information including dimensions, land use, legal descriptions, and assessed values. All fields are optional, nullable, and default to null.

Lot

All fields are optional, nullable, and default to null.

LandDimension

All fields are optional, nullable, and default to null.

LandTopography

All fields are optional, nullable, and default to null.

Structure fields

The structure array contains one record per building on the parcel. Each Structure object carries top-level building attributes and several nested detail objects. All fields are optional, nullable, and default to null.

Top-level structure fields

All fields are optional, nullable, and default to null.

Nested structure objects

Each Structure record may contain the following nested objects. All are optional, nullable, and default to null.

Attic

All fields are optional, nullable, and default to null.

Basement

All fields are optional, nullable, and default to null.

Bathroom

All fields are optional, nullable, and default to null.

Ceiling

All fields are optional, nullable, and default to null.

Commercial

All fields are optional, nullable, and default to null.

Dimensions

All fields are optional, nullable, and default to null.

SquareFootageDetail

All fields are optional, nullable, and default to null.

Footprint

All fields are optional, nullable, and default to null.

FinishComponents

All fields are optional, nullable, and default to null.

Fireplace

All fields are optional, nullable, and default to null.

StructureFunctionalComponents

All fields are optional, nullable, and default to null.

GarageParking

All fields are optional, nullable, and default to null.

StructureImprovement

All fields are optional, nullable, and default to null.

ImprovementFeature

All fields are optional, nullable, and default to null.

OtherStructureImprovement

All fields are optional, nullable, and default to null.

PatioPorch

All fields are optional, nullable, and default to null.

StructureResidential

All fields are optional, nullable, and default to null.

StructureRooms

All fields are optional, nullable, and default to null.

StructureStories

All fields are optional, nullable, and default to null.

StructuralComponents

All fields are optional, nullable, and default to null.

Property attributes fields

The propertyAttributes object contains ownership, location, utilities, and feature data. All fields are optional, nullable, and default to null.

Top-level property attributes

Nested property attributes objects


SummaryData

Aggregate statistics calculated across all buildings on the parcel. All fields are optional, nullable, and default to null.

Owner

Each entry in the owner array contains two nested objects. Both fields are optional, nullable, and default to null.

OwnerDetails

All fields are optional, nullable, and default to null.

OwnerAddress

All fields are optional, nullable, and default to null.

PropertyRights

All fields are optional, nullable, and default to null.

ExteriorFixtures

All fields are optional, nullable, and default to null.

Map

All fields are optional, nullable, and default to null.

Location

All fields are optional, nullable, and default to null.

FunctionalComponents

Parcel-level utility and service codes. All fields are optional, nullable, and default to null.

Features

All fields are optional, nullable, and default to null.

Sample response