# PremiumPin Property Search

> PremiumPin Property Search is a paid API for AI agents from api.premiumpin.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-27).

Search a closed-catalog real estate property database using natural language questions or structured filters by state, FIPS county code, and custom field selection

## Facts

- Endpoint: POST https://api.premiumpin.com/x402/search?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-27
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/premiumpin-property-search-b73f4f59
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ae4EnPbqDT7b7u7n47vaZ

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability premiumpin-property-search-b73f4f59 -d '<json body>'
```

Example prompt: Search PremiumPin's property catalog for up to 50 residential parcels in Travis County, Texas (FIPS 48453) — I want the address, owner name, and assessed value fields, and my question is 'single-family homes built after 2000'.

## When to prefer this

Use this endpoint when you need to search across PremiumPin's closed property catalog using flexible filters — natural language questions, geographic scoping by state or FIPS county codes, and custom field selection. Prefer this over the exact parcel lookup sibling endpoint when you don't have a specific parcel ID and need discovery-style search across multiple records. Use it instead of the CSV export endpoint when you need programmatic JSON results rather than bulk file output.

## Known failure modes

- Invalid FIPS code format (must be exactly 5 digits) returns validation error
- State code not matching two uppercase letters returns schema error
- Limit exceeding 1000 triggers maximum constraint error
- Empty or missing 'question' field when required causes 400 error
- Requesting fields not available in the closed catalog returns empty or partial results
- Payment failure via x402 protocol blocks the request before processing

## How this service works

PremiumPin closed-catalog property search

## Output

Returns a structured list of property records matching the search criteria, with only the fields specified in the 'select' array. Results are drawn from PremiumPin's closed property catalog and may include parcel identifiers, owner details, location data, assessed values, zoning, and other property attributes depending on field selection. The response may also include a generated search plan that can be passed back as 'previous_plan' in follow-up queries.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "fips": {
   "type": "array",
   "items": {
    "type": "string",
    "pattern": "^[0-9]{5}$"
   }
  },
  "limit": {
   "type": "integer",
   "maximum": 1000,
   "minimum": 1
  },
  "slots": {
   "type": "object"
  },
  "state": {
   "type": "string",
   "pattern": "^[A-Z]{2}$"
  },
  "select": {
   "type": "array",
   "items": {
    "type": "string"
   }
  },
  "question": {
   "type": "string",
   "minLength": 1
  },
  "previous_plan": {
   "type": "object"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/premiumpin-property-search-b73f4f59/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.premiumpin.com](https://www.zero.xyz/host/api.premiumpin.com/llms.txt)