No API key connectedThis browser never inserts the literal secret into a URL or quickstart. Customer-facing apps should call PropData from a trusted server or edge runtime.
Manage access, inspect usage, run real requests, understand coverage, connect AI clients, and get production support. Your application remains the customer experience.
Resolve an address, parcel ID, or coordinate into a canonical property record. Add verified geometry where configured, then attach ownership, valuation, tax, sale, comps, rent, market, risk, and location context through one account.
No API key connectedThis browser never inserts the literal secret into a URL or quickstart. Customer-facing apps should call PropData from a trusted server or edge runtime.
Choose a production route, supply only the parameters you need, then inspect the exact HTTP response. Live requests always use your connected key and never run automatically.
The authenticated usage contract reports plan consumption, allowance, remaining requests, reset time, and—when available—per-endpoint activity. Individual responses may also include worker-window rate-limit headers.
Your subscription allowance and live rate-limit window will appear here without inventing unavailable monthly usage.
Property resolution, parcel geometry, market and rent intelligence, due diligence, public-record signals, deltas, coverage, usage, health, and AI delivery are represented below. Custom endpoints extend this surface around your exact workflow.
PropData separates broad indexed reach from live official-source depth. That makes coverage easier to trust: national parcel indexing, county-configured assessor enrichment, and verified GIS geometry where available.
The national foundation used to resolve parcel identity across the U.S.
State-level reach does not imply identical county-field depth everywhere.
Assessor and GIS adapters are configured and tested at county level.
Customer needs become prioritized sourcing, crosswalk, and QA work.
Verified polygon, centroid, and bounds only where county GIS routing has passed QA.
Ownership, tax, valuation, sale, and building fields vary with the configured source.
County-aware parcel identity and location resolution form the national foundation.
/v1/property/coverage and response provenance to decide what your workflow can promise for a given county. A missing field remains null; coverage is never inferred from marketing language.Connect a PropData API key, switch to Production, then choose “Load live coverage.” This panel preserves the worker response exactly as returned.
Use REST directly, connect compatible MCP clients, or commission a customer-specific response contract. Authentication, account controls, coverage rules, and usage stay unified underneath.
PropData MCP uses OAuth in the client. This workspace can verify your REST key, but it will not claim Cursor, ChatGPT, or Claude is connected without a client authorization record.
Resolve parcels, inspect geometry, compare markets, estimate rent, and call supported tools without leaving the development workflow.
Add to Cursor →Bring PropData tools into supported AI clients while keeping production requests tied to the subscriber account and its limits.
Call standard routes, run bulk or delta workflows, or define a response shape that drops directly into an existing schema.
{
"mcpServers": {
"propdata": {
"url": "https://propdata-mcp.sales-fd3.workers.dev/mcp"
}
}
}
The workspace keeps the active key in memory for this session unless you explicitly choose to remember it on this device. Keys are never written into example source code or page URLs.
No API key connectedPROPDATA_API_KEY, not the literal credential.x-api-key header to the PropData API origin.# .env — never commit this file PROPDATA_API_KEY=pd_live_... # Runtime request curl "$PROPDATA_URL/v1/property?parcel=..." \ -H "x-api-key: $PROPDATA_API_KEY"
Store it in a secrets manager or server-side environment variable. Closing this panel permanently removes the workspace copy.
The old consumer-dashboard tiers are gone. Every plan is an API plan; higher tiers add volume, deeper enrichment, more keys, priority coverage, delivery options, and integration support.
Use the API reference for contracts, the workspace for live testing, and direct support for county coverage or customer-specific payloads.
Authentication, routes, request and response examples, coordinate lookup, geometry, enrichment, MCP, usage, errors, and implementation guidance.
Download guideBrowse the latest route reference, schemas, setup notes, and implementation examples in the documentation workspace.
Open documentationBuild a URL from supported parameters, make an explicit live request with your key, and inspect status, latency, size, and exact JSON.
Share the county FIPS, sample parcel IDs or coordinates, required fields, volume, and target response shape. We will scope the configuration path.
Email coverage requestBring your existing schema. Enterprise integrations can receive a route shaped around the fields and nesting your product already expects.
Send desired payloadFor integration blockers, key rotation, data questions, or incident follow-up, contact the PropData team directly.
sales@proptechusa.aiReview the complete API terms, security duties, source limitations, regulated-use restrictions, caching rules, and legal notices in one printable policy center.
These Terms govern access to the PropData API, developer workspace, MCP connector, official-source adapters, data outputs, documentation, and related services. They are written for an API-only platform—not a legacy consumer dashboard—and separate broad data access from regulated decisioning, source verification, security, and downstream customer responsibilities.
This is the first published API-only terms version in this workspace. No earlier version is represented as available. Future verified revisions will appear here with their effective dates and a real change summary.
“PropData,” “we,” “us,” and “our” mean Local Home Buyers LLC d/b/a PropTechUSA.ai. “Customer,” “you,” and “your” mean the individual or entity accepting these Terms or using the Services. Capitalized terms not defined here have the meaning stated in an applicable signed order form.
By creating an account, purchasing access, accepting an order form, generating or using a key, or otherwise accessing the Services after being presented with these Terms, you agree to them. If you act for an organization, you represent that you have authority to bind it. If you do not agree, do not use the Services. Use by a government entity may require a separately signed agreement.
The “Services” include the PropData APIs, workspace, MCP connector, batch or delta delivery, documentation, official-source adapters, support, and contracted custom endpoints. A signed order form may specify plan, fees, limits, term, service level, fields, permitted use, or special security terms. If documents conflict, the order is: signed order form, data processing addendum, service-level agreement, these Terms, then documentation. Marketing pages and examples do not expand a signed commitment.
You must provide accurate account information, be legally capable of contracting, and keep billing and contact details current. Accounts may not be transferred, rented, or shared outside your organization without written approval. You are responsible for Authorized Users, contractors, and systems acting under your credentials.
During the subscription term and subject to payment and compliance, PropData grants Customer a limited, non-exclusive, non-transferable, non-sublicensable right to access the Services and use returned outputs internally and within Customer applications for the documented or ordered use case. You may display derived or contextual results to your end users when the output is integrated into a legitimate workflow and is not a substitute for, or resale of, PropData’s raw database.
You must use the Services lawfully and may not undermine the service, its sources, or another person’s rights.
PropData aggregates, normalizes, links, or exposes information from public records, official assessor and GIS sources, licensed providers, customer inputs, and other identified sources. Coverage, fields, geometry, update cadence, and historical depth vary by location and source. Data may be incomplete, stale, delayed, inaccurate, unavailable, duplicated, or changed without notice. A national index does not promise identical official-source depth in every county. You must review response provenance, confidence, timestamps, coverage metadata, and null values and independently verify information before any material, legal, financial, safety-related, or regulated action.
PropData is not a consumer reporting agency, and the Services are not offered as “consumer reports” under the U.S. Fair Credit Reporting Act. Unless a separate signed agreement expressly authorizes a compliant product and workflow, you may not use the Services to determine a person’s eligibility, terms, or access to credit, insurance, employment, housing, tenancy, or another purpose governed by the FCRA or similar law. You may not use protected-class data or proxies to discriminate in housing or other regulated activity. You are solely responsible for notices, consent, permissible purpose, adverse-action procedures, testing, human review, and other legal duties applicable to your use.
Customer retains its rights in data, coordinates, parcel identifiers, addresses, schemas, and other content it submits (“Customer Data”). Customer grants PropData a limited right to process Customer Data to provide, secure, meter, support, troubleshoot, and improve the Services and to meet legal obligations. Customer represents that it has all rights, notices, and lawful bases needed to submit and process Customer Data. The parties will enter a data processing addendum when required. Do not submit highly sensitive data unless the applicable order form and security documentation expressly allow it.
API keys and tokens are confidential credentials. Customer must use reasonable administrative, technical, and physical safeguards; keep secrets out of client-side code, repositories, logs, URLs, and support messages; apply least privilege; rotate exposed keys; and promptly revoke access for departed users. Notify PropData without undue delay at sales@proptechusa.ai if you suspect compromise. You are responsible for requests made with your credentials until notice and effective revocation, except to the extent caused by PropData’s breach of its own obligations.
Plans may include monthly allowances, worker rate-limit windows, concurrency limits, key limits, source-specific limits, or overage rules. The API’s authenticated metering records control absent manifest error. Different limits may apply at the account, key, endpoint, source, or time-window level. You may not evade a limit by creating accounts or rotating keys. PropData may throttle abusive or destabilizing traffic and will use commercially reasonable efforts to identify plan remedies for legitimate growth.
You may cache outputs internally for performance, audit, and customer-workflow continuity for the period stated in documentation or an order form, subject to source restrictions and deletion duties. You must refresh time-sensitive outputs and may not treat a cache as perpetually current. You may create derived scores, analytics, and application features, but may not use caching, joins, or repeated calls to reconstruct or redistribute a substantially complete raw PropData or source dataset. AI and MCP-assisted use through your authorized account is permitted; bulk model training requires written authorization.
Fees, currency, billing frequency, allowance, term, and overages are shown at purchase or in an order form. Unless stated otherwise, subscriptions renew automatically for successive periods until canceled before renewal, fees are non-refundable except as required by law or expressly stated, and plan changes may take effect immediately or at the next cycle. Customer is responsible for applicable taxes excluding taxes on PropData’s net income. Failed payment may result in retries, reduced access, suspension, or collection costs permitted by law.
The Services may interoperate with Stripe, RapidAPI, Cursor, ChatGPT, Claude, cloud providers, public agencies, licensed data vendors, and other third parties. Their terms and availability may apply independently. Purchases through a marketplace are also subject to its billing and refund rules; the applicable checkout or order form controls pricing. PropData is not responsible for third-party services outside its control, but will not use this clause to avoid obligations expressly assumed in a signed agreement.
Customer controls its application, user interface, decisions, and downstream disclosures. Customer must provide accurate descriptions of its use, protect end-user information, obtain required permissions, prevent unauthorized extraction, and avoid representing an estimate or incomplete record as guaranteed fact. Customer is responsible for its own terms, privacy notice, accessibility, consumer support, and compliance. PropData may require reasonable remediation where a Customer application creates a material legal, security, source, or reputational risk.
PropData and its licensors retain all rights in the Services, software, documentation, schemas, normalization logic, source configuration, brands, and aggregated operational information. No rights are granted except as expressly stated. Customer retains its applications, Customer Data, and independently developed logic. If Customer provides suggestions, it grants PropData a perpetual, worldwide, royalty-free right to use them without identifying Customer or disclosing Confidential Information.
Each party will protect the other’s non-public business, technical, security, pricing, and product information using at least reasonable care and use it only to perform or receive the Services. Confidential Information excludes information independently developed, lawfully received without restriction, publicly available without breach, or approved for release. A recipient may disclose information when legally required after reasonable notice where permitted.
PropData may improve, replace, add, or deprecate features and sources. We will use commercially reasonable efforts to give advance notice of material breaking changes when practicable. Beta, preview, experimental, or newly sourced features may be changed or discontinued and are provided without a production commitment. Support response times, uptime commitments, service credits, onboarding, and custom coverage apply only when expressly included in a plan or signed order form.
TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE SERVICES AND OUTPUTS ARE PROVIDED “AS IS” AND “AS AVAILABLE.” PROPDATA DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, AND ANY WARRANTY THAT DATA WILL BE COMPLETE, CURRENT, ERROR-FREE, OR AVAILABLE IN EVERY LOCATION. PROPDATA DOES NOT GUARANTEE A BUSINESS, INVESTMENT, VALUATION, COMPLIANCE, OR DECISION OUTCOME. EXPRESS COMMITMENTS IN A SIGNED ORDER FORM REMAIN IN EFFECT.
TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER PARTY WILL BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES, OR LOST PROFITS, REVENUE, DATA, GOODWILL, OR BUSINESS INTERRUPTION, EVEN IF ADVISED OF THE POSSIBILITY. EXCEPT FOR PAYMENT OBLIGATIONS, MISUSE OF THE OTHER PARTY’S INTELLECTUAL PROPERTY OR CONFIDENTIAL INFORMATION, INDEMNITY OBLIGATIONS, FRAUD, WILLFUL MISCONDUCT, OR LIABILITY THAT CANNOT LEGALLY BE LIMITED, EACH PARTY’S AGGREGATE LIABILITY ARISING FROM THE SERVICES WILL NOT EXCEED FEES PAID OR PAYABLE BY CUSTOMER FOR THE SERVICES DURING THE TWELVE MONTHS BEFORE THE EVENT GIVING RISE TO LIABILITY.
Customer will defend and indemnify PropData and its affiliates from third-party claims, damages, penalties, and reasonable costs arising from Customer Data, Customer applications, a prohibited or unlawful use, downstream representations, or Customer’s breach of Sections 5, 7, 8, 9, 11, or 14. PropData will defend Customer from a third-party claim that the unmodified Services, as provided and authorized, directly infringe a U.S. patent, copyright, or trademark, and may modify, replace, or terminate the affected feature. Indemnity requires prompt notice, control of the defense, and reasonable cooperation; no settlement may admit fault or impose obligations on the protected party without consent.
Either party may terminate a signed agreement for uncured material breach after the stated cure period, or immediately for insolvency or an unlawful use that cannot be cured. PropData may suspend access as reasonably necessary to address a security threat, credential compromise, nonpayment, source restriction, legal demand, material prohibited use, or threat to service integrity, and will narrow and communicate the suspension when practicable. On termination, access ends; accrued fees remain due; Customer must stop using restricted raw outputs and delete them where required by source terms or law. Sections intended by their nature to survive will survive.
Customer may not access or use the Services in violation of U.S. export controls or economic sanctions, including by or for prohibited persons, territories, or end uses. Customer represents that it is not restricted from receiving the Services and will maintain appropriate screening and controls for its use and downstream access.
These Terms are governed by Minnesota law, without regard to conflict-of-law rules. Unless a signed order form states otherwise, the parties consent to exclusive jurisdiction and venue in the state courts located in Ramsey County, Minnesota, and the federal courts with jurisdiction over that county. Before filing a claim, each party will give written notice and allow thirty days for good-faith executive resolution, except where urgent injunctive relief is reasonably necessary.
PropData may update these Terms for legal, security, source, operational, or product changes. We will post the effective date and provide reasonable advance notice of a material adverse change through the workspace, account email, or other agreed channel. A material change will not apply retroactively unless required by law. Continued use after the effective date constitutes acceptance only where the updated Terms were properly presented and acceptance is lawfully recorded. Legal notices to PropData must be sent to sales@proptechusa.ai with “Legal Notice” in the subject and by any additional method stated in an order form.
Neither party may assign the agreement without the other’s consent, except to an affiliate or in connection with a merger, reorganization, or sale of substantially all relevant assets, provided the assignee assumes the obligations. The parties are independent contractors; no agency, partnership, fiduciary, franchise, or employment relationship is created. Neither party is liable for delay caused by events beyond reasonable control, excluding payment obligations. Waivers must be written. If a provision is unenforceable, it will be modified to the minimum extent necessary and the rest remains effective. Headings are for convenience. These Terms and incorporated signed documents are the complete agreement regarding the Services and supersede prior proposals on the same subject.
Use the email on your account or connect an existing API key. No demo credential is embedded in this page.