Configure premium capabilities without rebuilding the operating system. API keys and platform credentials belong in Oracle OCI Secret Management; this console retains references only. Provider calls, rendering, public publishing, monetization and automation remain OFF until you configure and enable them.
Ready — store actual keys in OCI Vault, then attach only a masked vault reference through the signed owner API. No raw provider or publishing credential is saved in Postgres, GitHub or the browser.
Read verified platform metrics after connection.
Schedule production runs only when explicitly enabled.
Generate premium scenes after provider and budget setup.
Send approved assets through isolated draft-first gateways.
Create premium output masters after setup.
Track and enable verified business routes when approved.
Create Griot Sound masters after provider and rights setup.
Public distribution controlled separately from draft delivery.
Create private or release masters only when enabled.
Generate scripts and structured production decisions after provider setup.
Generate or import approved voices only after consent and configuration.
Set budgets through owner-authorized controls before enabling paid production.