Build with the Napster Omniagent API. Integrate it into whatever you're working on, or whatever you've always wanted to build, and show us what becomes possible when an agent can show up everywhere your users do.
The brief is wide open. The API is the constraint, not the scenario. Here are a few directions to prime the pump — but these are examples, not a menu:
Deploy one Omniagent across a VS Code extension (via WebSocket) and a browser-based code review interface (via WebRTC), sharing memory of what the developer is working on. The same agent that answered a question in the IDE already knows the context when the developer opens the review view.
Job interviews, salary negotiations, difficult feedback conversations. The agent plays the other person and uses memory to track how the user's performance changes across practice sessions. Video presence and persistent memory both do real work here.
An agent that joins a live stream or virtual event as a visible participant — answering audience questions via WebRTC in real time, with a knowledge base scoped to that event. The layer between a live host and a large audience. Focus: latency, simultaneous sessions, graceful fallback.
A screenplay, a funding round, a product launch — something with many moving parts over weeks. The agent holds the full context across every session: decisions made, open questions, next steps. The demo should show the agent referencing something from a much earlier session unprompted — that's what makes memory tangible.
Four winners. One per category. Each winner receives a prize pack worth nearly $2,000. Every submission is eligible for every category; judges decide which submission best fits each one.
| Category | What we're looking for |
|---|---|
| Best agent in production | The submission closest to something you could ship to real users tomorrow. Code quality, error handling, observability, deployment story. |
| Most creative use of voice + video | The submission that best leverages multimodal capabilities — voice, video, or both — in a way that surprises us. |
| Best enterprise application | The submission that most convincingly solves a real enterprise problem — customer support, sales, onboarding, internal ops, or anything where an agent adds clear business value. |
| Wild card | The submission that takes the API somewhere none of us expected. Originality of concept, not just execution. |
Each winner receives:
| Step | Stage | What happens |
|---|---|---|
| 1 | Sign up | Register above. You'll get a confirmation email immediately. |
| 2 | Get your key | Your API key will be included in the confirmation email along with links to documentation, sample integrations, and a quickstart guide. Your key is scoped to the hackathon period. |
| 3 | Build | Build between May 18 and June 7. Questions? Ask in the Discord community — Napster engineers are around during US working hours. |
| 4 | Submit | Email your GitHub repo, 60-second demo video, and description to [email protected] by June 7, 23:59 PT. Submissions are final after that. |
| 5 | Winners | Winners across all four categories announced June 15. |
| 6 | Prizes | Winners confirm shipping details within 5 business days. Prizes ship within 30 days. |
This is a skill contest, judged on merit. Every submission is evaluated against a published rubric. Decisions are final.
| Criterion | Weight | What we're scoring |
|---|---|---|
| Use of the API | 30% | How well does the submission exercise the distinctive capabilities of the Napster Omniagent API? Submissions that could've been built on any LLM API score lower. |
| Technical execution | 25% | Does it work? Is the implementation clean? Are edge cases handled? |
| Creativity | 25% | Did the entrant bring an original idea? Does the scenario surprise us? |
| Presentation | 20% | Demo video quality, clarity of description, ease of understanding the build. |
Judging panel: Napster leadership including Edo Segal (CTPO), engineers, and product leads.
For the complete legal terms, see the Official Rules.