WAO — Waltrump AI Orchestrator / Controlled Beta Access
Know what can be reviewed before you design the evaluation.
Explore 36 capabilities within the WAO Controlled Beta Program. Availability varies by provider, model, operation, modality, region and project. Selected capabilities require project-level activation and customer-managed BYOK.
Can this application or proposal-only agent complete representative scenarios safely?
Evidence
Versioned scenario, bounded trace and human-review evidence
Credential boundary
Customer-managed provider credential encrypted in the exact project is required only for approved provider execution
Provider/model boundary
Provider-neutral; exact combinations are separately qualified · Workload-selected and entitlement controlled
BYOK required
Yes — only after exact project activation
Availability
Limited Controlled Access
Execution dependency
exact project byok and tuple activation for provider or agent runs
Evidence freshness
Reviewed 2026-09-10; exact workload evidence may be newer
Known limitation
Ten governed pack definitions are reviewable. Three owner-operated end-to-end pack runs remain an acceptance gate; installation alone executes nothing.
Does the agent complete the task safely with auditable tool use?
Evidence
Capability-specific evidence and known limitations
Credential boundary
Customer-managed provider credential encrypted in the exact project is required only for approved provider execution
Provider/model boundary
One exact Google Gemini proposal-only agent tuple · Exact model/version confirmed during controlled access review
BYOK required
Yes — only after exact project activation
Availability
Limited Controlled Access
Execution dependency
exact project byok and tuple activation proposal only
Evidence freshness
Reviewed 2026-09-10; exact workload evidence may be newer
Known limitation
One exact Google Gemini text-to-text agent.run proposal path has controlled-beta certification with an accepted limited live case. WAO never executes a proposed tool automatically; bounded human approval remains required.
Does speech or realtime interaction meet accuracy, latency and consent expectations?
Evidence
Capability-specific evidence and known limitations
Credential boundary
Customer-managed provider credential encrypted in the exact project is required only for approved provider execution
Provider/model boundary
Selected exact OpenAI speech and transcription tuples · Exact model/version confirmed during controlled access review
BYOK required
Yes — only after exact project activation
Availability
Limited Controlled Access
Execution dependency
exact project byok and tuple activation
Evidence freshness
Reviewed 2026-09-10; exact workload evidence may be newer
Known limitation
Selected exact OpenAI speech and transcription tuples have controlled-beta certification. Realtime interaction, voice cloning and unlisted audio operations are not enabled.
Customer-managed provider credential encrypted in the exact project is required only for approved provider execution
Provider/model boundary
Provider-neutral; exact combinations are separately qualified · Workload-selected and entitlement controlled
BYOK required
Yes — only after exact project activation
Availability
Limited Controlled Access
Execution dependency
exact project byok and tuple activation for live runs
Evidence freshness
Reviewed 2026-09-10; exact workload evidence may be newer
Known limitation
Results apply only to the tested workload, provider, model, and evidence window. A live run needs exact project approval and customer-managed credentials.
Capability-specific evidence and known limitations
Credential boundary
No provider credential is needed unless a separately approved workflow executes a provider
Provider/model boundary
Provider-neutral; exact combinations are separately qualified · Workload-selected and entitlement controlled
BYOK required
No for catalog review
Availability
Limited Controlled Access
Execution dependency
none
Evidence freshness
Reviewed 2026-09-10; exact workload evidence may be newer
Known limitation
Review visibility does not enable provider execution. External use requires accepted review terms and a separately authorized exact project/provider tuple.
Does generated or edited imagery meet the task, safety and review expectations?
Evidence
Capability-specific evidence and known limitations
Credential boundary
Customer-managed provider credential encrypted in the exact project is required only for approved provider execution
Provider/model boundary
Selected exact OpenAI and Google Gemini tuples · Exact model/version confirmed during controlled access review
BYOK required
Yes — only after exact project activation
Availability
Limited Controlled Access
Execution dependency
exact project byok and tuple activation
Evidence freshness
Reviewed 2026-09-10; exact workload evidence may be newer
Known limitation
Selected exact OpenAI and Google Gemini image generation and editing tuples have controlled-beta certification. Execution remains default-off, project scoped and artifact governed; this does not cover every model or image operation.
Which exact provider, model, operation and modality path can be reviewed for activation?
Evidence
Normalized execution metadata, artifact references and exact tuple evidence
Credential boundary
Customer-managed provider credential encrypted in the exact project is required only for approved provider execution
Provider/model boundary
Selected exact OpenAI, Anthropic, Google Gemini, Mistral and OpenRouter tuples · Exact model/version confirmed during controlled access review
BYOK required
Yes — only after exact project activation
Availability
Limited Controlled Access
Execution dependency
exact project byok and tuple activation
Evidence freshness
Reviewed 2026-09-10; exact workload evidence may be newer
Known limitation
Selected exact tuples have controlled-beta certification; not every provider, model, modality, operation, account or region is qualified, and execution remains default-off.
Does the video workflow preserve temporal, coverage and artifact evidence?
Evidence
Capability-specific evidence and known limitations
Credential boundary
Customer-managed provider credential encrypted in the exact project is required only for approved provider execution
Provider/model boundary
One exact Google Gemini preview video-generation tuple · Exact model/version confirmed during controlled access review
BYOK required
Yes — only after exact project activation
Availability
Limited Controlled Access
Execution dependency
exact project byok and tuple activation
Evidence freshness
Reviewed 2026-09-10; exact workload evidence may be newer
Known limitation
One exact Google Gemini preview video-generation tuple is certified only for a bounded 720p, eight-second, single-output path. It does not include 4K, extension, cancellation or every video operation.
How can an authorized user send selected browser content into a governed WAO record?
Evidence
Explicit submission receipt and governed destination record
Credential boundary
No provider credential is needed unless a separately approved workflow executes a provider
Provider/model boundary
Provider-neutral; exact combinations are separately qualified · Workload-selected and entitlement controlled
BYOK required
No for catalog review
Availability
Limited Controlled Access
Execution dependency
none
Evidence freshness
Reviewed 2026-09-10; exact workload evidence may be newer
Known limitation
The extension uses explicit preview, redaction, classification and destination selection. It is not publicly distributed and never enables provider execution.
Certification, review and execution are different gates.
A capability may have accepted evidence while customer execution stays off. Exact provider, model, operation, project, BYOK, quota and expiry checks still apply.
01
CONTROLLED_BETA
The scoped capability has controlled acceptance evidence and remains subject to quotas and limitations.
02
REVIEW_AVAILABLE
The workflow can be reviewed inside an approved customer scope; this is not global activation.
03
REQUIRES_ACTIVATION + REQUIRES_BYOK
Live provider execution needs an exact project tuple grant and an encrypted customer-managed credential.
04
CONTROLLED_DISTRIBUTION
The artifact can be supplied through an approved path but is not a public download.
05
NOT_YET_ENABLED / UNAVAILABLE
No customer activation is offered for that capability today.
06
DEGRADED
An available path has an active operational limitation; follow the stated safe next action.