尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證製作者的介紹僅有上面的一句話。 更多詳情請閱讀儲存庫 README。 儲存庫 README ↗
正在載入完整 README。
檢視完整 README ↗Three answers in, one culturally coherent evening out — powered by the Qloo taste graph.
Most agents answer well. Taste Concierge knows what people like: it maps a 3-question interview to Qloo's taste-graph entities (250M+), then chains insights across dining, film, music and retail to compose an evening that fits that person — not the charts.
An LLM alone recommends popular things. Taste Concierge recommends that person's things:
/search./v2/insights call is seeded by
your entities — and the playlist is additionally seeded by the chosen
film, so the music follows the night's centerpiece. That's cultural
coherence, not four independent top-10s.Remove Qloo and the product collapses: without the taste graph there is no entity affinity, no cross-domain coherence, and no grounding — just generic popular answers.
# 1. Get a hackathon API key: see the Devpost overview page / docs.qloo.com
# 2. Configure and start
cp .env.example .env # put your key in QLOO_API_KEY
npx vercel dev # local dev server
Deploy:
npx vercel --prod # set QLOO_API_KEY in the Vercel dashboard
index.html the interview UI + plan cards (zero-framework, fast)
api/plan.ts serverless endpoint: the agent loop
src/lib/qloo.ts Qloo client (X-Api-Key, GET-only, hackathon base URL)
src/lib/agent.ts the pipeline: mapAnswersToEntities → composeEvening
→ recomposeWithRejection (the negative-feedback loop)
The agent pipeline is deliberately small and inspectable — every Qloo call and every affinity decision can be traced in the code.
Built for the Qloo Agentic Hackathon. License: MIT.