For AI agents

A skill gives your coding agent the instructions it needs to build with WeGen: discover models, upload owned references, submit with a budget, poll tasks, and save outputs.

InstallCopy Anchor Link

Run this in your project directory with Node.js installed:

npx skills add https://docs.wegen.art

Choose your coding agent and installation scope in the installer. The site publishes the letsgen-generation skill using standard well-known skill discovery. The skill lives with these docs in the Character AI repository and is published alongside the release documentation.

If your agent uses the terminal, install the Lets Gen CLI. It supports JSON output, request previews, durable recovery, and its own bundled agent skill. The docs-hosted skill below covers both CLI workflows and direct HTTP integrations.

Preview available skills without installing:

npx skills add https://docs.wegen.art --list

Give your agent accessCopy Anchor Link

Create a personal key in WeGen → API keys, with read/generate scopes and a monthly Gem cap. Store it as LETSGEN_API_KEY in your shell or secret manager, then start the agent from that environment. Use a secure prompt or platform secret settings to enter the value; never paste it into your agent conversation or source code.

The API base URL is https://wegen.art. This skill teaches agents to call the generation API; the text endpoint supports a chat-completions subset and does not provide the full protocols needed to switch a coding agent's own inference backend.

Ask for an outcomeCopy Anchor Link

Add a server-side image generation feature. Discover the current models, use one output, and require my confirmation before any live generation test. My per-request ceiling is 10 Gems.

Build a speech integration using my owned voice. Persist request identities and task IDs so a reload cannot create duplicate generations.

Generate one approved image for my project and save it to ./public. Use at most 10 Gems. Ask me if the selected configuration needs more.

Installing the skill does not itself make API calls or spend Gems. A live upload can process media; a live generation or extraction request spends account allowance. The agent should obtain the user's intended spending budget and respect the key's cap.

What the agent doesCopy Anchor Link

1. Discover current model IDs and read the relevant reference.
2. Confirm the requested output, inputs, and budget.
3. Upload only required references and keep returned owned IDs.
4. Persist a stable request identity and exact body before submitting.
5. Poll a media task or consume text/extraction, preserving uncertain identities.
6. Download successful outputs locally and report IDs and actual reported charges.

Read Agent workflow for integration details and Troubleshooting for setup failures.