Teams that already keep meeting recordings in TicNote often ask a practical question: can Claude, ChatGPT or Gemini work from those transcripts instead of from a blank chat? TicNote answers it with a published path called the TicNote API Skill. This article summarizes what the Skill page states, what it does not state, and how a buyer can test the workflow before deciding whether a recorder such as the TicNote card belongs in the kit.
The facts below were checked against the English Skill page on ticnote.com on 27 September 2026. They describe TicNote's documentation; CNPS.AI sells hardware and does not sell or configure API access.
1. What the Skill page actually says
The TicNote API Skill page describes one install path in four steps: copy the published install prompt, send it to your AI assistant, log in to TicNote and copy the API Key from “TicNote Key” in the profile menu, then give that Key to the assistant to finish setup. After setup, the page says no special syntax is needed: you ask in plain language to find recordings, transcribe audio, summarize decisions, translate, run research across a project or organize a library. It also says the Key can be used to retrieve completed transcripts and AI summaries for external tools.
The Skill is unlocked with a TicNote Professional or Business plan. The page addresses “your AI assistant” generically; the only named walkthrough is for Codex.
2. What it does not say, and why that matters
As of the check date, the page publishes no dedicated card, connector, plugin, custom GPT or Gem for Claude, ChatGPT or Gemini. It also prints no REST endpoints, no rate limits and no Skill price. A team can still send the published prompt to any of the three assistants, because that is exactly what the page instructs, but it should not expect a vendor-documented menu path for them. If an assistant cannot download the Skill package, the sensible move is to stop and use the tool TicNote documents rather than searching for a hidden setting.
Treat every gap as a question for your inquiry or for TicNote, not as something to fill by assumption.
3. Handle the Key like a password
The Key is pasted into a chat. That is convenient and also the main governance point. Decide who is allowed to generate a Key, which assistant account receives it, and how it is revoked when someone changes role. Paste it only into the conversation that installed the Skill; never into a shared prompt library, a screenshot or a second tool. Record where the assistant provider processes the content it receives, and check that against your existing rules for meeting recordings.
4. Test the workflow, not the demo
A short pilot answers more than a feature list. Use recordings you are authorized to process and one assistant your team already licenses.
| Test | What to record |
|---|---|
| Install | Whether the published prompt installs on your assistant, and the exact assistant and version used |
| Retrieval | Whether the assistant finds the intended recording by date, project or title |
| Summary | Decisions, owners and dates compared against a human note of the same meeting |
| Language | Behaviour on mixed-language and technical passages your team actually uses |
| Permissions | What the Key exposes, and what happens after it is revoked |
| Exit | How transcripts and summaries are exported if the workflow stops |
Keep the failures. A summary that misses one decision is more informative than five good ones. The method in Meeting AI: measure the finished note applies unchanged.
5. Decide about hardware last
Hardware is optional for the Skill; files can be uploaded from other sources. The question is where reliable recordings will come from once the assistant workflow works. For fixed meeting rooms, the TicNote card publishes 64GB of storage (about 434 hours), sits visibly on the table and lists Basic and 1-Year Pro Plan variants; the TicNote Lite is the lower-priced recorder for meetings and lectures, and the Pods WiFi are earbuds for recording on the move. Whether a hardware-bundled Pro plan counts as a Professional or Business plan for the Skill is not published on the shop; confirm it on ticnote.com before you buy for that reason.
Current prices are shown on the shop listing (for example the TicNote card on shop.cnps.ai); this site does not take payments.
6. Write down the decision
A useful record names the assistant and version, the plan that unlocked the Skill, the Key owner, the test recordings, the observed failures and the export path. Add the hardware decision only after that record exists. Use the knowledge pilot worksheet for the assistant side. To discuss recorders for a team, send a quotation request with destination, quantity, meeting languages and whether you plan to connect an assistant; the API plan itself is confirmed with TicNote, not with CNPS.
