API Usage Agreement

DRAFT — for Dan's approval. Not published. This page is not in the navigation (meta.json) and nothing links to it. It is adapted from the CB API Usage Agreement (the CB docs site, api-terms.mdx, version 2026-10-06). The legal wording is yours; every clause below is marked with what was adapted and what needs your decision:

§	Source	What changed / open question
Intro	CB intro	"generate a key in your account settings" → keys from the Connect page or OAuth sign-in (both end in the same key). CB has an acceptance checkbox in its settings; Pink has none — decide whether creating a key / signing in counts as acceptance, or add a checkbox.
1	CB §1 "Your own boats"	Rewritten: scope is the sites you own or are a member of, within your role. The CB Discovery API / redistribution clause is marketplace-specific and was dropped. New: "MCP server and Publish Protocol are the only supported interfaces" (no SDK, no public REST).
2	—	New: your content stays yours; you are responsible for what you publish. Not in CB. Needs your wording on licence to host / serve on *.edit.pink.
3	CB §2 "Attribution required"	Dropped for content you publish (it is yours). Kept nothing about attributing keyword/SERP data — decide whether resold data needs attribution or is simply forbidden (Fair use already forbids bulk resale).
4	—	New: credits — paid calls charged to the site owner at the listed price; refunds as on the Credits page.
5	CB §4 "Daily limits"	Per-key daily budget → per-account limits and Fair use, pointing at the Limits page. CB "Partnership" contact → dan@edit.pink (the address Limits already uses).
6	CB §3 "Terms of Service apply"	Placeholder: Pink has no Terms of Service page yet — the link target is open. Revocation sentence kept as CB's.
7	—	New: Publish Protocol receivers — a destination's publish key is yours to keep secret; Pink calls your receiver only for your site's publishes.
Changes	CB "Changes to these terms"	Kept: the date is the version. CB emails "everyone who holds an API key" — Pink has no such mailing today; decide the notice channel.
Closing	CB closing paragraph	"limited to CB integrations" → dropped (Pink has no such restriction).

Last updated: DRAFT (not in force)

Every Pink API key, and every connection you sign in to, is issued under these terms.

1. Your sites, through the supported interfaces. A key acts as you: it reaches the sites you own or are a member of, and does what your role on each site allows (see Authentication). The supported interfaces are the MCP server and the Publish Protocol. Pink offers no SDK and no public REST API; other endpoints the Pink apps call are internal and may change without notice.
2. Your content. What you write and publish through Pink stays yours. You are responsible for it, and for having the right to publish it.
3. Data you pull. Keyword, SERP and backlink data you pull through Pink is for working on your own sites. Don't resell or redistribute it in bulk (see Fair use).
4. Credits. Paid calls are charged to the site owner's credit balance at the listed price, per call; refunds follow the rules on Credits and pricing.
5. Limits. Every account has the same request limits; see Limits and fair use. If you need more, email us before you build around them.
6. Terms of Service apply. Use of Pink is subject to our Terms of Service. We may revoke a key or a connection at any time for violations of these terms.
7. Receivers. A destination's publish key belongs to you; keep it secret. Pink calls your receiver only to publish your site's pages.

By creating a key or connecting a client you confirm that you use Pink for sites you are entitled to work on, under these terms.

Changes to these terms

Any change to these terms moves the date above. Continuing to use Pink after a change means you accept it.