Approve paid actions and review results
Apply current delegated authority, estimate before spending, use idempotency keys, and stop for review when intent or output is uncertain.
On this page
Connecting an agent does not approve paid execution. Unless the current instruction explicitly delegates autonomous paid work for the relevant scope, the agent should present the estimate and obtain approval before creating a generation or running a workflow.
Approval is an operating instruction, not a separate token or server-side approval gate. Current organization membership, role, and capabilities still determine whether each tool call is allowed.
Apply current delegated authority
Membership, role, and capabilities are checked on every requestgenerations:readDiscover and inspect generationDenied when the current user no longer has this capability.playground:runEstimate, create, or retry generationDenied when the current user no longer has this capability.workflows:runPrepare a local media uploadDenied when the current user no longer has this capability.generations:cancelCancel generationDenied when the current user no longer has this capability.workflows:read, workflows:manage, workflows:runRead, edit, or run workflowsDenied when the current user no longer has this capability.publishing:read, publishing:manageRead or edit publishing draftsDenied when the current user no longer has this capability.publishing:scheduleSchedule, reschedule, or cancelDenied when the current user no longer has this capability.publishing:analytics:readRead publishing analyticsDenied when the current user no longer has this capability.Estimate, then confirm paid work
Load the current contract and construct the intended input.
Price the exact request before any generation or workflow run.
Present cost unless autonomous paid execution was explicitly delegated for this scope.
Approval is an instruction between the user and agent. Connection is not approval, and a read-only connection check never requires paid work.
Give every paid write an intent key
Generation creates and retries, workflow runs, and workflow retries require caller keys.
Reuse a key only for the same call after a timeout or uncertain response.
Publishing mutations have no key. Re-read state before repeating them.
Stop at review boundaries
OutputInspect assets, structured results, final usage, and errors before another paid action.WorkflowRe-read the workflow and run before edits, pins, retries, or another run.PublishingConfirm account, media, caption, exact time, and timezone before schedule changes.Manual reviewStop automation, preserve the resource ID, and return control to the user.