不可变版本 / Immutable version 2026-10-25.1. 本副本不加载分析或应用脚本 / No analytics or app scripts.

Laintas Search 专用条款

适用于搜索 API、网页提取、Playground 与 MCP 接口。

2026-10-25.1 · 2026-10-25

适用与共同规则

本附件适用于 Laintas Search 的相应功能,与平台服务条款、隐私政策、数据用途说明及收费与退款政策共同适用。仅在本附件明确的产品事项上补充或优先于总条款;强制性法律及双方有效的个别协商约定优先。以购买或使用时明确提供且依法有效接受的版本为准,网页更新不自动改变已有订单。

结果与网页权利

搜索提供标题、URL、摘要或网页提取结果,可能受索引时间、页面变化、权限、地区和上游状态影响,不保证覆盖所有页面或内容真实完整。结果中的链接和摘录不授予原站内容、数据库、图片或付费资料的再发布权;请遵守原站许可、访问限制和适用法律,不得绕过登录、付费墙或其他权限。

有效请求、重试和失败处理

请求可预留额度,成功后按当前接口的单位计量,失败按该接口的预留退回和去重机制处理。搜索和网页提取可能采用不同单位,不应把供应商内部重试次数直接当作用户调用次数。客户端新提交的有效请求可能单独计费;幂等或去重保障只在接口支持的字段和窗口内成立。空结果、部分结果、缓存和超时应按接口文档与实际交付状态核查,错误计费可请求更正。

查询、提取与日志范围

Search 控制台请求日志不保存原始查询正文,记录状态、数量、耗时、用量等元数据;这不表示查询未被处理或所有上游、网络和用户自己的应用都不保存内容。查询与所需 URL 或页面内容会传给搜索路径,必要时使用 Serper 等已配置的后备服务;访问目标站点本身也会产生连接。不要在查询、URL 或 API key 标签中放入不必要的敏感信息。

密钥、限流和服务状态

保护 API key 并为泄露密钥撤销授权;合法请求、接口配额、并发和速率限制同时适用。平台可为稳定性和防滥用进行相称限流,不保证无限并发或永久免费试用。REST 与 MCP 是同一服务的不同入口,不能用于重复领取或规避额度。涉及第三方用户数据时,调用者仍须履行对其用户的告知、授权和保护义务。

Laintas Search product terms

For search APIs, page extraction, the Playground and MCP endpoints.

2026-10-25.1 · 2026-10-25

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.

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.

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.

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.

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.