Build something useful.
Respect the boundaries.

Verified access

Use your own account and a mobile number you control. Do not share account credentials, misrepresent your identity, create repeated accounts to obtain additional free credits or use verification services to circumvent the account controls.

Keys, quotas and fair use

Keep API keys private and revoke exposed keys promptly. Published credit costs, request intervals, daily caps, page bounds and time-window limits apply across your account. Do not evade limits using multiple keys, accounts, clients or networks. Automated calls must respect the server’s retry instructions.

Permitted service surface

Use the documented REST API and MCP tools. Do not attempt to access private source fields, underlying databases, descriptions, internal search bands, agent contact details or another person’s account information. Do not probe undocumented paths to obtain a broader dataset.

Source rights and redistribution

Access to the API is not a transfer of ownership in source data. Respect applicable source rights and privacy obligations. Do not use the free service to reconstruct or republish the underlying database, sell unrestricted data exports or create an agent contact directory.

What the observations mean

Data reflects the sources and observations available to the service. Coverage and freshness vary. A missing listing is not proof of a sale, an advertised price is not a valuation and observed counts are not a complete census of the property market. Check important conclusions against appropriate sources.

Availability and changes

The current free developer tier does not include a service-level guarantee. Endpoints, limits and credit allowances may change as the product develops. Account access may be restricted to investigate abuse or protect the service. These terms do not exclude rights that cannot lawfully be excluded.

Before putting an integration into production

Review coverage and freshness, the public field policy, usage limits and account privacy. Build error handling and backoff into your client, and avoid presenting observations as verified transaction facts.

Published 7 November 2026.