Redfin Scraper API

# Integrate HasData Redfin Scraper API

## Task

Add the Redfin data function this project needs using HasData Redfin Scraper API.
Inspect project instructions, the server-side runtime, existing HTTP client, and tests first.
Follow the project's conventions and preserve unrelated code. No new SDK is required.
Choose listing search, property lookup, or both to match the user's requested workflow.
Implement only the endpoints the project needs.
Do not replace the REST integration with an MCP connection or a custom Redfin scraper.

## References

Read the documentation for each selected endpoint before implementing:

- Listing search: https://docs.hasdata.com/apis/redfin/listing.md
- Property lookup: https://docs.hasdata.com/apis/redfin/property.md
- Error handling: https://docs.hasdata.com/api-codes.md
- Documentation index: https://docs.hasdata.com/llms.txt
- Full documentation (fallback): https://docs.hasdata.com/llms-full.txt

Start with the endpoint references. Use `llms.txt` to find additional pages.
Use `llms-full.txt` only when needed; extract relevant sections instead of loading everything into context.
If a `.md` reference is unavailable, try its HTML URL without `.md`.
If it is still unavailable, ask for the missing documentation rather than guessing.

## Optional agent skill

If the official `hasdata` skill is already available, use its relevant guidance.
Otherwise, if this agent supports skills, ask before installing it in this project:

```sh
npx skills add hasdata/agent-skills --skill hasdata
```

Run from the project directory and select the coding agent in use.
The `hasdata-cli` skill is not required. If installation is declined or unsupported, continue with the docs.
Flag conflicts between skill guidance and current API docs rather than guessing.

## Implementation

- Listing search: `GET https://api.hasdata.com/scrape/redfin/listing`. Accept required `keyword` and `type` (`forSale`, `forRent`, or `sold`), plus optional documented filters and `page`.
- A ZIP or city searches a market. An address or building can return a single property card instead of a list; `type` does not apply to that result.
- Property lookup: `GET https://api.hasdata.com/scrape/redfin/property`. Accept the required `url`, a valid Redfin property URL.
- Encode query parameters, including bracketed filters, with the project's HTTP client.
- Preserve the returned JSON. Listing searches include `properties` and pagination; property details are under `property`, including optional `priceHistory`, `taxHistory`, and `redfinEstimate`.
- Handle timeouts, documented errors, empty results, varying search result shapes, and missing optional fields. Bound pagination to the user's requested scope.
- Keep requests server-side. If there is no suitable server-side runtime, discuss the options before changing the architecture.

## Credentials

- Implement the integration and mocked tests without requiring a live API key.
- Read `HASDATA_API_KEY` from the project's existing environment or secret store and send it as `x-api-key`.
- If the key is missing before live verification, ask the user to configure it from https://app.hasdata.com/api-keys.
- Never ask the user to paste the key into chat. Check only that it is configured, without printing its value.
- Never put the key in browser code, logs, or version control. Add only a placeholder to the project's example configuration.
- If using a local `.env` file, make sure it is gitignored.
- Send the key only to `https://api.hasdata.com`. Never forward it to documentation, result URLs, or redirects to another origin.

## Verification

- Add mocked tests for success, empty results, missing optional fields, and errors, plus a usage example. Cover list and single-card shapes if using listing search. Run local checks.
- Only after explicit user approval and with a configured key, make one live verification request to the selected endpoint with agreed inputs. Successful requests consume credits.
- Validate the HTTP status, documented API status, and response structure. An empty result set can be valid.
- Do not automatically repeat paid requests to obtain a nonempty response.
- Report changed files, setup commands, and test results. State separately whether live verification passed, failed, or was skipped.
- Ask before deploying.