Castingwords
for LuumenAI
Order human transcription, check balances, and pull finished transcripts
Connect CastingWords and your agent can see what transcription work is in flight without leaving the terminal. Check the prepay balance, look up service tiers and pricing, pull a finished transcript as text or rtf, and confirm which webhook URL is registered. Placing orders and changing webhooks are approved steps, previewed before they run.
The Castingwords toolbox
9 tools: 4 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Prepay BalanceRetrieve the current prepay balance for the account.
- ReadGet TranscriptRetrieve the transcript for a given audiofile in the requested format (txt, doc, rtf, or html).
- ReadGet registered webhook URLRetrieve the currently registered webhook URL for account notifications.
- ReadList Available SKUsRetrieves all available CastingWords transcription service SKUs with pricing.
- WriteCancel and Refund Audio FileCancel an ordered audio file and issue a refund if applicable. Approval by default
- WriteOrder TranscriptCreate a transcription order for audio/video files at publicly accessible URLs. Approval by default
- WriteOrder UpgradesOrder an upgrade for a specific audio file. Approval by default
- WriteRegister WebhookRegisters a webhook URL to receive CastingWords event notifications. Approval by default
- WriteTest Webhook CallRequest a test webhook call for a specific event type. Approval by default
One prompt, start to finish
What a governed Castingwords run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — cancel and refund audio file, order transcript, order upgrades, register webhook, and more — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Castingwords — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task status
AffindaRead parsed documents, collections, and annotations — change them with approval
Agent MailGive the agent its own mailbox for reading threads and sending updates
AI/ML APIInspect assistants, threads, and runs — and change them as approved stepsPut Castingwords to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.