How spending works
MediaThrive MCP uses ordinary MediaThrive product credits and billing. An administrator sets a monthly MCP limit and a per-job limit in team settings. Both limits must allow the requested operation, and normal billing eligibility must also pass. A zero budget prevents paid generation.
Once you authorize an assistant to generate audio or render video, it can spend automatically within those limits. MCP does not add a mandatory confirmation before every paid call. Your assistant or organization may still require tool approval.
The cost estimate shows the requested maximum cost and remaining MCP budget without spending or reserving credits. A paid request places a temporary hold. Final measured usage is billed through normal product billing, and unused reserved capacity is released. The hold is not an additional product charge.
Monthly periods follow UTC calendar months. Active holds count against available capacity, including unresolved work from an earlier month. Lowering a limit does not cancel work or erase existing commitments.
For narration, the estimate uses the maximum delivered duration you request. Longer generated audio is trimmed to that cap before delivery and billing. This can cut off narration, so prepare text and scene duration accordingly.
Permissions and team selection
| Permission | Access |
|---|---|
media:read | Inspect team media and catalogues, estimate cost and check operations. |
media:write | Create and edit drafts and attach existing media. |
media:generate | Start paid narration generation and video rendering. |
Each connection is bound to your user and one selected team. Access is checked against current membership, role permissions, granted scopes and connection status. Connecting does not grant administrator rights or access to another team’s media.
For another team, start a new connection and choose that team during consent. Do not share access or refresh tokens with teammates. Each person should connect through their own MediaThrive account.
Manage or revoke access
Open the team’s Settings → AI connections page to inspect connections. You can revoke your own connections; a team administrator can revoke team connections and manage budgets. Removing membership or relevant permissions also prevents subsequent use.
Revocation stops future access. It does not retract information already returned to the assistant or undo media processing that already started. Review your AI provider’s data handling and your organization’s rules before connecting sensitive material.
Access tokens are short-lived and refresh automatically in compatible clients. Connections expire after 30 days and may require a fresh sign-in. Reusing an old rotated refresh token revokes that connection family.
Reliable paid requests
A paid operation has a durable operation ID. Your assistant should keep it and check get_operation until the outcome is clear. Identical retries reuse the same idempotency key, which returns the existing operation instead of creating a duplicate.
A timeout is not proof that generation failed. If an outcome is unknown, do not start a replacement job or change the idempotency key. The budget hold remains while MediaThrive reconciles provider processing and billing. Contact support with the operation ID; never send tokens or authorization callback URLs.
Scene text, news and media metadata are content, not instructions that authorize additional assistant actions. Scope requests to the work you intend and use read-only access when you only need inspection.