Govilo To Go

Turn any file into a paid unlock link — one command to package, upload, and collect crypto payments. The last mile of automation: from creation to monetization.

Before Running

Always ask the user for these values before executing the CLI — never guess or use placeholders:

1. title — What is the product name?
2. price — How much to charge (in USDC)?
3. description — Short description of the product (optional, but always ask)

CLI Command

Requires uv. See [references/setup-guide.md](references/setup-guide.md) for install instructions.

Run from this skill's base directory. Use a dedicated env file containing only GOVILOAPIKEY (and optionally SELLER_ADDRESS). Never point --env-file at a project .env that contains unrelated secrets.

cd <skill_base_directory>
uv run --env-file <path_to>/.env.govilo create-link \
  --input <path>         \
  --title "Product Name" \
  --price "5.00"         \
  --address "0x..."      \
  --description "optional"

If no .env.govilo exists, create one before running:

GOVILO_API_KEY=sk_live_xxx
SELLER_ADDRESS=0x...

--input accepts ZIP file, folder, or individual files (repeatable). Non-ZIP inputs are auto-packaged.

All output is JSON {"ok": true/false, ...} with exit code 1 on failure.

Parameters

Workflow

1. Validate config (API Key + seller address)
2. Package inputs → ZIP (if not already ZIP)
3. POST /api/v1/bot/uploads/presign → get uploadurl + sessionid
4. PUT upload_url → upload ZIP to R2
5. POST /api/v1/bot/items → get unlock_url

File Limits

• Max ZIP size: 20 MB
• Max files in ZIP: 20

Setup

Two values are required:

[govilo.xyz]: https://govilo.xyz/

*SELLER_ADDRESS can also be passed via --address CLI parameter.

See [references/setup-guide.md](references/setup-guide.md) for step-by-step registration and wallet setup instructions.

API Reference

See [references/bot-api-quick-ref.md](references/bot-api-quick-ref.md) for Bot API endpoints and error codes.