• ## Inspiration
Beam Music started from a simple idea: music apps should feel more personal and more playful. Instead of only listening to a song as it was released, we wanted users and agents to explore “what if this track had a different vocal style?” in a fast, demoable way.
## What it does
Beam Music converts a short music preview into a selected AI voice style and returns a playable audio result. For the demo, an agent can call a Zero-friendly API with a source audio URL, a voiceId like ariana_grande, and an output format, then receive an MP3 conversion result.
## How we built it
We built a web demo with a React/Vite frontend, an Express API layer, and a GPU-backed Beam SVC voice-conversion service running on akash. The conversion backend uses RVC-style voice models, trims the input for a short demo flow, processes the vocal conversion, mixes the result, and returns an MP3. We also prepared a Zero-compatible endpoint and smoke-test commands so agents can invoke the capability programmatically.
## Challenges we ran into
The hardest parts were deployment shape and reliability. The frontend site and the Express API did not map cleanly to the same hosted environment at first, so the public Zero endpoint returned 404 even though the local route existed. We also had to verify which voice models were actually available in the live GPU service and adjust the demo to use ariana_grande, the model that worked reliably.
## Accomplishments that we're proud of
We got the GPU Modal voice-conversion service working end to end with real audio output. The ariana_grande conversion returns a valid 15-second MP3, and the service reports healthy GPU/model status. We also set up Zero CLI authentication, tested direct Zero fetches, documented the payload, and created repeatable smoke-test scripts for future demos.
## What we learned
We learned that agent-facing APIs need more than a working model. They need stable public routes, clear schemas, predictable errors, reachable media URLs, and deployment environments that match the runtime. We also learned that Zero integration is easiest when the capability endpoint is already healthy, payment-aware, and testable with one command.
## What's next for Beam Music
Next, we’ll deploy the Zero-facing API route so POST /api/zero/voice-conversion works on the public Beam Music URL, connect it to the live Modal BEAM_SVC_URL, and add x402 or MPP payment handling so it can be indexed and reviewed as a Zero capability. After that, we’ll expand supported voices, improve conversion quality, add result hosting, and make Beam Music available as a reliable agent-callable music transformation API.
Built With
- akashgpu
- react
- rvc
- zerocli
Log in or sign up for Devpost to join the conversation.