Legendarylibr

Seisoai

AI 智慧體v1.1.1
作者:Legendarylibr更新於 2026-05-11共 31 個版本 · 最新版本釋出於 2026-02-17seiso@clawhub_legendarylibr/seiso
Agent 框架工具呼叫#Audio#Music

據 AlphaMoat 統計,截至 2026-09,Seisoai 累計下載 3,960 次、獲 3 個星標,在全部 5,078 個 AI 技能中排名第 2,600 位,在「AI 智慧體」分類(969 個)中排名第 507 位。

累計安裝
264
累計下載
3960
星標
3
全站排名
#2,600
全站前 52% · 「AI 智慧體」前 53%
平台累計安裝累計下載星標評論
ClawHub ↗127379432
SkillHub ↗26439603—

各平台的計數口徑不同,統計時間不一致。

這個技能是做什麼的

基礎 URL 為 https://seisoai.com,主端點 POST /api/gateway/invoke/{toolId},認證用 X-API-Key 或 x402 支付(USDC on Base)。每次會話的 agent-first 工作流:先經 GET /api/gateway/tools 動態發現線上工具(有即時登錄檔時不依賴靜態工具列表),對選定工具取精確 schema,可選用 GET /api/gateway/price/{toolId} 預定價,再呼叫並輪詢佇列任務的 statusUrl/resultUrl。認證決策序:有專案 API key 用 X-API-Key;沒有則用 x402 按請求付費(402 後簽名重試);機器客戶端不傳送瀏覽器 CSRF token。對普通媒體生成無需額外檢查;僅當任務明確要求操作特定 agent 時才可訪問 /api/gateway/agent/*,且須透過九條強制安全控制:明確任務要求、精確 agent 繫結(絕不從名稱猜測 agentId)、授權邊界(只用當前呼叫者憑據)、單 agent 範圍、工具白名單校驗、禁止遞迴編排、禁止無關的廣泛列舉、審計留痕、歧義即停並回退到普通 invoke。錯誤碼策略:400 修正 schema、402 補支付、404 重新整理登錄檔、503 選同類回退、500 退避重試。重試時絕不復用過期的 x402 簽名。 佇列任務提交成功即屬於計費成功;換臉、聲音克隆等涉及真實人物時,僅處理有權且獲同意的素材,並明確確認。

資料釋出於 2026-10-27

可以用來做什麼

  • 為 agent 動態發現並呼叫 Seisoai 的圖像/影片/音訊/音樂/3D 生成工具
  • 用 x402 按請求付費或 API key 呼叫媒體生成端點並處理佇列任務
  • 需要按白名單與安全控制操作特定 agent 編排時

什麼時候用

  • 開發者和 agent 用它發現 Seisoai 媒體生成工具、選擇認證方式、可靠管理佇列任務
  • 僅在使用者明確要求執行或編排特定 agent 時使用 agent-scoped 端點

示例提示詞

以下是根據技能文件生成的示例,不代表實際執行結果。

用 Flux 生成一張日落山脈圖並返回結果 URL
幫我把這張圖轉成 6 秒影片,用 x402 付費流程
呼叫前先查詢這個工具的即時價格和 schema

月度資料趨勢

累計下載3960
2920347940372026-03 · 累計下載 29972026-05 · 累計下載 33012026-06 · 累計下載 34012026-07 · 累計下載 36182026-08 · 累計下載 36982026-09 · 累計下載 396026-0326-09
星標3
2342026-03 · 星標 32026-05 · 星標 32026-06 · 星標 32026-07 · 星標 32026-08 · 星標 32026-09 · 星標 326-0326-09

2026-09 起統計方法調整:同名技能按作者分別統計,並覆蓋全部技能。圖中虛線為調整前的月份,與之後的資料不直接比較,也不計算跨越調整的增長。

月份累計下載環比星標
2026-093960—3
2026-083698+2.2%3
2026-073618+6.4%3
2026-063401+3.0%3
2026-053301—3
2026-032997—3

SKILL.md 原文

以下是作者釋出的原始檔案,按純文字顯示,本站未做修改或稽核;其中的連結不可點選,命令請核實後再執行。抓取於 2026-10-23。

7.3 KB · ClawHub v1.1.1
---
name: seisoai
description: Unified media generation gateway for agents. Discover tools dynamically, choose API key or x402 auth, invoke image/video/audio/music/3D/training tools, and handle queue jobs reliably.
metadata: {"openclaw":{"homepage":"https://seisoai.com","emoji":"🎨"}}
version: 1.1.1
last_synced: 2026-02-09
---

# Seisoai
展開全部(共 210 行)
Base URL: `https://seisoai.com`
Primary endpoint: `POST /api/gateway/invoke/{toolId}` or `POST /api/gateway/invoke` with `toolId` in body.
Auth: `X-API-Key` or x402 payment (USDC on Base).

## Agent-First Workflow (Do This Every Session)

1. Discover live tools:
   - `GET /api/gateway/tools`
2. For selected tools, fetch exact schema:
   - `GET /api/gateway/tools/{toolId}`
3. Optionally pre-price inputs:
   - `GET /api/gateway/price/{toolId}`
4. Invoke with API key or x402.
5. If queue tool, poll job status/result URLs from response.

Do not rely on static tool lists when a live registry is available.

## Auth Strategy

Use this decision order:

1. If you have a project API key, use `X-API-Key`.
2. If you do not have a key, use x402 pay-per-request.
3. Do not send browser CSRF tokens for machine clients.

### API Key Example

```http
POST /api/gateway/invoke/image.generate.flux-2
X-API-Key: sk_live_xxx
Content-Type: application/json

{"prompt":"a sunset over mountains"}
```

### x402 Example (2-step)

1. Call without payment header.
2. Receive `402` with payment requirements.
3. Sign/pay on Base.
4. Retry same request with one of:
   - `payment-signature`
   - `x-payment`
   - `payment`

## High-Value Endpoints

- Discovery:
  - `GET /api/gateway/tools`
  - `GET /api/gateway/tools/{toolId}`
  - `GET /api/gateway/price/{toolId}`
  - `GET /api/gateway/mcp-manifest`
- Invoke:
  - `POST /api/gateway/invoke/{toolId}`
  - `POST /api/gateway/invoke`
- Jobs:
  - `GET /api/gateway/jobs/{jobId}?model=...`
  - `GET /api/gateway/jobs/{jobId}/result?model=...`
- Agent-scoped:
  - `GET /api/gateway/agents`
  - `GET /api/gateway/agent/{agentId}`
  - `POST /api/gateway/agent/{agentId}/invoke/{toolId?}`
  - `POST /api/gateway/agent/{agentId}/orchestrate`

## Agent-Scoped Safety Controls (Mandatory)

For normal media generation (images, video, audio, 3D), use **`/api/gateway/invoke`** and the discovery endpoints above; no extra checks. The rules below apply only when the user explicitly asks to run or orchestrate a **specific agent** (e.g. a named bot or workflow).

Default posture: **deny by default** for agent-scoped routes (`/api/gateway/agent/*`). Use agent-scoped endpoints only when all checks pass:

1. **Explicit task requirement**
   - Do not call `/agent/*` routes unless the current task explicitly requires operating a specific agent.
2. **Exact agent binding**
   - Resolve `agentId` from a trusted source (`GET /api/gateway/agents` or user-provided exact ID).
   - Never infer or guess agent IDs from names/prompts.
3. **Authorization boundary**
   - Use only the current caller credentials.
   - Never attempt to reuse, escalate, or proxy credentials to access other tenants/owners.
4. **Single-agent scope**
   - For one task, operate on one approved `agentId` unless the user explicitly requests multi-agent execution.
5. **Tool allowlist enforcement**
   - Before invoke/orchestrate, fetch `GET /api/gateway/agent/{agentId}` and only use tool IDs declared for that agent.
   - Reject tool IDs not listed in that agent definition.
6. **No recursive orchestration**
   - Do not create self-referential orchestrations, orchestration loops, or fan-out patterns across unknown agents.
7. **No broad discovery exfiltration**
   - Do not enumerate all agents unless needed for user task; prefer direct lookup when `agentId` is known.
8. **Audit trail requirement**
   - Log `agentId`, route, tool ID, and reason for each agent-scoped call in agent run notes.
9. **On mismatch or ambiguity: stop**
   - If ownership/scope/tool authorization is ambiguous, do not call `/agent/*`; fall back to `/api/gateway/invoke`.

## Tool Selection Cheatsheet (Verified IDs)

### Images
- Fast text->image: `image.generate.flux-2`
- Premium cinematic: `image.generate.kling-image-v3`
- Premium consistency: `image.generate.kling-image-o3`
- 360/panorama: `image.generate.nano-banana-pro`
- Prompted edit: `image.generate.flux-pro-kontext-edit`
- Face swap: `image.face-swap`
- Inpaint/outpaint: `image.inpaint`, `image.outpaint`
- Background removal/layer: `image.extract-layer`
- Upscale: `image.upscale`

### Video
- Text->video (Veo): `video.generate.veo3`
- Image->video (Veo): `video.generate.veo3-image-to-video`
- First/last frame: `video.generate.veo3-first-last-frame`
- Kling text: `video.generate.kling-3-pro-text`, `video.generate.kling-3-std-text`
- Kling image: `video.generate.kling-3-pro-image`, `video.generate.kling-3-std-image`
- Motion transfer: `video.generate.dreamactor-v2`

### Audio / Speech / Music
- Voice clone TTS: `audio.tts`
- TTS quality tiers: `audio.tts.minimax-hd`, `audio.tts.minimax-turbo`
- Lip sync: `audio.lip-sync`
- Transcription: `audio.transcribe`
- Music: `music.generate`
- Sound FX: `audio.sfx`
- Stem separation: `audio.stem-separation`

### 3D
- Image->3D standard: `3d.image-to-3d`
- Image->3D pro: `3d.image-to-3d.hunyuan-pro`
- Text->3D pro: `3d.text-to-3d.hunyuan-pro`
- Fast image->3D: `3d.image-to-3d.hunyuan-rapid`
- Mesh post-processing: `3d.smart-topology`, `3d.part-splitter`

## Minimal Payload Patterns

Text->image:
```json
{"prompt":"..."}
```

Image edit:
```json
{"prompt":"...","image_url":"https://..."}
```

Text->video:
```json
{"prompt":"...","duration":"6s"}
```

DreamActor motion transfer:
```json
{"source_image_url":"https://...","driving_video_url":"https://..."}
```

Voice clone TTS:
```json
{"text":"...","audio_url":"https://..."}
```

3D image->mesh:
```json
{"image_url":"https://...","output_format":"glb"}
```

## Queue Handling Contract

If `executionMode` is `queue`, response includes job metadata. Use:

1. `statusUrl` until completed/failed.
2. `resultUrl` when completed.

Treat queue submit success as billable success (x402 settlement/API-key credit deduction already handled server-side).

## Error Policy

- `400`: Schema/input mismatch. Re-fetch tool schema and correct fields.
- `402`: Missing/invalid payment or insufficient API key credits.
- `404`: Tool/agent not found. Refresh registry.
- `503`: Tool disabled. Select fallback in same category.
- `500`: Retry with backoff; then switch model/tool.

## Reliability Rules for Agents

1. Always discover live tools before planning multi-step flows.
2. Use exact schema from `GET /tools/{toolId}` for required fields.
3. Keep one tool call per request; chain in your agent.
4. Prefer explicit model/tool IDs over natural-language routing assumptions.
5. For retries, do not reuse stale x402 signatures.
6. Treat `/api/gateway/agent/*` as privileged routes and apply the mandatory safety controls above.

## Self-Maintenance

When this file is updated:
- Keep IDs aligned with `backend/services/toolRegistry.ts`.
- Update `last_synced` and `version`.
- Keep examples minimal and executable.

## Changelog

- [2026-02-09] v1.1.1 - Added mandatory safety controls for agent-scoped endpoints (deny-by-default, agent/tool scoping, anti-recursion, and audit requirements).
- [2026-02-09] v1.1.0 - Rewrote for agent discovery-first flow, corrected stale tool IDs/params, tightened auth/x402 guidance, and added queue/error reliability policy.
- [2026-02-08] v1.0.0 - Initial self-improvement protocol added.

「AI 智慧體」分類下的熱門技能

資料月份:2026-09 · 下載/星標/安裝數聚合自公開技能註冊庫(ClawHub、SkillHub),按月更新。口徑說明見資料方法。