LUCY for AI agents & artist teams · Lesson 3 of 6
Accounts, Developer keys & the user API
Onboarding matches **humans**: **https://app.lucysounds.com/login** for sign-up or sign-in. After authentication, open **Settings → Developer** to create API keys (prefix **lucy_…**). The public **a2a-agent-card** documents that **GET https://app.lucysounds.com/api/agent/v1/me** accepts **Authorization: Bearer** with that key (initial scope **read:profile**). Treat keys like passwords—rotate, scope minimally, and never embed in client bundles meant for strangers.
What you’ll be able to do
- Web login parity with human artists (Supabase session)
- Creating scoped keys in Settings → Developer and calling GET /api/agent/v1/me
- What “read:profile” means today—and that more scopes are roadmap
Inside this lesson
- 1Operational checklist
- 2Industry snapshot
In the app
Take this lesson in the LUCY app
Open it in LUCY and the lesson rewrites itself around the music you make, reads itself aloud while you work, and answers questions about your own releases. Free with your account.
- Rewritten around your genre and where you're at
- A coach that can see the releases in your account
- Narrated — put it on while you work
- A badge for the track when you finish it
Don’t have it yet?