What to Build

Build a working software application that integrates the Qloo API and either functions as an agentic tool, is built using an agent framework, or wires Qloo into an agent you already have. Use Qloo to ground recommendations in real cultural taste so your agent can do more than "answer well"; it can reliably know what people like across music, film/TV, dining, fashion, travel, and more.

Your project should make cultural intelligence the differentiator: the agent should outperform generic LLM-only approaches because it has access to Qloo's API and taste graph (250M+ entities). If your submission would work the same without Qloo, you're building the wrong thing.

Don't be afraid to think laterally: 

- Can an agent help electricians’ customers choose lighting styles for specific rooms -- mood, comfort, function, and personal taste -- instead of generic “bright or dim” advice?

- Can an agent recommend meals and dining options for seniors that match not just taste, but age-specific needs like easy-to-chew menus, low-heat delivery, medication-aware ingredients, or other health constraints?

- Can an agent support people in rare-disease journeys by finding the right mix of information + community + next steps that matches what they actually need both emotionally and practically?

What to Submit

To be eligible, your submission must include all of the following:

1. A link to a functional demo application

A live, working app participants can try end-to-end. This should demonstrate the core features of your project.

2. A URL to a public code repository (GitHub, GitLab, or Bitbucket)

The repo must be public and it should contain all source code, assets, and instructions needed for the project to run.

3. A text description of what your project does

Explain the key features and functionality: what the agent or workflow can do, and what makes it "Qloo-powered."

4. External hosting / fully published requirement

Your demo must be hosted and fully published externally, such as a live website or web app, or a hosted APK / TestFlight build. Submissions that only run locally or rely on private access will not qualify.

5. An open-source license, with the file visible in About section of your repo. 

NOTE: Demo videos are not required. Instead of asking for a recording, we're requiring something judges can actually use.