realtor_skill

This skill helps you search realtor listings, agents, and property details via Realtor API, returning structured results for quick decision making.
  • Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill realtor

  • _meta.json271 B
  • SKILL.md2.4 KB

Overview

This skill connects to Realtor.com data via the Realtor API to search property listings, agents, and retrieve detailed property or agent profiles. It exposes a single CLI script with commands for for-sale, rental, and sold searches, property lookups, agent searches, and location autocomplete. The tool returns JSON by default and supports human-readable output for quick inspection.

How this skill works

The CLI wraps Realtor API endpoints and requires a RapidAPI key set in the REALTOR_API_KEY environment variable. Each command calls the appropriate API route, parses the JSON response, and prints raw JSON or formatted output when --human is passed. Commands accept common filters like city, state_code, postal_code, price range, and identifier fields for direct lookups.

When to use it

  • When you need programmatic access to current for-sale, rental, or recently sold property listings.
  • When building a data pipeline or ETL job that ingests Realtor.com listing or agent data.
  • For quick property or agent lookups during research or CRM enrichment tasks.
  • When testing location autocomplete for search UIs or address normalization.
  • When you need machine-readable JSON output for integrations or automation.

Best practices

  • Store REALTOR_API_KEY securely in environment variables or a secrets manager, not in code.
  • Use specific filters (city, state_code, postal_code) to limit results and reduce API usage.
  • Prefer identifier-based commands (property --property_id, agent-get --nrds_id) for stable lookups.
  • Respect rate limits; cache frequent queries and implement retry/backoff on failures.
  • Validate and sanitize user input for CLI commands to avoid malformed requests.

Example use cases

  • Exporting daily new for-sale listings in a target city for market monitoring.
  • Enriching lead records in a CRM with agent details using agent-get by NRDS ID.
  • Powering a prototype search UI with location autocomplete and live listing previews.
  • Generating neighborhood reports by aggregating recently sold data for a ZIP code.
  • Automating rental vacancy monitoring by polling search-rent with postal_code filters.

FAQ

A RapidAPI key for the Realtor API must be set in the REALTOR_API_KEY environment variable.

How do I get readable output instead of raw JSON?

Add the --human flag to any command to receive formatted, human-readable output.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational