返回提示词目录第 1386 页

起草面向开发者的 API 使用条款

依据 API 信息生成开发者条款草案、关键决策建议和待确认事项,并标出需用占位符或法律审阅的内容。

完整提示词

<context>
You draft the terms developers accept to use an API. API terms govern a different relationship from end-user terms: the developer builds their own product on yours and often handles your users' data. The clauses that matter most: accounts and credentials (keys are confidential, the developer is responsible for everything done with them, and must report compromise); limits (rate limits and quotas, no circumvention through multiple accounts, fair use); permitted and prohibited uses (no scraping beyond the API, no building a directly competing product or clone where that is the policy, no reverse engineering or security testing without permission, no reselling raw access, no high-risk uses the service is not built for, and restrictions on using outputs to train competing models where relevant); data (what developers may store and for how long, caching limits, deletion when users disconnect or on request, compliance with privacy law, a privacy policy for their app, no selling user data, and security incident notice); branding and attribution (when to credit and how to use marks); changes (versioning, notice periods for breaking changes and deprecations, and emergency changes for security); monitoring and audit; fees and billing for paid tiers; suspension and termination with what happens to data and apps afterwards; disclaimers and liability; and confidentiality of non-public features. Platforms often get the change and deprecation clause wrong, either promising stability they cannot keep or reserving rights so broad that developers will not build on them.

Jurisdiction: {{jurisdiction}}
</context>

<task>
API:
<api>
{{api}}
</api>

1. Key decisions: commercial use, competing products, data retention limits, deprecation notice period, attribution requirements, audit rights, and AI training restrictions, each with a recommendation and trade-off.
2. API terms: numbered sections in plain language covering acceptance and relationship to other terms, accounts and keys, licence to use the API, limits, prohibited uses, user data and privacy, security, branding and attribution, fees, changes and deprecation, monitoring, confidentiality, intellectual property and feedback, suspension and termination, effect of termination, disclaimers, liability, indemnity, and governing law. Use [BRACKETS] for anything not supplied.
3. Developer portal summary: a short "the rules in brief" section that matches the terms.
4. Points to confirm, including whether a data processing agreement is needed for developers processing personal data on your behalf or vice versa.
</task>

<constraints>
{{> guardrails/professional-limits}}
- Do not invent rate limits, prices or notice periods; use brackets and recommend a range only as a suggestion.
- Keep the prohibited-uses list tied to the risks the user described plus common baseline items; do not pad it.
- Make the change and deprecation clause balanced: a real notice period for breaking changes, with an exception for urgent security or legal changes.
- Recommend legal review where the API handles health, financial or children's data, or where developers act on behalf of end users.
{{> output/uncertainty}}
</constraints>

<output_format>
## Key decisions
Table: decision | recommendation | trade-off.

## API terms
Numbered sections with headings.

## Developer portal summary
Short bulleted list.

## Points to confirm
Numbered list.
</output_format>

可替换内容

  • {{jurisdiction}}
  • {{api}}
  • {{> guardrails/professional-limits}}
  • {{> output/uncertainty}}
  • [BRACKETS]

分类与标签

办公效率、API 服务、开发者协议、法律草案

前往 AI 图片创作