01
Scope and common rules
This annex applies to the relevant Laintas Search functions together with the Platform Terms, Privacy Policy, Data Use Notice and Billing and Refund Policy. It supplements or overrides general terms only on its stated product matters. Mandatory law and valid individually negotiated agreements take priority. The version expressly provided and validly accepted at purchase or use applies; a web update does not automatically change existing orders.
02
Results and webpage rights
Search returns titles, URLs, snippets or extracted pages and depends on indexing, changes, access, region and upstream state. It does not promise complete coverage or accurate content. Links and excerpts do not license republication of site content, databases, images or paid material. Respect source licences, access restrictions and law; do not bypass login, paywalls or other permissions.
03
Successful requests, retries and failures
A request may reserve allowance and settle in the endpoint’s units on success, with failures following its reservation-refund and deduplication mechanism. Search and fetch can have different units; internal supplier attempts are not automatically user calls. New valid client requests can be separately charged; idempotency only applies within the supported fields and window. Empty or partial results, cache and timeouts are assessed against endpoint documentation and delivery, with billing corrections available.
04
Queries, extraction and log scope
Search console request logs omit raw query bodies and record status, counts, latency and usage metadata. This does not mean queries are unprocessed or that every upstream, network or user application retains nothing. Queries and required URLs or page content reach the search path, including configured fallback such as Serper when needed; target sites also receive connections. Do not put unnecessary sensitive information in queries, URLs or key labels.
05
Keys, limits and service state
Protect and revoke leaked API keys. Request validity, quotas, concurrency and rate limits apply together. Proportionate throttling may protect stability and prevent abuse; unlimited concurrency and permanent trials are not promised. REST and MCP are different interfaces to the same service and cannot evade limits or duplicate grants. Callers processing their users’ data retain notice, authority and protection duties to those users.
06
Metering search, extraction and empty results
Search and extraction use their respective documented and confirmed units even with the same key. Empty search results can be valid retrieval, not necessarily endpoint failure. Blocked pages, missing text and partially successful URLs follow actual delivery and disclosed endpoint pricing. Timeouts distinguish an undelivered client response from server non-completion; an HTTP status alone establishes neither universal free use nor universal charging. Internal supplier retries must not become repeated user charges without corresponding delivery or authority.
07
Idempotency windows, retries and request evidence
Deduplication applies only where an endpoint supports it and the agreed identifier is used correctly. Supported Search Idempotency-Key records currently have a seven-day technical window. Outside it, missing IDs, changed bodies or newly generated IDs do not guarantee merging with an earlier request. After a network loss, check available usage and request state before resubmission; retries may return prior results, fail or form new valid requests. Metadata retention does not make unstored queries recoverable. Supply time, a key identifier rather than its secret, request ID and endpoint for billing review.
08
Automated access, caching and downstream users
Robots rules, login, geography, paywalls and licences can limit content access; the API does not promise circumvention. Cached text or summaries may be outdated, especially for prices, law, health and other timely facts. Serving your users still requires notices, authority, attribution and source rights; API access is not a licence to copy or commercially redistribute an entire source database. Targets, queries and pages can disclose business intentions. Avoid unrelated access tokens and personal secrets in URLs and queries.