The 60-second recipe. Zero cost. No software to install. A stranger can follow it.
The steps
Open the Muse app (iOS, Android, or web) and start a new chat.
Paste this into the chat:
Build a custom connector to the CWI music catalog so you can
answer questions about Cumulative Web Inc's catalog. Read the
connector brief first: https://cumulativewebinc.github.io/cwi-muse-recipe/muse.md
The API is public and needs no credentials. When you fetch catalog
data, use URLs tagged ?src=muse-recipe.
Let Muse guide you. Per Meta's Help Center: "ask Muse to create a Custom Connector. Muse will guide you through the process, which can involve retrieving API information from the service." Approve any fetch prompts it shows you.
No credentials needed. The catalog API is public and unauthenticated. If Muse asks for an API key, something went wrong — it should never need one. (Meta stores credentials in its Secure Credentials Store; here there is nothing to store.)
Try it: ask Muse "Which tracks are in the CWI catalog?" It should fetch catalog.json and answer from the data.
Done. You can also just ask Muse anytime: "Connect the CWI catalog custom connector" — it will re-read the brief.
✅ VERIFIED — 2026-09-19
What was verified on 2026-09-19:
Meta's official custom-connector mechanism, quoted verbatim from Meta's Help Center ("How Muse works with Connectors"): a custom connector is created by asking Muse; Muse guides the setup and stores credentials in its Secure Credentials Store. This recipe follows that mechanism exactly.
API behavior: all catalog endpoints answered HTTP 200 on 2026-09-19 — /openapi.json, /catalog.json, /llms.txt, /graph.json, /kit.json, /.well-known/agent-card.json on cumulativewebinc.github.io/cwi-learn.
OpenAPI 3.0.3 spec parses and enumerates 70+ read-only GET paths; every path is a static file on GitHub Pages.
What was NOT verified (open item): the actual in-app click-through — tapping through Muse's setup screens — was not performed. That step requires a live Muse app session, which cannot be run from an agent sandbox. It is queued for Black's laptop session and will be recorded here when done.
🧪 Dogfood status
Dogfood-gated: docs-verified ✔ · API-behavior-verified ✔ · in-app click-through ⏳ (needs Black's laptop session). A recipe claiming full end-to-end verification before that click-through is done would be a trust liability — so it says so here, on the page.
🔒 Security guarantee
The catalog API exposes nothing beyond public catalog data: track metadata, verified placements, gear registry, datasets. There is no server — the entire API is static files on GitHub Pages, which is physically incapable of writes, logins, or sessions.
No secret values appear anywhere in this recipe. The API needs no credentials (no API keys, no logins, no tokens).
If any credential is ever required in the future, this recipe requires it to go through Meta's Secure Credentials Store only — never pasted into chat.
⚠️ Honest labeling — from Meta, verbatim
"Meta doesn't review custom connectors or how they use your information, so grant access with caution and review the provider's privacy policies." — Meta Help Center, "How Muse works with Connectors".
This is a community-published recipe, not a Meta product. Cumulative Web Inc is not affiliated with Meta.
📏 Measurement & kill rule
Every catalog link from this recipe carries ?src=muse-recipe so downstream queries are attributable to it.
Honest measurement: a setup that never queries is a zero — the count only includes catalog requests that actually arrived with the tag. Current counting is done by the CWI team; the tag is present in the markup to verify.
Kill rule: fewer than 25 attributed catalog queries in 90 days → this lane is killed and the page is taken down. Re-verification every 30 days; if the stamp passes 30 days without re-verification, the page is marked STALE.
🔁 Re-verify cadence
Re-verify every 30 days: (1) re-check Meta's Help Center text for the custom-connector mechanism — if Meta changed the flow, update or no-ship; (2) re-run the HTTP 200 sweep over all catalog endpoints; (3) update the stamp date or mark STALE on this page. Next due: 2026-10-19.