canonical: https://jentic.com/apis/attomdata.com/attomdata

# Attomdata ATTOM Property API

Jentic publishes the only available OpenAPI specification for ATTOM Property API, keeping it validated and agent-ready. The ATTOM Property API exposes a US property data warehouse covering 158 million parcels, with attributes such as ownership, mortgage, deed history, building permits, assessed and market value, and most-recent transaction records. Lookups are available by ATTOM ID, full address, or ZIP code, and responses can range from a single basic profile to an expanded profile with tax and transaction detail. The API is designed for real-estate, mortgage, insurance, and property-analytics workflows that need to enrich an address with structured property facts.

## For AI agents

Look up US property records by ATTOM ID, address, or ZIP code, and pull basic or expanded profiles including ownership, value, taxes, and building permits.

## Scope

Does not handle property listings, MLS feeds, or rent estimates - use for US property record lookup, ownership, value, and permit history only.

## Capabilities

- Resolve a US street address to an ATTOM property ID using `/property/id`
- Fetch a property's owner, mortgage, and most-recent sale via `/property/detail`
- List every property in a ZIP code with `/property/address` for territory analysis
- Pull a basicprofile with assessed value and last transaction in a single call
- Retrieve building permit history attached to a parcel via `/property/buildingpermits`
- Generate market-value snapshots across a filter set with `/property/snapshot`
- Return an expandedprofile combining ownership, tax, and transaction history

## Use cases

### Address-to-property enrichment for lending

Mortgage and insurance applications often start from a typed address. The ATTOM Property API converts that address into a structured property record with owner name, last sale price, mortgage data, assessed value, and tax history, so an underwriting workflow can verify the subject property without manual title research. `/property/basicprofile` returns the core enrichment in a single request, while `/property/expandedprofile` adds transaction and tax history when deeper review is required.

Example prompt: Given the address '586 Franklin Ave, Brooklyn NY 11238', call `/property/basicprofile` and return the owner name, last sale price, last sale date, and assessed value.

### ZIP-level market analysis

Real-estate analysts and proptech tools need to pull every property in a target ZIP to estimate market depth, average sale price, or building-permit activity. `/property/address` paginates the parcels in a ZIP, `/property/snapshot` returns a filtered slice with characteristics, and `/property/buildingpermits` exposes recent permit activity that signals new supply or renovation trends. These three endpoints together let an agent build a ZIP-level market sheet without scraping public records.

Example prompt: For ZIP 78704, call `/property/address` with pagesize=100, then for each ATTOM ID call `/property/buildingpermits` and return the count of permits issued in the last 12 months.

### Permit-driven lead generation for contractors

Contractors and home-service providers want to reach owners who have just pulled a renovation permit. `/property/buildingpermits` returns permit type, effective date, job value, and contractor name attached to a parcel, and `/property/detail` attaches the current owner. An agent can chain the two calls to produce a daily list of newly permitted properties with owner contact context, ready for outreach into a CRM.

Example prompt: Pull `/property/buildingpermits` for ZIP 30308 filtered to permits issued in the last 30 days, then for each ATTOM ID call `/property/detail` to return the owner mailing address.

### AI agent integration via Jentic

An agent built on the Jentic SDK can call the ATTOM Property API without hand-coding HTTP clients or storing the apikey in the agent context. The agent searches for an intent like 'look up property by address', Jentic returns the matching ATTOM operation and its input schema, and the call is executed with credentials resolved from your Jentic One instance. This is the fastest path for a real-estate agent assistant to read property facts on demand.

Example prompt: Use Jentic search 'look up property by address', load the schema for `/property/basicprofile`, and execute it for the address '1600 Pennsylvania Ave NW, Washington DC'.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/property/id` | Resolve an address or filter set to ATTOM property IDs |
| GET | `/property/detail` | Return owner, mortgage, and recent transaction for a property |
| GET | `/property/address` | List properties within a ZIP code |
| GET | `/property/basicprofile` | Return basic property info plus most-recent transaction and taxes |
| GET | `/property/expandedprofile` | Return detailed property info plus most-recent transaction and taxes |
| GET | `/property/buildingpermits` | Return building permit history for a parcel |
| GET | `/property/snapshot` | Return properties matching characteristic filters |

## Key resources

- **Property** — Address, ATTOM ID, owner, characteristics, assessed and market value across basic, expanded, and snapshot profiles
- **Building Permits** — Permit type, effective date, job value, and contractor records attached to a parcel
- **Transactions and Tax** — Most-recent sale and tax assessment data returned within basicprofile and expandedprofile responses

## Why Jentic

- **Setup:** Wiring the ATTOM Property API by hand means handling its API-key auth against its gateway host and passing address or id parameters for each property read. Through Jentic you install once, import the ATTOM Property API from the API Directory, store the key once, and your agent calls it while Jentic applies the key.
- **Permission scoping:** ATTOM's property reads take the identifier or address as query parameters rather than a resource id in the URL path, so limit the agent to the operations it needs, such as property lookup by address or building-permit history. The spec exposes only GET reads, so no write operation is available regardless of what you allow.
- **Credential handling:** Your ATTOM apikey is stored once, encrypted, by your own Jentic One instance and applied at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'look up a property by address', and Jentic returns the matching ATTOM operation with its input schema so the agent calls `/property/basicprofile` or `/property/buildingpermits` without browsing the reference docs.

## Related APIs

- **RentCast API** — RentCast covers US property records and rent estimates and is closer to a self-serve developer plan than ATTOM.
- **Harvard Art Museums API** — Unrelated domain, included only as a fallback. Prefer the alternative above for property workflows.
- **Stripe API** — Stripe handles payments for property-tech subscription products built on top of ATTOM data.

## FAQ

### Why is there no official OpenAPI spec for ATTOM Property API?

ATTOM Data Solutions does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ATTOM Property API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the ATTOM Property API use?

The ATTOM Property API uses an API key passed as the apikey query parameter or header on every request. When called through Jentic the apikey is held in your Jentic One instance and injected at execution time, so the raw key never reaches the agent's context.

### Can I look up a property by street address with the ATTOM Property API?

Yes. Call GET `/property/id` with address1 and address2 parameters to resolve the address to an ATTOM ID, or call GET `/property/basicprofile` or `/property/expandedprofile` directly with the same address parameters to get the property record in one round trip.

### What are the rate limits for the ATTOM Property API?

Rate limits are tied to your ATTOM subscription tier and are enforced per apikey rather than declared in the spec. ATTOM publishes per-plan throttling on the developer portal. Plan for the response volume of `/property/address` in particular, since it can return many parcels per ZIP.

### How do I retrieve building permit history with the ATTOM Property API through Jentic?

Run jentic search 'building permits for a property' to load the operation, then execute GET `/property/buildingpermits` with an attomid or address. Jentic resolves the apikey from the vault at execution time. With pip install jentic an agent can complete the lookup in one async call.

### Is the ATTOM Property API free?

ATTOM Property API is a paid commercial product. ATTOM offers a 30-day free trial of the developer plan, and production tiers are priced by query volume and data scope. Pricing details are negotiated through ATTOM's sales team rather than self-serve.

### Can I limit what my agent is allowed to do with the ATTOM Property API?

Yes. Because you run Jentic One yourself, your own rules decide which ATTOM operations and credentials the agent can use, so you can grant only the reads it needs, such as property lookup by address via `/property/basicprofile` or permit history via `/property/buildingpermits`, while withholding the rest. Every ATTOM operation takes the identifier or address as a query parameter rather than a path resource, so scoping happens at the operation level. The spec exposes only GET reads, so no write operation is available no matter what you allow.