Venice.ai Media Generation
PassAudited by ClawScan on May 12, 2026.
Overview
This appears to be a coherent Venice.ai media-generation plugin, but it will use your Venice API key, send prompts and selected images to Venice.ai, and the optional source-install URL should be verified.
This plugin looks purpose-aligned for Venice.ai image and video generation. Before installing, make sure you are comfortable with OpenClaw using your Venice API key, sending selected prompts/images to Venice.ai, and potentially consuming account quota. Prefer the ClawHub install path unless you have verified the optional source repository yourself.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Media requests can consume your Venice.ai account quota or billing using the same key used for Venice text models.
The plugin retrieves the configured Venice provider API key and sends it as a Bearer token to Venice API calls. This is disclosed and purpose-aligned, but it means the plugin can use the user's Venice account authority.
resolveApiKeyForProvider({ provider: "venice", ... }); ... Authorization: `Bearer ${apiKey}`Use a Venice API key you are comfortable delegating to OpenClaw, monitor provider usage, and revoke or rotate the key if you stop using the plugin.
Private or sensitive images and prompts you provide for generation or editing may be sent to Venice.ai for processing.
For image-to-video requests, the plugin embeds an uploaded image as base64 data in the request body sent to the Venice video API. This matches the advertised feature, but selected images and prompts leave the local environment.
requestBody.image_url = `data:${mimeType};base64,${firstImage.buffer.toString("base64")}`;Only upload media you are comfortable sending to Venice.ai, and review Venice.ai's data-handling terms if the images or prompts are sensitive.
If you follow the from-source instructions without checking, you could install code from a repository different from the one identified in the registry metadata.
The optional from-source install command clones a repository named openclaw-venice-ai, while the supplied source metadata names acwilan/openclaw-venice-media. This may be a documentation or repository rename issue, but users should verify provenance before installing from source.
git clone https://github.com/acwilan/openclaw-venice-ai.git
Prefer the ClawHub install path, or manually verify the GitHub repository, owner, and package contents before running npm install or plugin install from source.