Legal Data Hunter API and MCP Service Terms

Effective date: August 11, 2026. This document applies prospectively and does not alter pre-publication records or obligations.

These API and MCP Service Terms, the API Terms, apply when an Order Form selects an LDH API, Model Context Protocol, hosted search, retrieval, citation, or reference-resolution Service. They supplement the GSA. Capitalized terms not defined here have the meanings in the GSA.

1. Service and access

LDH will provide the selected hosted endpoints, tools, features, environments, allowance, and support identified in the Order Form and Documentation. Beta, preview, experimental, planned, estimated, and best-efforts features are not binding unless the Order Form expressly says otherwise.

Customer may use the Service only for the authorized product, purpose, territory, users, and environments. Customer will protect all keys, tokens, MCP clients, and authentication material and is responsible for its applications, environments, authorization, configuration, and use through its credentials. Customer may not circumvent rate, usage, authentication, technical, or security controls or use undocumented extraction methods.

2. Standard permitted use

Subject to the Agreement, Customer may use responses for the internal business, professional, legal-research, academic, educational, or institutional purpose selected in the Order Form. Customer may incorporate citations, provenance links, bounded excerpts, and non-reconstructive summaries, classifications, analytics, and similar outputs into internal work product.

Customer-facing, embedded, white-label, or OEM use is permitted only when expressly selected in the Order Form. Authorized end users may receive only the content categories and quantities allowed there and by applicable Source restrictions.

Full-text display, downloadable records, bulk endpoints, raw export, persistent end-user copies, model training, sublicensing, internal indexes or embeddings, or other enhanced use requires express Order Form authorization and any required Source-right confirmation.

3. Restrictions

Customer may not:

• offer the Service or indexed materials as a standalone database, corpus, feed, bulk API, downloadable dataset, SQL dump, vector database, or substitute repository;
• reconstruct or systematically extract a substantial portion of indexed materials or LDH's source inventory;
• resell, sublicense, syndicate, publish, or transfer raw or substantially reconstructed content unless expressly authorized;
• use content or outputs for model training, fine-tuning, generalized model improvement, or evaluation-dataset creation unless expressly authorized;
• remove required attribution, provenance, copyright, database-right, or Source notices;
• represent outputs as official, exhaustive, guaranteed current, legal advice, or a substitute for professional verification; or
• use a removed or restricted Source after an effective restriction notice.

4. Customer-facing products

When customer-facing use is authorized, Customer will authenticate and authorize end users; use reasonable rate, download, and extraction controls; maintain end-user terms against raw resale, bulk extraction, database reconstruction, and unlawful use; preserve required attribution and provenance; provide appropriate privacy notices and lawful bases; implement reasonably required Source removals, corrections, or restrictions; and remain responsible for its product, outputs, advice, and end-user relationship.

Customer may not state that LDH endorses Customer or its product without written consent.

5. Caching, storage, indexes, and embeddings

Customer may use transient caching reasonably needed for an authorized integration. Persistent storage is limited to the period, fields, environment, and purpose selected in the Order Form. Internal indexes or embeddings are allowed only if expressly authorized, access-controlled, non-public, used only for the authorized product, and not transferred or exposed as a substitute corpus. No export or sublicence right is implied.

Customer will delete or stop using cached, stored, indexed, or embedded material when required by the Agreement, Source restrictions, or termination rules.

6. Query content and privacy

Query Content means query bodies, prompts, references, search parameters, and other information Customer submits through a request. Service Output means result payloads, retrieved documents, searched citations, returned identifiers, summaries, and other material returned by LDH in response.

LDH will Process Query Content and Service Output only to provide, secure, and support the contracted Service, comply with law, and perform Processing expressly authorized by Customer. LDH will not use Query Content or Service Output to train, fine-tune, or improve generalized models for LDH or a third party without Customer's express written instruction.

Customer may submit ordinary privileged or confidential legal-research inputs where authorized and reasonably necessary. Those inputs are Customer Data and Confidential Information where applicable. Customer remains responsible for authority, minimization, privilege, work product, professional secrecy, and confidentiality. LDH does not guarantee that use of a third-party hosted service preserves privilege, work product, or professional secrecy in every jurisdiction. Other highly sensitive regulated data remains subject to the DPA and any express Order Form authorization.

For Paid Search, LDH will not intentionally store Paid Search query text or ranked result payloads after providing the response in LDH application databases, customer or administrative dashboards, query caches, or intentional content logs. This commitment applies only to Paid Search. It does not apply to the separate Resolve Reference feature, which may cache normalized legal references and canonical identifiers, or to public legal documents, ordinary document-retrieval responses, necessary non-content account, billing, usage, security, support, or compliance records, transient infrastructure processing, or disclosed provider exceptions. Those exclusions remain subject to applicable privacy, confidentiality, security, and DPA obligations.

The DPA applies when LDH Processes Customer Personal Data on Customer's behalf. Returning public legal materials does not by itself make LDH a Processor for Customer.

7. Usage and billing

Allowances, credits, endpoints, request limits, concurrency, rate limits, overages, and renewal treatment are stated in the Order Form. LDH may enforce documented limits. If Customer materially exceeds its allowance, LDH may throttle excess use, request an upgrade, or charge only agreed overages. Unused credits expire only as stated in the Order Form and have no cash value.

8. Sources, availability, and changes

Source coverage and availability may change because of publication practices, access restrictions, law, rights, quality, reprocessing, or technical operations. Unless expressly committed in an Order Form, LDH does not guarantee a Source, document, jurisdiction, date range, refresh cadence, response time, result, or uninterrupted feature. A missing result does not prove that no relevant authority exists.

LDH may add, remove, suspend, reprocess, correct, or restrict Sources and features. Where practicable, LDH will use commercially reasonable efforts to give advance notice before materially reducing paid core functionality. Advance notice is not required for emergencies, security, law, abuse prevention, or upstream restrictions.

Availability, maintenance, support hours, response targets, service levels, and credits apply only if stated in the Order Form or an incorporated SLA. Service credits are the exclusive remedy where the SLA says so.

9. Suspension and end of term

In addition to the GSA, LDH may suspend affected access for compromised credentials, material abuse, attempted bulk extraction, material Source-restriction violations, or conduct reasonably likely to harm the Service or third parties.

At termination, Customer will stop calling the Service and delete credentials. Customer may retain authorized ordinary work product. Cached raw content, stored materials, indexes, and embeddings may be retained only as expressly permitted by the Order Form and Source restrictions.

10. Incorporation and versioning

These API Terms are incorporated only by an Order Form or affirmative online acceptance that identifies this exact version and makes it available before acceptance. A later version does not amend an existing fixed-term Order Form unless the Parties expressly agree otherwise.