recoup-content-connect-fans
Connect a site's fans to the artist
Use the customer's Recoup account to configure a hosted Spotify connection journey. The site contains a public link; the agent keeps the account credential private. Paths below are relative to this skill directory.
Read references/api.md for exact calls, responses and release dependencies. Check endpoint availability before promising this integration: this skill requires the corresponding fan-connection API, database migration, billing policy and Spotify callback to be deployed. A 404 or 503 is a setup problem, not a reason to invent an endpoint or simulate success.
1. Connect the customer
Reuse a customer-provided Recoup API credential from the host's secure environment. Verify it with GET /api/accounts/id. Never print credentials or put them into website code, URLs, generated screenshots or logs.
If no credential exists, use the customer's real email with POST /api/agents/signup, ask for the emailed code, then submit POST /api/agents/verify. Use the returned api_key in the host's secret store or session environment. Ask before writing home-directory files or modifying shell configuration. Do not create a disposable identity for the artist. An empty roster can be a legitimate new account; it is not proof of invalid credentials.
2. Establish ownership and attribution
Resolve the intended artist from the authenticated roster. Use its Recoup artist account ID, not a Spotify ID or an artist row ID. If the artist does not exist, complete the platform's supported artist onboarding first. Resolve the customer workspace before creating a site; ask only if multiple choices remain ambiguous.
Reuse the existing Recoup site ID when provided. For an externally hosted site, register a Recoup site record with its artist and release URL. This record provides attribution without requiring Recoup to host or generate the website. Do not duplicate a site on every retry. Never accept an owner ID from public browser input.