Docs · Support
Support
THIRI is built by one engineer-musician and a community. Here is how to reach both, and how to make a report that gets fixed fast.
Updated 2026-10-02
Channels
| T.H.I.R.I. Builders (Skool) | The fastest answer. Thursday live Builders calls, Monday repo walkthroughs, private repos. Join with the same email as your key. |
| dennison@bluesprincemedia.com. Paid plans get a reply within a business day. | |
| 20 minutes with the builder | Book a walkthrough for integration questions, quota, or partnership. |
| GitHub | MCP server issues go to BluesPrince/thiri-mcp. |
A bug report that gets fixed
- The endpoint or tool, the exact request body, and the response (status, code, message).
- The time in UTC and your key prefix (
sk_live_xxxxxxxx, never the full key). - What you expected musically. "C13 should keep E and B♭" is more useful than "wrong voicing".
Status
The API's health endpoint is GET https://chords.thiri.ai/health. The engine runs on Cloudflare's edge; the keys portal runs on Supabase. A public status page is on the roadmap; until then, outages are posted in the Skool community first.
Next
The THIRI manual →
What the engine is, how it reasons, and what we measured.