Traspion

View saved version →

---
name: traspion-account-settings
description: Inspect Traspion plan usage, billing history, spelling replacements, or active vocabulary. Use for read-only questions about the connected account, recent payments, and language settings.
---

# Inspect Traspion account settings

Use the narrowest read-only tool that answers the request:

- Use `get_account_status` for plan, wallet-balance, and transcription-usage questions. It returns a link to the Traspion billing page.
- Use `get_billing_history` when the user asks about payments, purchases, charges, credits, or transaction history. Request only as many recent records as needed, up to 100. If `hasMore` is true, explain that older records are available in the Traspion billing dashboard.
- Use `get_spelling_replacements` for custom spelling replacement pairs.
- Use `get_vocabulary` for active vocabulary entries.

Keep these boundaries clear:

- Report only the fields returned by the tool. Do not expose or infer payment, order, subscription, or user identifiers, payment methods, failure details, purchase totals, or other private billing data.
- These tools do not change account or language settings. Do not claim that a setting was added, removed, or updated.
- Do not claim that vocabulary or spelling settings were applied to an upload unless an upload result explicitly confirms it.
- Present the exact billing-page link returned by `get_account_status` whenever reporting plan or wallet status, regardless of the available minutes.
- If an entitlement is unavailable, explain the account status and include the billing-page link returned by the tool. Do not claim to complete purchases or subscription changes in ChatGPT.
- Billing changes, purchases, subscription management, settings changes, and deletion are unavailable through this plugin.

View saved version →

---
name: traspion-transcribe-media
description: Transcribe an attached audio or video file with Traspion, including speech-to-text, audio-to-text, video-to-text, speaker detection, or translation requests. Use when the user wants a new recording converted into a transcript.
---

# Transcribe audio or video to text with Traspion

Use `upload_and_transcribe` once for the audio or video attachment the user identifies.

- If no attachment is available, or multiple attachments make the target ambiguous, ask the user to identify one file.
- If the user has not specified speaker handling, ask one combined question before uploading: “Would you like speaker labels? If yes, how many speakers are there (2–30), or should Traspion detect the number automatically?” Do not ask a second confirmation after the answer; the original transcription request already authorizes the upload.
- If the answer is no, set `speakerPartitioning: false` and omit `speakersCount`. If the answer is yes with a count, set `speakerPartitioning: true` and pass that count. If the answer is yes but the count is unknown, set `speakerPartitioning: true` and omit `speakersCount` for automatic detection.
- Skip the speaker question when the user already specified whether speaker labelling is wanted. Never guess the number of speakers or attempt to determine it before transcription.
- Set `channelIdentification: true` only when the user requests channel identification. Speaker diarization and channel identification may both be enabled when requested; omit `speakersCount` in that combination so AssemblyAI detects speakers automatically within each channel.
- Use the tool defaults for other unspecified options. Pass a language, translation target, transcription prompt, PII redaction, or profanity filtering only when the user requests it or supplies the value.
- Do not claim that advanced options unavailable in `upload_and_transcribe` were enabled.
- Do not automatically retry an upload. A retry can create a duplicate Traspion file.

Treat the tool result as authoritative:

- If transcription completed, retrieve any remaining transcript pages needed for the user's request. Present the text in ChatGPT's native editable view when available; otherwise show it in the conversation. Never claim that a partial page is the complete transcript.
- If validation or transcription is still processing, preserve the returned `fileId`, explain the status and suggested follow-up, and do not claim completion.
- On an explicit request to check progress, call `get_transcription` with that `fileId`. If it is still processing, report the status and stop; do not repeatedly poll within the same response or upload the file again.
- If the account lacks transcription balance, report the failure and present the exact Traspion billing-page link returned by the tool. Do not retry the upload or rewrite the link.

View saved version →

---
name: traspion-work-with-content
description: Find, retrieve, translate, edit, save, rename, or export an existing Traspion speech-to-text transcript. Use when the user wants to work with audio-to-text or video-to-text content already stored in Traspion.
---

# Work with Traspion content

Resolve the intended file before using a file-specific tool.

- Reuse a `fileId` already returned for the clearly identified file.
- Otherwise call `list_files`, using its filename, date, or status filters when the user supplied those details. If several files could match, ask the user to choose; do not silently infer an ID. A request for the latest file may use the most recent matching list result.
- When showing files returned by `list_files`, present them as a Markdown table with row number, filename, upload time, and status. Keep the returned order and use the row number to resolve a user's follow-up selection. Do not expose a pagination cursor unless it is needed for the next page.
- Call `get_transcription` for every request to retrieve a transcript, including when the user switches to another file later in the conversation.

## Retrieve and translate

- Use the returned pagination flags and next offsets when more transcript content is required. Continue only until the user's task has enough content or the complete requested transcript has been retrieved.
- Clearly identify partial results. Never describe a truncated transcript as complete.
- When displaying a completed transcript or stored translation, retrieve all pages needed and use ChatGPT's native editable view when available. Otherwise show the text in the conversation. If client limits prevent showing it all, identify the result as partial and offer a complete export. The plugin does not supply its own editor.
- Follow the returned `presentationMode`. When both speaker and channel identification are enabled, present each segment once in a combined form such as `[00:00–00:08] Channel 1 · Speaker A: text`. Preserve the returned labels and timestamps, omit a label only when it is absent, and do not duplicate the same content as a separate plain transcript unless the user explicitly asks for plain text.
- Use `get_translation` first when the user asks for a translation, because a stored Traspion translation may have been requested during transcription. If it is still processing, report the status and stop after that check.
- If `get_translation` reports `TRANSLATION_NOT_REQUESTED`, tell the user: "You didn't opt for translation while transcribing, so I'll use ChatGPT to translate the transcription." Retrieve the complete transcription and translate it directly in ChatGPT into the user's requested language. If a requested stored translation is still processing, report that status instead of substituting ChatGPT translation.
- Present that fallback as **Transcript translation**. Translate faithfully and preserve the transcript's meaning, paragraph structure, speaker labels, and timestamps when present. Do not summarize, paraphrase, polish, add commentary inside the translation, or claim that Traspion generated or stored it.
- After translating the complete transcript in ChatGPT, present it in a native editable view if the client offers one. Otherwise present the complete translation in the conversation under **Transcript translation**.
- Never save a ChatGPT-produced translation to Traspion, even after a save request. Tell the user to copy or download the ChatGPT result if they want to keep it.
- For a stored translation, follow `nextTextOffset` until the complete text is available. For a transcript, follow the returned text and segment offsets as needed. Use `export_transcript` when a complete stored file is too large to display.

## Edit and save

- Retrieve the current stored Traspion content and its revision before editing it. Edits in ChatGPT's native view remain local until the user explicitly approves saving the complete revised content to Traspion.
- Show the proposed cont

Preview of the first 4,000 characters. Read full instructions →