Venice Mod

Venice wallet-auth Capability. Provides the original Intel-compatible LLM surfaces plus the broader Venice x402/no-API-key endpoint set:

• cap.llm.chat, cap.llm.search, cap.social.search.x
• cap.llm.responses, cap.llm.embed
• cap.image.generate, cap.image.edit, cap.image.upscale
• cap.audio.speech, cap.audio.transcribe, cap.audio.generate
• cap.video.generate, cap.video.transcribe
• cap.web.search, cap.web.scrape, cap.document.parse, cap.crypto.rpc

These endpoints are SIWE-gated with Venice's X-Sign-In-With-X header and x402-priced where Venice charges. The mod uses the host's cap.x402.pay + cap.identity.siwe capabilities — it never holds a signing key directly.

Install

moltbank mod install venice

Lifecycle

moltbank mod setup venice
moltbank mod doctor venice --json
moltbank mod estimate venice --json
moltbank mod status venice --json

Used as a capability provider

Other mods call Venice transparently via the SDK:

import { useLLM, useSocial } from '@moltbankhq/mod-sdk';

const llm = useLLM();
const r = await llm.chat({ messages: [...], model: 'grok-x-native' });

const social = useSocial();
const x = await social.searchX({ query: 'x402 protocol launches', limit: 5 });

The host CLI resolves each capability to whichever mod is installed and pinned. Pin Venice as the preferred provider with:

moltbank mod prefer cap.llm.chat=venice --json
moltbank mod prefer cap.social.search.x=venice --json

Broader Venice surfaces can be called through the capability layer or directly for debugging:

moltbank cap call cap.llm.responses responses --mod-arg body='{"model":"grok-x-native","input":"hello"}' --json
moltbank cap call cap.image.generate image-generate --mod-arg body='{"model":"hidream","prompt":"diagram of x402"}' --json
moltbank cap call cap.web.search web-search --mod-arg body='{"query":"x402 wallet auth"}' --json
moltbank cap call cap.crypto.rpc crypto-rpc --mod-arg network=base --mod-arg method=eth_blockNumber --json

Binary outputs, such as generated speech or background-removed images, are written under the mod run's artifact directory and returned as { artifactPath, contentType, sizeBytes }.

crypto-rpc is read-only by default. Chain-write methods such as eth_sendRawTransaction require allowCryptoWrites: true in config and confirmCryptoWrite=true on the call.

The raw request command is intentionally allowlisted to documented Venice wallet-auth routes; it rejects arbitrary Venice API paths and API-key/admin/billing surfaces.

Caveats

• Venice prepaid x402 credits are tracked on Venice's own ledger and are not usable as signer-wallet balance for third-party x402 merchants. See openclaw-npm/src/core/x402.ts:917-945 for the actionable error the host emits when this confusion surfaces.
• The mod's setup currently picks grok-x-native as the default model unless VENICE_DEFAULT_MODEL is set or the user overrides via mod setup.