dlazy-search_video

English · 中文

Video search tool: queries Pixabay video API by keywords and returns stock video URLs and metadata for footage sourcing.

Trigger Keywords

• search_video

Authentication

All requests require a dLazy API key. The recommended way to authenticate is:

dlazy login

This runs a device-code flow (also works in remote shells) and automatically saves your API key to the local CLI config — no manual copy/paste required.

Alternative: Set the Key Manually

If you already have an API key, you can save it directly:

dlazy auth set YOUR_API_KEY

The CLI saves the key in your user config directory (~/.dlazy/config.json on macOS/Linux, %USERPROFILE%\.dlazy\config.json on Windows), with file permissions restricted to your OS user account. You can also supply the key per-invocation via the DLAZY_API_KEY environment variable.

Getting Your API Key Manually

1. Sign in or create an account at dlazy.com
2. Go to dlazy.com/dashboard/organization/api-key
3. Copy the key shown in the API Key section

Each key is scoped to your dLazy organization and can be rotated or revoked at any time from the same dashboard.

About & Provenance

• CLI source code: github.com/dlazyai/cli
• Maintainer: dlazyai
• npm package: @dlazy/cli (pinned to 1.0.9 in this skill's install spec)
• Homepage: dlazy.com

You can install on demand without persisting a global binary by running:

npx @dlazy/[email protected] \x3Ccommand>

Or, if you prefer a global install, the skill's metadata.clawdbot.install field declares the exact pinned version (npm install -g @dlazy/[email protected]). Review the GitHub source before installing.

How It Works

This skill is a thin client over the dLazy hosted API. When you invoke it:

• Prompts and parameters you provide are sent to the dLazy API endpoint (api.dlazy.com) for inference.
• Any local file paths you pass to image / video / audio fields are uploaded to dLazy's media storage (files.dlazy.com) so the model can read them — the same flow as any cloud-based generation API.
• Generated output URLs returned by the API are hosted on files.dlazy.com.

This is the standard SaaS pattern; the skill itself does not access network or filesystem resources beyond what the dLazy CLI already handles. See dlazy.com for the full service terms.

Usage

CRITICAL INSTRUCTION FOR AGENT: Execute dlazy search_video to get the result.

dlazy search_video -h

Options:
  --query [query]                      Search Query
  --videoType [videoType]              Video Type [default: all] (choices: "all", "film", "animation")
  --category [category]                Category (choices: "backgrounds", "fashion", "nature", "science", "education", "feelings", "health", "people", "religion", "places", "animals", "industry", "computer", "food", "sports", "transportation", "travel", "buildings", "business", "music")
  --minDuration [minDuration]          Min Duration (s)
  --maxDuration [maxDuration]          Max Duration (s)
  --page [page]                        Page [default: 1]
  --perPage [perPage]                  Results Per Page [default: 10]
  --dry-run                            Print payload + cost estimate without calling API
  --no-wait                            Return generateId immediately for async tasks
  --timeout \x3Cseconds>                  Max seconds to wait for async completion (default: "1800")
  -h, --help                           display help for command

Any flag also accepts pipe references — - (auto-pick from upstream stdin), @N (n-th output), @N.path (jsonpath into output), @* (all primary values), @stdin / @stdin:path (whole envelope). See dlazy --help for details.

Output Format

{
  "ok": true,
  "result": {
    "tool": "search_video",
    "modelId": "search_video",
    "outputs": [
      {
        "type": "json",
        "id": "o_xxxxxxxx",
        "value": {}
      }
    ]
  }
}

Async tasks (when --no-wait is passed) return outputs: [] and a task: { generateId, status } field instead. Use dlazy status \x3CgenerateId> --wait to poll.

Examples

dlazy search_video --prompt 'prompt content'

Error Handling

AGENT CRITICAL INSTRUCTION:

1. If the execution result returns code: "insufficient_balance", you MUST explicitly inform the user that their credits are insufficient and guide them to recharge: https://dlazy.com/dashboard/organization/settings?tab=credits
2. If the execution result returns code: "unauthorized" or indicates missing API key, you MUST inform the user to get their API key from https://dlazy.com/dashboard/organization/api-key and save it using dlazy auth set \x3Ckey> and resume the task.

Tips

Visit https://dlazy.com for more information.