LivePair AI 发布官方 Agent 技能包 livepair-skills
livepairai/livepair-skills
LivePair AI 推出官方 Agent 技能包 livepair-skills,覆盖图像、视频、文本生成,支持 x402(Base 链 USDC,无需账户)与 lp_ API key 预付费两种按次计费方式。
Official agent skills for the LivePair AI API —
private-by-default image, video, and text generation with per-call
pricing: x402 (USDC on Base, no account) or a prepaid lp_ API key.
Install
npx skills add livepairai/livepair-skills
or point your agent at the single-file contract hosted at
https://livepairai.com/SKILL.md.
Plugin manifests for Claude Code, Codex, and Cursor live in
.claude-plugin/, .codex-plugin/, .cursor-plugin/ — hosts that read
them load the whole skills/ bundle.
Skills
One folder per surface, each with a SKILL.md:
| Skill | Covers |
|---|---|
livepair-api-overview |
Endpoint map, the two payment rails, routing to sibling skills |
livepair-models |
Catalog fields, per-option USD pricing, quote math |
livepair-image-generate |
t2i / i2i / edit / upscale / remove-bg + job polling |
livepair-video |
t2v / i2v incl. the private line, per-second pricing |
livepair-chat |
OpenAI-compatible text completions, per-token billing |
livepair-x402 |
HTTP 402 → PAYMENT-SIGNATURE loop, volume tiers |
livepair-api-keys |
lp_ key auth, balance endpoint, refund semantics |
livepair-mcp |
Remote MCP server config per host + the 11 tools |
livepair-errors |
Status map, job failures, refund rules, rate limits |
livepair-single-file |
The whole contract in one file — same document the site serves at /SKILL.md, generated from the live catalog |
Integrations elsewhere
- Bots & workflows:
livepairai/livepair-bots— Telegram/Discord/n8n templates, zero deps - ComfyUI:
livepairai/ComfyUI-LivePair— custom nodes for the full catalog
API surfaces
- Catalog:
GET https://livepairai.com/v1/agent/models(free) - OpenAPI:
https://livepairai.com/v1/agent/openapi.json - Manifest:
https://livepairai.com/v1/agent/manifest.json - MCP:
https://livepairai.com/mcp(streamable HTTP) - Docs: https://livepairai.com/docs/api · https://livepairai.com/docs/frameworks
Running alongside other generation MCPs
Already using another image/video MCP (Higgsfield, fal, Replicate…)?
LivePair coexists in the same client config — agents see both tool
lists and pick per call. Example claude_desktop_config.json:
{
"mcpServers": {
"higgsfield": { "url": "https://mcp.higgsfield.ai/mcp" },
"livepair": { "url": "https://livepairai.com/mcp" }
}
}Calls route to LivePair when you want private generation (renders auto-delete after 48h), per-result prepaid billing instead of a subscription, or a model from the LivePair catalog. No migration — it's a second engine, not a replacement.
Developing these skills
python scripts/validate_skills.py checks the manifest ↔ disk
integrity. See CONTRIBUTING.md — accuracy rules:
never hardcode model IDs/prices, keep both payment rails documented,
and keep privacy claims literal.
License
MIT
来源:GitHub · github.com