api-license-agreement

name	api-license-agreement
title	API License Agreement (US)
description	Drafts a clickwrap-ready US API License Agreement for companies licensing proprietary APIs to third-party developers. Use when drafting API terms of service, developer agreements, API access agreements, or click-through license terms. Produces full agreement (17 sections), condensed terms, or developer quick-reference. Cross-references DPA, SLA, AUP, trademark guidelines, and privacy policy modules.
author	CaseMark
author_url	https://github.com/CaseMark/skills/tree/main/skills/legal/api-license-agreement
license	Apache-2.0
version	0.1.0
execution_mode	open
jurisdiction	us
practice	contracts
language	en
tags	["agreement","drafting","transactional"]

API License Agreement (US)

Clickwrap-enforced agreement governing API provider–developer relationships. Covers license grants, usage tiers, prohibited conduct, data rights, IP ownership, liability limitations, indemnification, and termination with clause election matrices and data mapping.

Quick Start

1. Gather intake information (or apply defaults)
2. Set clause elections (Permissive / Balanced / Protective)
3. Complete data map
4. Draft 17-section agreement
5. Validate with quality audit
6. Deliver in requested output mode

Output Modes

Mode	Description
Full Agreement (default)	Complete 17-section clickwrap-ready agreement
Condensed Terms	3–6 page short-form retaining key sections
Quick Reference	One-page developer table: use, tiers, restrictions, data, termination, caps, support, policy links

Step 1: Pre-Draft Intake

Gather unless user says "use defaults" or "just draft":

1. Parties — Provider legal name, state, entity type, notice address
2. API identification — Name, Documentation URL, Developer Portal URL
3. Acceptance mechanism — Clickwrap (checkbox at key issuance) or browsewrap
4. Business model — Free/paid/tiered; rate limits, quotas, overages, billing
5. Permitted use — Commercial use? Developer charges end users? Revenue share?
6. Data sensitivity — Personal data? Regulated (HIPAA/GLBA/FERPA/COPPA)? DPA needed?
7. Governing law — State, venue, arbitration (AAA/JAMS), class-action waiver?
8. Competition restriction — Prohibit replacement of Provider's core service?
9. Branding — Attribution required? Trademark guidelines URL?
10. Deprecation policy — Breaking-change notice period; deprecation window

Defaults (apply and label when user does not specify):

Item	Default	Placeholder
Acceptance	Clickwrap at API key issuance	[INSERT UX DETAILS]