Connecting Straker Dubbing to a Native IBM watsonx Orchestrate Agent

Attach Straker Dubbing to a native agent after subscribing from the Agent Catalog. Audience: WXO admins / agent builders.

Prerequisites

1. IBM watsonx Orchestrate instance with Agent Catalog access.

2. Agent Builder permissions on the target instance.
3. Subscription to Straker Dubbing from the Agent Catalog (billing tier provisioned with subscription — see Pricing).
4. At least one native agent to act as orchestrator. Create one via Agent Builder → Create new agent → Native if needed.

Why a native agent is requiredExternal agents cannot be chatted with directly — they must be attached to a native agent as collaborators (IBM Agent Connect).

Customer chat surfaces talk to a native agent first; the native agent delegates dubbing turns to Straker Dubbing.

Step 1 — Open your native agent

1. Sign in to your WXO instance.
2. Open Agent Builder.
3. Open the native agent to extend with dubbing.

Step 2 — Add Straker Dubbing as collaborator

1. Open Collaborators (or Agents / Skills — naming varies by release).
2. Click Add collaborator and search for Straker Dubbing.
3. Select it (straker_dubbing) and click Add.

No extra authentication on your side — Straker manages the BEARER_TOKEN WXO uses for /chat/completions.

Step 3 — Update native agent instructions

Example routing instructions:

You are a Straker-enabled assistant.  If the user asks to dub a video, 
translate a video into another language, or lip-sync a video, delegate 
the turn to the "straker_dubbing" collaborator.  If the user asks for 
the status or progress of a dubbing job, also delegate to "straker_dubbing".  
For all other requests, answer directly.Step 4 — Save and publish

Save and publish (or deploy) the native agent to your end-user chat surface.

Step 5 — Smoke test

Dub https://example.com/sample-video.mp4 into Japanese

Expect a Job ID within a few seconds. Dubbing is long-running — see Usage. If no Job ID appears, see Support.

https://dubbing-ai.straker.ai/