Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.venice.ai/llms.txt

Use this file to discover all available pages before exploring further.

Venice Skills is the canonical collection of Agent Skills for the Venice API. Each skill is a self-contained folder with a SKILL.md that an LLM agent loads on demand to work correctly against a specific surface area of the API.

GitHub: veniceai/skills

19 skills covering the full Venice API. MIT licensed. Kept in sync with the public swagger.yaml.

19 Skills

One per Venice API surface area

Runtime-agnostic

Works with Claude Code, Cursor, Codex, OpenCode, Hermes, Cline, and any other Agent Skills host

Spec-synced

Derived from Venice’s OpenAPI spec, with CI checks for drift

​
Why skills?

Without skills, your agent has to discover Venice’s quirks the hard way: venice_parameters, model-type enums, 402 payment-required flows, video queue/retrieve lifecycle, character slugs, and so on. Skills bundle that knowledge into focused, on-demand files so the agent only loads what it needs for the current task. Each SKILL.md includes:
  • The endpoint(s) it covers
  • Required headers, parameters, and response shapes
  • A curl example plus a minimal SDK example
  • A “gotchas” section with the things real integrators trip over

​
Skill catalog

SkillCovers
venice-api-overviewBase URL, auth modes, response headers, pricing model, versioning
venice-authBearer API keys + SIWE / x402 wallet authentication
venice-chat/chat/completions with venice_parameters, multimodal, tools, reasoning, streaming
venice-responses/responses, the OpenAI-compatible Responses API (Alpha)
venice-embeddings/embeddings models, encoding formats, dimensions
venice-image-generate/image/generate, /images/generations, /image/styles
venice-image-edit/image/edit, /image/multi-edit, /image/upscale, /image/background-remove
venice-audio-speech/audio/speech TTS models, voices, formats, streaming
venice-audio-music/audio/quote, /audio/queue, /audio/retrieve, /audio/complete
venice-audio-transcription/audio/transcriptions with Whisper, Parakeet, Scribe, Wizper, xAI STT
venice-video/video/* generation + transcription
venice-models/models, /models/traits, /models/compatibility_mapping
venice-characters/characters* + venice_parameters.character_slug
venice-api-keysCRUD /api_keys, rate limits, Web3 key generation
venice-billing/billing/balance, /billing/usage, /billing/usage-analytics
venice-x402/x402/* wallet credits, USDC on Base
venice-crypto-rpc/crypto/rpc/* JSON-RPC proxy with 1×/2×/4× pricing
venice-augment/augment/text-parser, /augment/scrape, /augment/search
venice-errorsError shapes, 402 payment required, 422 content policy, 429 rate limits, retry strategy

​
Install

Each skill is just a folder with a SKILL.md that starts with YAML frontmatter: 
---
name: venice-chat
description: When the agent should load this skill and what's in it
---
Drop the skills/ folder (or any subset) into whichever path your runtime watches.
Project-local:
git clone https://github.com/veniceai/skills.git
cp -r skills/skills/* .claude/skills/
Or global, for every project on your machine:
git clone https://github.com/veniceai/skills.git ~/src/venice-skills
ln -s ~/src/venice-skills/skills ~/.claude/skills/venice

​
Path reference

RuntimeProject-localGlobal
Claude Code.claude/skills/~/.claude/skills/
Codex.codex/skills/~/.codex/skills/ (or $CODEX_HOME/skills/)
OpenCode.opencode/skills/ (also .claude/skills/, .agents/skills/)~/.config/opencode/skills/
Hermes Agent$HERMES_OPTIONAL_SKILLS_DIR~/.hermes/skills/
Cursor.cursor/skills/~/.cursor/skills/
Cline.clinerules/skills/n/a
Other runtimes.agents/skills/ (convention)~/.agents/skills/
Runtimes that define extra frontmatter fields (version, platforms, metadata.*, compatibility, …) are required by spec to ignore unknown fields, so the same skill file works everywhere without forks.

​
As a git submodule

If you want pinned versions in your own repo: 
git submodule add https://github.com/veniceai/skills.git vendor/venice-skills
Then symlink or copy the subsets you want into your agent’s skill path.

​
How agents load them

The agent discovers each SKILL.md by its frontmatter name and description. When the user asks something that matches a skill’s purpose, the agent loads that one file into context (not the whole catalog), so the prompt stays small and the answer stays accurate. For example, an agent that needs to generate music will load venice-audio-music and immediately know:
  • That music goes through the queue/retrieve/complete lifecycle, not a synchronous endpoint
  • Which models are available and their per-minute pricing
  • How to call /audio/quote for cost estimation first
  • What the polling backoff should look like
Without the skill, the agent might try to call /audio/speech for music and get a useless response.

​
Authoring a new skill

  1. Copy template/ to skills/<your-skill>/.
  2. Fill in the frontmatter and body. Keep description concrete, since it’s what an agent uses to decide when to load the skill.
  3. Link related skills at the bottom for cross-navigation.
  4. Open a PR against veniceai/skills.
See the repository’s CONTRIBUTING.md for style conventions (short first paragraph, explicit endpoint tables, curl + one SDK example, “gotchas” section, ≤ 500 lines).

​
Resources

GitHub

Source code, contributing guide, and skill template

Venice MCP Server

Pair skills with the official MCP server for runtime tool access

Agent Skills Spec

Learn the underlying format

Venice API Spec

The OpenAPI source of truth these skills are derived from