Agent skill

Inventpay

by LeoYeAI in LeoYeAI/openclaw-master-skills

Accept crypto payments, manage a digital storefront, and track balances through the InventPay REST API

MIT-0Auto-check passedBackend & APIs

Install Inventpay

skills CLI

$ npx skills add LeoYeAI/openclaw-master-skills --skill inventpay -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install LeoYeAI/openclaw-master-skills inventpay --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/inventpay-api .claude/skills/inventpay && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "inventpay" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/inventpay-api into .claude/skills/inventpay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inventpay", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/inventpay-api

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add LeoYeAI/openclaw-master-skills --skill inventpay -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install LeoYeAI/openclaw-master-skills inventpay --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/inventpay-api .agents/skills/inventpay && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "inventpay" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/inventpay-api into .agents/skills/inventpay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inventpay", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add LeoYeAI/openclaw-master-skills --skill inventpay -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install LeoYeAI/openclaw-master-skills inventpay --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/inventpay-api .cursor/skills/inventpay && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "inventpay" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/inventpay-api into .cursor/skills/inventpay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inventpay", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/inventpay-api

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add LeoYeAI/openclaw-master-skills --skill inventpay -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install LeoYeAI/openclaw-master-skills inventpay --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/inventpay-api .gemini/skills/inventpay && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "inventpay" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/inventpay-api into .gemini/skills/inventpay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inventpay", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install LeoYeAI/openclaw-master-skills inventpay

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add LeoYeAI/openclaw-master-skills --skill inventpay -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/inventpay-api .github/skills/inventpay && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "inventpay" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/inventpay-api into .github/skills/inventpay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inventpay", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add LeoYeAI/openclaw-master-skills --skill inventpay -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install LeoYeAI/openclaw-master-skills inventpay --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/inventpay-api .opencode/skills/inventpay && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "inventpay" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/inventpay-api into .opencode/skills/inventpay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inventpay", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: inventpay
GitHub stars: 2.2k
Token cost: ~4.3k tokens
SKILL.md length: 1,297 words
Files: 2
Skills in repo: 1,235
Repo updated: Jul 20, 2026
First seen: Oct 9, 2026
Licence: MIT-0

At a glance

Accept crypto payments, manage a digital storefront, and track balances through the InventPay REST API

Works in 3 steps: Sign up at inventpay.io and go to… → Copy your API key (starts with pk_live_) → Set the environment variable
Tasks that involve REST APIs
SKILL.md covers What this skill does, Quick start, Base URL and Authentication, plus 11 more sections
Reaches inventpay.io and api.inventpay.io; needs INVENTPAY_API_KEY

What it does

Inventpay is an agent skill from LeoYeAI/openclaw-master-skills. Accept crypto payments, manage a digital storefront, and track balances through the InventPay REST API

Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `_meta.json`).

It sits in Backend & APIs, covering REST APIs and Forms and invoices. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT-0.

When your agent uses it

Tasks that involve REST APIs
Tasks that involve Forms and invoices

Example prompts

“/inventpay”

Requirements

A credential in INVENTPAY_API_KEY

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Sign up at inventpay.io and go to Dashboard > Settings
Copy your API key (starts with pk_live_)
Set the environment variable

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- inventpay.io
- api.inventpay.io
Also links to:
- github.com
- npmjs.com
- docs.inventpay.io
- pypi.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- INVENTPAY_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Inventpay loads about 4.3k tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 1,297 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~28
When it runs · the whole SKILL.md, loaded when a task matches: ~4.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT-0 licence (© LeoYeAI). 1,297 words, ~4,347 tokens.

Download SKILL.mdSave it as .claude/skills/inventpay/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: inventpay
description: Accept crypto payments, manage a digital storefront, and track balances through the InventPay REST API
version: 1.0.0
author: jams24
homepage: https://inventpay.io
source: https://github.com/jams24/inventpay-mcp
license: MIT-0
tags: payments, crypto, store, ecommerce, bitcoin, solana, usdt, usdc, invoicing, digital-products, monetization

InventPay Skill

Accept crypto payments, run a digital storefront, and track balances through the InventPay REST API.

What this skill does

This skill teaches your agent how to interact with the InventPay payment platform using direct HTTP requests. No external packages or binaries required — your agent makes standard REST API calls.

Your agent can:

Create crypto payment links and multi-currency invoices (BTC, ETH, LTC, SOL, USDT, USDC)
Set up and manage a digital storefront with automatic product delivery
Manage a key pool for unique license keys per customer
Check balances across all currencies
Track orders and view store analytics

Quick start

Install

bash

openclaw install inventpay

No binaries or packages needed. This skill is instruction-only.

Configure

Sign up at inventpay.io and go to Dashboard > Settings
Copy your API key (starts with pk_live_)
Set the environment variable:

bash

export INVENTPAY_API_KEY="pk_live_your_key_here"

Verify

Ask your agent: "What's my InventPay balance?"

The agent should make a GET request to https://api.inventpay.io/v1/merchant/balance with your API key and return your balances. If you see an auth error, check that INVENTPAY_API_KEY is set and starts with pk_live_.

Base URL

https://api.inventpay.io

Authentication

All authenticated endpoints require:

Header: X-API-Key: <INVENTPAY_API_KEY>
Content-Type: application/json

The API key (pk_live_...) is your main merchant key for all operations: payments, invoices, store, products, orders, and balances.

IMPORTANT: correct endpoint paths

Payment creation is POST /v1/create_payment — NOT /v1/payments
Invoice creation is POST /v1/create_invoice — NOT /v1/invoices or /v1/store/manage/invoices
Balance endpoint is GET /v1/merchant/balance — NOT /v1/balance
Store checkout is POST /v1/store/{slug}/checkout — uses the store URL slug (e.g. "my-store"), NOT a store ID
Do NOT guess or invent endpoint paths. Use ONLY the exact paths listed below.

Important URLs

Store page: https://inventpay.io/store/{slug}
Product page: https://inventpay.io/store/{slug}/product/{productSlug} — the /product/ segment is required
Invoice/payment page: https://inventpay.io/invoice/{paymentId}
Do NOT omit /product/ from product URLs — /store/{slug}/{productSlug} will NOT work

API endpoints

All responses follow the format: { "success": true/false, "data": {...}, "message": "..." }

Payments

Create a fixed-currency payment

Use when you know which cryptocurrency the buyer will pay with.

POST /v1/create_payment
Header: X-API-Key: <INVENTPAY_API_KEY>
Content-Type: application/json

{
  "amount": 50.00,                        // required — payment amount
  "currency": "USDT_BEP20",              // required — BTC, ETH, LTC, USDT_ERC20, USDT_BEP20, SOL, USDC_SOL, USDC_BEP20
  "amountCurrency": "USD",               // optional, default "USDT" — USD, USDT, BTC, ETH, LTC, SOL
  "orderId": "order-123",                // optional — your reference ID (max 100 chars)
  "description": "Payment for service",  // optional (max 500 chars)
  "callbackUrl": "https://your-site.com/webhook",  // optional — webhook for status updates
  "expirationMinutes": 30                // optional, default 30, range 5-1440
}

Response includes: paymentId, amount (crypto amount), currency, address (wallet to pay), invoiceUrl (shareable link), qrCode, expiresAt.

Use /v1/create_payment for single-crypto payments. Use /v1/create_invoice for multi-crypto choice.

Create a multi-currency invoice

Use when you want the buyer to choose which crypto to pay with.

POST /v1/create_invoice
Header: X-API-Key: <INVENTPAY_API_KEY>
Content-Type: application/json

{
  "amount": 100.00,                       // required
  "amountCurrency": "USD",               // optional, default "USDT"
  "orderId": "inv-456",                  // optional
  "description": "Monthly subscription", // optional
  "callbackUrl": "https://your-site.com/webhook",  // optional
  "expirationMinutes": 60                // optional, default 60
}

Response includes: paymentId, invoiceUrl (send this to the buyer), expiresAt, availableCurrencies.

Check payment status

GET /v1/invoice/{paymentId}/status
No authentication required (public endpoint)

Response: { "status": "PENDING", "currentBalance": 0, "confirmations": 0 }

Statuses: PENDING, PROCESSING, COMPLETED, EXPIRED, CANCELLED, FAILED, UNDERPAID.

Balances

Get all balances

GET /v1/merchant/balance
Header: X-API-Key: <INVENTPAY_API_KEY>

Response:

json

{
  "success": true,
  "data": {
    "merchantId": "...",
    "businessName": "...",
    "balances": {
      "balances": [
        {
          "currency": "USDT_BEP20",
          "totalEarned": 812.71,
          "totalWithdrawn": 25.30,
          "totalFees": 1.41,
          "availableBalance": 504.87,
          "lockedBalance": 265.10,
          "pendingBalance": 0
        }
      ],
      "summary": {
        "totalAvailable": 504.92,
        "totalLocked": 265.10,
        "totalPending": 0,
        "totalEarned": 812.77,
        "totalWithdrawn": 25.30,
        "totalFees": 1.41
      }
    }
  }
}

Get balance for a specific currency

GET /v1/merchant/balance/{currency}
Header: X-API-Key: <INVENTPAY_API_KEY>

Currency must be: BTC, ETH, LTC, USDT_ERC20, USDT_BEP20, SOL, USDC_SOL, or USDC_BEP20.

Store management

Create a store

POST /v1/store/manage
Header: X-API-Key: <INVENTPAY_API_KEY>
Content-Type: application/json

{
  "name": "My Digital Store",             // required, 2-100 chars
  "description": "Selling digital goods"  // optional, max 1000 chars
}

Response includes: id, name, slug, url (public store page at inventpay.io/store/{slug}), isActive, product/order counts.

Get your store

GET /v1/store/manage
Header: X-API-Key: <INVENTPAY_API_KEY>

Update your store

PUT /v1/store/manage
Header: X-API-Key: <INVENTPAY_API_KEY>
Content-Type: application/json

{
  "name": "Updated Name",        // optional
  "description": "New desc",     // optional
  "logo": "https://...",         // optional, HTTPS URL
  "banner": "https://...",       // optional, HTTPS URL
  "isPublished": true            // optional
}

Products

Create a product

POST /v1/store/manage/products
Header: X-API-Key: <INVENTPAY_API_KEY>
Content-Type: application/json

{
  "name": "Premium Skill Bundle",         // required, 1-200 chars
  "price": 9.99,                          // required, 0.01-1000000 (in USDT)
  "description": "10 advanced skills",    // optional, max 5000 chars
  "images": ["https://example.com/img.jpg"],  // optional, max 10 URLs
  "stock": 100,                           // optional, omit for unlimited
  "contentType": "GENERAL",              // optional — "GENERAL" (default) or "SKILL"
  "skillContent": "---\nname: ...\n---\n...",  // optional — raw SKILL.md content, only when contentType is "SKILL"
  "digitalContent": {                     // optional — for automatic delivery on payment
    "fileUrl": "https://example.com/bundle.zip",  // download link
    "fileName": "skill-bundle-v2.zip",    // display name
    "instructions": "Extract and copy to your skills folder",
    "licenseKey": "SKILL-PRO-2026",       // access code
    "textContent": "Inline content here"  // or deliver text directly
  }
}

Response includes: id, name, slug, price, isActive, productUrl, contentType, skillMeta.

Digital products auto-deliver after payment via the digitalContent field.

When contentType is "SKILL", the backend automatically parses YAML frontmatter from skillContent and stores it as skillMeta (name, version, author, tags, etc.) for storefront display. The raw skillContent is never exposed publicly — it is delivered to the buyer after payment.

List products

GET /v1/store/manage/products?page=1&limit=20&search=skill
Header: X-API-Key: <INVENTPAY_API_KEY>

Query parameters: page (default 1), limit (default 20, max 50), search (by name).

Update a product

PUT /v1/store/manage/products/{productId}
Header: X-API-Key: <INVENTPAY_API_KEY>
Content-Type: application/json

{
  "name": "Updated Name",      // optional
  "price": 14.99,              // optional
  "description": "...",        // optional
  "stock": 50,                 // optional
  "isActive": true,            // optional
  "contentType": "SKILL",      // optional — "GENERAL" or "SKILL"
  "skillContent": "---\n...",  // optional — raw SKILL.md, only for SKILL type
  "digitalContent": { ... }    // optional
}

Delete a product

DELETE /v1/store/manage/products/{productId}
Header: X-API-Key: <INVENTPAY_API_KEY>

If the product has order history it gets deactivated (soft delete). If no orders exist it gets permanently removed.

Key pool (unique keys per customer)

For products where each buyer gets a unique license key, activation code, or content.

Upload keys

POST /v1/store/manage/products/{productId}/keys
Header: X-API-Key: <INVENTPAY_API_KEY>
Content-Type: application/json

{
  "keys": ["KEY-001", "KEY-002", "KEY-003"],  // required, 1-10000 unique keys
  "label": "Batch #1"                         // optional, max 200 chars
}

Response: { "added": 3, "duplicates": 0 }

List keys

GET /v1/store/manage/products/{productId}/keys?page=1&limit=50&status=AVAILABLE
Header: X-API-Key: <INVENTPAY_API_KEY>

Query: page, limit (max 100), status (AVAILABLE, ASSIGNED, REVOKED).

Get key pool stats

GET /v1/store/manage/products/{productId}/keys/stats
Header: X-API-Key: <INVENTPAY_API_KEY>

Returns: total, available, assigned, revoked, useKeyPool.

Remove all available keys

DELETE /v1/store/manage/products/{productId}/keys
Header: X-API-Key: <INVENTPAY_API_KEY>

Only removes unassigned (AVAILABLE) keys. Assigned keys are preserved.

Orders

List orders

GET /v1/store/manage/orders?page=1&limit=20&status=PAID
Header: X-API-Key: <INVENTPAY_API_KEY>

Query: page, limit (max 50), status (PENDING, PAID, PROCESSING, SHIPPED, COMPLETED, CANCELLED, REFUNDED).

Get order details

GET /v1/store/manage/orders/{orderId}
Header: X-API-Key: <INVENTPAY_API_KEY>

Returns full order with items, payment info, customer details, and delivery status.

Update order status

PUT /v1/store/manage/orders/{orderId}/status
Header: X-API-Key: <INVENTPAY_API_KEY>
Content-Type: application/json

{
  "status": "COMPLETED",           // PROCESSING, SHIPPED, COMPLETED, CANCELLED, REFUNDED
  "notes": "Delivered successfully" // optional, max 500 chars
}

Valid transitions: PAID can go to PROCESSING/SHIPPED/COMPLETED/CANCELLED/REFUNDED. Digital products auto-complete on payment.

Store checkout (public, no auth)

POST /v1/store/{slug}/checkout
Content-Type: application/json

{
  "items": [{ "productId": "prod_...", "quantity": 1, "variant": {} }],
  "customerEmail": "buyer@example.com",
  "customerName": "John Doe",
  "currency": "USDT_BEP20"   // optional
}

Uses the store URL slug (e.g. "my-store"), NOT a store ID.

Store analytics

GET /v1/store/manage/analytics
Header: X-API-Key: <INVENTPAY_API_KEY>

Returns: order counts by status, total/confirmed revenue in USDT, product count, store info.

Agent behavior when creating products

When the user asks to create or add a new product, ALWAYS ask them:

Product name (required)
Price in USDT (required)
Content type — ask: "Is this a regular digital product or a SKILL file (.md)?"
- If SKILL: ask the user to paste or provide the SKILL.md content. Set contentType: "SKILL" and put the raw markdown in skillContent. The backend will auto-parse the YAML frontmatter.
- If regular/general: ask about digital delivery (file URL, license key, instructions, or text content). Set contentType: "GENERAL" or omit it.
Description (optional)
Stock (optional, omit for unlimited)
Images (optional)

Do NOT skip the content type question. This is important because SKILL products get special storefront display (skill badge, version, author, tags) and the raw .md file is delivered to the buyer after payment.

Show full SKILL.md (486 more words)Show less

Example conversations

Creating a payment:

"Create a $25 USDT payment for the logo design"

Agent makes: POST /v1/create_payment with {"amount": 25, "currency": "USDT_BEP20", "description": "Logo design"} and returns the payment link.

Setting up a store:

"Create a store called AI Skill Shop"

Agent makes: POST /v1/store/manage with {"name": "AI Skill Shop"} and returns the store URL.

Adding a product:

"Add a product called Code Review Skill for $8 with download URL https://files.example.com/review-skill.md"

Agent makes: POST /v1/store/manage/products with name, price, and digitalContent.fileUrl.

Adding a skill product:

"Create a skill product called 'SEO Audit Skill' for $5 with this SKILL.md content: ---\nname: seo-audit\nauthor: devtools\nversion: 1.0.0\ntags: [seo, audit]\n---\n\n# SEO Audit\n..."

Agent makes: POST /v1/store/manage/products with name, price, contentType: "SKILL", and skillContent containing the raw markdown.

Checking balance:

"What's my balance?"

Agent makes: GET /v1/merchant/balance and summarizes available amounts per currency.

Checking orders:

"Show me recent paid orders"

Agent makes: GET /v1/store/manage/orders?status=PAID and lists them.

Managing key pool:

"Upload 50 license keys for the Pro Skill product"

Agent makes: POST /v1/store/manage/products/{id}/keys with the keys array.

Selling OpenClaw skills through your store

Practical setup for monetizing premium skill files:

Create your store — agent calls POST /v1/store/manage
Add skill files as products — set contentType: "SKILL", paste the raw SKILL.md into skillContent, set a price. The backend parses frontmatter automatically for the storefront. Alternatively, use contentType: "GENERAL" with a digitalContent.fileUrl for a hosted download link.
Share your store link — inventpay.io/store/your-slug
Buyers see rich skill cards — storefront shows skill name, version, author, and tags from parsed frontmatter
Buyers pay with crypto — BTC, ETH, LTC, SOL, USDT, or USDC
Delivery is automatic — buyer pays, gets the skill file immediately
Check earnings — agent calls GET /v1/merchant/balance

What sells well: industry-specific skills, complex automation chains, curated skill bundles, premium versions of popular free skills, API integration skills. Price range $3-15 for individual skills, $20-40 for bundles.

Guidelines

All amounts default to USD/USDT unless specified otherwise
Supported cryptos: BTC, ETH, LTC, USDT_ERC20, USDT_BEP20, SOL, USDC_SOL, USDC_BEP20
Payment expiration: 5-1440 minutes (default 30)
The API key (pk_live_...) is used for all operations
Store checkout uses the store slug in the URL path, NOT a store ID
Digital products auto-deliver after payment via the digitalContent field
Product URLs require the /product/ segment: /store/{slug}/product/{productSlug}
To withdraw funds, use the InventPay dashboard at inventpay.io

Security notes

The INVENTPAY_API_KEY can create payments, manage your store, and read balances. It cannot withdraw or transfer funds.
Never pass credentials, secrets, or private keys as product delivery content. Use hosted file URLs for delivery.
You can revoke and regenerate your API key from the dashboard at any time.

Environment variables

Variable	Required	Description
`INVENTPAY_API_KEY`	Yes	Merchant API key (`pk_live_...`). Used for payments, store, products, orders, balances. Cannot withdraw funds.

Publisher

InventPay — Crypto payment infrastructure for developers and AI agents.

Files

SKILL.md and 1 other file in skills/inventpay-api of LeoYeAI/openclaw-master-skills.

SKILL.md
_meta.json

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Inventpay next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Inventpay compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Inventpay this skillLeoYeAI/openclaw-master-skills	2.2k	—	~4.3k	Automated safety check: Pass	MIT-0	2 mo ago
Stripe Paymentshewi333/Mom-n-Pop-Skills	122	—	~2.1k	Automated safety check: Notes	MIT	28 days ago
Pp Breezedocmvanhorn/printing-press-library	2.1k	—	~2.2k	Automated safety check: Notes	Apache-2.0	today
Paperclippaperclipai/paperclip	99k	—	~9.6k	Automated safety check: Pass	MIT	today
Nodejs Backend Patternsever-works/ever-works	162	18 repos	~4k	Automated safety check: Pass	AGPL-3.0	today
OpenAPI to MCP Servermcp-use/mcp-use	11k	—	~5.2k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Stripe Payments
hewi333/Mom-n-Pop-Skills
Create Stripe checkout sessions, payment links, invoices, and customers via Stripe REST API.
122 GitHub stars~2.1k tokensUpdated 28 days ago
Backend & APIsAuto-check: notes
Pp Breezedoc
mvanhorn/printing-press-library
Printing Press CLI for Breezedoc. An agent skill from mvanhorn/printing-press-library.
2.1k GitHub stars~2.2k tokensUpdated today
Backend & APIsAuto-check: notes
Paperclip
paperclipai/paperclip
Interact with the Paperclip control plane API for task coordination and governance.
99k GitHub stars~9.6k tokensUpdated today
Backend & APIsAuto-check passed
Nodejs Backend Patterns
ever-works/ever-works
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.
162 GitHub starsUsed in 18 repos~4k tokens
Backend & APIsAuto-check passed
OpenAPI to MCP Server
mcp-use/mcp-use
Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.
11k GitHub stars~5.2k tokensUpdated today
Backend & APIsAuto-check passed
Use Yaak
mountain-loop/yaak
A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…
19k GitHub stars~1.9k tokensUpdated 2 days ago
Backend & APIsAuto-check passed

Questions about Inventpay

What does Inventpay do?

Accept crypto payments, manage a digital storefront, and track balances through the InventPay REST API. Inventpay is an agent skill from LeoYeAI/openclaw-master-skills.

When should I use Inventpay?

Inventpay fits situations like: tasks that involve REST APIs; tasks that involve Forms and invoices.

How do I install Inventpay in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill inventpay -a claude-code`. Or copy the skill folder (skills/inventpay-api in LeoYeAI/openclaw-master-skills) into .claude/skills/inventpay in your project. Claude Code loads it when a task matches its description.

How do I install Inventpay in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill inventpay -a codex`. Or copy the skill folder (skills/inventpay-api in LeoYeAI/openclaw-master-skills) into .agents/skills/inventpay in your project. Codex loads it when a task matches its description.

Can I use Inventpay in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill inventpay -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/inventpay, .gemini/skills/inventpay, .github/skills/inventpay and .opencode/skills/inventpay in your project.

What does Inventpay need to run?

Going by SKILL.md and its folder, Inventpay needs credentials named INVENTPAY_API_KEY. Our summary lists: A credential in INVENTPAY_API_KEY.

Does Inventpay access the network?

SKILL.md names 6 domains. In commands or code: inventpay.io and api.inventpay.io; the agent is likely to contact these when it follows the instructions. As links in the text: github.com, npmjs.com, docs.inventpay.io and pypi.org. This is read from the text; nothing was executed.

Is Inventpay safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Inventpay use?

Inventpay is published under the MIT-0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Inventpay use?

About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Inventpay?

Skills that share tags, products or a category with Inventpay: Stripe Payments (hewi333/Mom-n-Pop-Skills, 122 stars), Pp Breezedoc (mvanhorn/printing-press-library, 2.1k stars), Paperclip (paperclipai/paperclip, 99k stars) and Nodejs Backend Patterns (ever-works/ever-works, 162 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Inventpay?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,160 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Inventpay

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

InventPay Skill

What this skill does

Quick start

Install

Configure

Verify

Base URL

Authentication

IMPORTANT: correct endpoint paths

Important URLs

API endpoints

Payments

Create a fixed-currency payment

Create a multi-currency invoice

Check payment status

Balances

Get all balances

Get balance for a specific currency

Store management

Create a store

Get your store

Update your store

Products

Create a product

List products

Update a product

Delete a product

Key pool (unique keys per customer)

Upload keys

List keys

Get key pool stats

Remove all available keys

Orders

List orders

Get order details

Update order status

Store checkout (public, no auth)

Store analytics

Agent behavior when creating products

Example conversations

Selling OpenClaw skills through your store

Guidelines

Security notes

Environment variables

Links

Publisher

Files

Compare with similar skills

Similar skills

More from LeoYeAI/openclaw-master-skills

Related

Questions about Inventpay