These Developer API Terms apply to your use of the PostcodeProperty.ai REST API, Model Context Protocol server, test environment, developer dashboard, keys and related documentation (the Developer Services). They supplement our general Terms of Service. An order form or written enterprise agreement takes priority if it expressly conflicts with these terms.
1. Account and API keys
You must provide accurate account information, keep credentials confidential and restrict each key to the people and systems that need it. Keys may not be embedded in public client code, shared between unrelated organisations, published, sold or transferred. You are responsible for activity under your account until you notify us of suspected compromise. Test keys are for development and return synthetic or fixed test data; they must not be treated as evidence about a real property.
2. Permitted use
You may use results in your own lawful applications, internal workflows and customer-facing property products, subject to your plan, these terms, the response metadata and the source licences. You must preserve applicable attribution and provenance, distinguish estimates or modelled values from source facts, and make material coverage or freshness limitations visible to your users.
You must not:
- use the Developer Services for unlawful discrimination, fraud or harassment;
- circumvent authentication, rate limits, metering or technical restrictions;
- probe for vulnerabilities except under an agreed security-testing process;
- misrepresent a derived value as an official source record or professional advice;
- build or redistribute a general-purpose address database from returned address fields;
- use restricted fields outside the purpose, territory or tier stated in the response or documentation; or
- resell substantially unchanged bulk results as a substitute for our Developer Services without written permission.
3. Source data, caching and redistribution
Source datasets retain their own copyright, database rights and licence terms. A response does not grant broader rights than its source permits. The response's provenance, licence, coverage, vintage, restrictions and attribution fields form part of the permitted-use conditions. Our attribution register identifies the standard notices, but you remain responsible for checking the fields and use case you select.
You may cache results only for your application's operational needs and only while permitted by the applicable source licence and your plan. Refresh time-sensitive results at a reasonable interval. Do not remove source identifiers or combine data in a way that conceals a licence restriction. Bulk extracts, persistent mirrors, training corpora and redistribution feeds require a written enterprise data licence unless the documentation expressly says otherwise.
4. AI and MCP use
You may call read-only tools from an AI assistant or agent. You are responsible for the agent's calls, downstream output and human review. Do not present generated summaries as surveys, valuations, conveyancing searches, lending decisions or legal, financial, environmental or safety advice. Do not use results to train or fine-tune a model unless your plan and every applicable source licence allow that use.
5. Charges, limits and taxes
Plans include a stated credit allowance and request-rate limit. Endpoint weights are published in the documentation. Successfully delivered billable calls consume credits; rejected or failed calls do not. Subscriptions renew until cancelled. Fees are non-refundable except where required by law or stated in an order form. Taxes are added where applicable. We may correct obvious metering errors and will provide reasonable evidence for a disputed charge.
6. Changes and availability
We may make additive changes within a version. We will use reasonable efforts to give 90 days' notice before a breaking change to a generally available version, except where a security, legal or upstream-data change requires faster action. Beta features, test data and third-party sources may change or end without that notice. No service level applies unless agreed in writing.
7. Security, privacy and support
You must use reasonable security controls and promptly rotate exposed keys. Do not submit special-category personal data, secrets or unnecessary personal data in query parameters. We process account, billing, security and usage telemetry to operate the service, prevent abuse, support customers and meet legal obligations. Support requests should include the response's X-Request-Id, but never the full API key.
8. Suspension and termination
We may limit or suspend access where reasonably necessary to address security risk, unlawful use, non-payment, licence breach, excessive load or material breach. Where practicable, we will give notice and an opportunity to cure. You may stop using the service and cancel a subscription at any time. On termination, stop calling the service and delete restricted cached data when the relevant licence or agreement requires it.
9. Accuracy, advice and liability
Property data can be delayed, incomplete, approximate, modelled or wrong. Coverage varies by source and geography. The Developer Services are informational and are not a valuation, survey, title report, environmental search or professional advice. To the maximum extent permitted by law, the services are supplied as available and our aggregate liability arising from the Developer Services is limited to the fees you paid for them in the 12 months before the event giving rise to the claim. Nothing excludes liability that cannot lawfully be excluded.
10. General
These terms are governed by the laws of England and Wales and the courts of England and Wales have exclusive jurisdiction. If one provision is unenforceable, the others continue. Contact hello@postcodeproperty.ai with contractual questions.