Connect
Signed-in capture, no extension
You do not install anything in your laptop browser. Songdata opens a sandbox Chrome with a named profile. You sign into the dashboard there. Cookies stay in that profile. Cron reopens it and runs the service skill. A scraping extension does not help: it still needs a session, and Chromium in a burst sandbox barely runs extensions.
- 1. Attest who you are on dots.id and name the dashboard.
- 2. Login vault — live remote Chrome, profile songdata-russ-spotify.
- 3. Skill — per-service clicks and a screenshot. Moondream reads the integer.
Spotify for Artists
Spotify for Artists has no public totals API. The artist logs into artists.spotify.com once inside Songdata’s sandbox Chrome. Cookies stay in the agent-browser profile for that artist and platform.
Dashboard https://artists.spotify.com
Signed in when URL is on artists.spotify.com and the page is not the marketing/login wall. Home or Music/Songs is visible.
No public S4A API. The signed-in Chromium profile is the credential. Never store the Spotify password in Songdata.
Artist does this in the sandbox Chrome
- Open the live sandbox Chrome Songdata started (not your own browser).
- Sign into artists.spotify.com. Complete 2FA there.
- Stay until the dashboard home is visible.
- Songdata snapshots that profile. You never install an extension.
Cron runs the skill
agent-browser --profile songdata-russ-spotify open https://artists.spotify.com agent-browser --profile songdata-russ-spotify snapshot -i
Set AGENT_BROWSER_SNAPSHOT_ID (and Vercel tokens locally) to burst the vault. Until then this page is the contract, not a live Chrome.