Using Vydra with OpenClaw

Prerequisites

• ✓A Vydra account with an API key that starts with `vydra_live_...` so you can call their API.
• ✓An existing OpenClaw project where you can edit the agents and messages configuration.
• ✓Access to a shell where you can run `openclaw` commands and export environment variables.

Steps

1. 1

   Run Vydra onboarding in OpenClaw

   Start by letting OpenClaw’s bundled Vydra plugin walk you through auth. The onboarding flow wires up the provider using your API key so you do not have to hand-edit config first.

   bashCopy

   openclaw onboard --auth-choice vydra-api-key

2. 2

   Set the Vydra API key via environment variable

   If you prefer env-based configuration or run OpenClaw in a non-interactive environment, set `VYDRA_API_KEY` directly. ai/api/v1` to avoid auth issues on redirects.

   bashCopy

   export VYDRA_API_KEY="vydra_live_..."

3. 3

   Configure Vydra as the default image generation provider

   Wire `vydra/grok-imagine` into your agent defaults so image tools route through Vydra. This sets the primary image model for any agent that does not override `imageGenerationModel` explicitly.

   jsonCopy

   {
     agents: {
       defaults: {
         imageGenerationModel: {
           primary: "vydra/grok-imagine",
         },
       },
     },
   }

4. 4

   Configure Vydra as the default video generation provider

   Next, point OpenClaw’s video generation to Vydra’s registered models. `vydra/veo3` handles text-to-video, while `vydra/kling` handles image-to-video using a remote image URL.

   jsonCopy

   {
     agents: {
       defaults: {
         videoGenerationModel: {
           primary: "vydra/veo3",
         },
       },
     },
   }

5. 5

   Set Vydra as the speech synthesis provider

   Enable Vydra’s ElevenLabs-backed TTS route for your messages. This config tells OpenClaw to use Vydra for TTS, passing your `VYDRA_API_KEY` and a known-good default voice that returns MP3 audio.

   jsonCopy

   {
     messages: {
       tts: {
         provider: "vydra",
         providers: {
           vydra: {
             apiKey: "${VYDRA_API_KEY}",
             voiceId: "21m00Tcm4TlvDq8ikWAM",
           },
         },
       },
     },
   }

6. 6

   Run Vydra video live tests

   Once configuration is in place, run the bundled live tests to verify text-to-video and image-to-video flows. These tests hit `vydra/veo3` and `vydra/kling` using a remote image URL fixture so you can confirm end-to-end behavior.

   bashCopy

   OPENCLAW_LIVE_TEST=1 \
   OPENCLAW_LIVE_VYDRA_VIDEO=1 \
   pnpm test:live -- extensions/vydra/vydra.live.test.ts

7. 7

   Override the Kling image URL for live tests when needed

   If the default remote image fixture is not appropriate for your environment, override it with your own URL. This is useful when you want to test Kling against a specific reference image hosted on your own infrastructure.

   bashCopy

   export OPENCLAW_LIVE_VYDRA_KLING_IMAGE_URL="https://example.com/reference.png"

Configuration

Troubleshooting

export OPENCLAW_LIVE_VYDRA_KLING_IMAGE_URL="https://example.com/reference.png"

Frequently asked questions