企业账户开户:简化 Vivid 银行设置 - Openclaw Skills

作者:互联网

2026-03-31

AI教程

什么是 企业账户开户?

企业账户开户技能允许 AI 代理协助开设 Vivid 企业账户的初始阶段。通过连接到远程模型上下文协议 (MCP) 服务器,该技能会收集必要的法律实体信息(如实体类型和国家),并生成安全的、预填写的入驻 URL。它旨在弥合 AI 驱动的聊天界面与 Openclaw Skills 生态系统内专业金融服务之间的差距。

安全性是该技能架构的核心组成部分。它在严格的隐私模型下运行,文档解析在 AI 客户端本地进行,确保敏感的原始文件永远不会传输到远程服务器。这使其成为在管理业务管理任务时同时重视自动化和数据主权的用户的理想选择。

下载入口:https://github.com/openclaw/skills/tree/main/skills/stanlee000/vivid-business-account-opening

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

npx clawhub@latest install vivid-business-account-opening

2. 手动安装

将技能文件夹复制到以下位置之一

全局模式 ~/.openclaw/skills/ 工作区 /skills/

优先级:工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

请帮我使用 Clawhub 安装 vivid-business-account-opening。如果尚未安装 Clawhub,请先安装(npm i -g clawhub)。

企业账户开户 应用场景

  • 为 GmbH、UG 或自由职业者等实体启动新的业务入驻流程。
  • 自动从上传的银行申请文件中提取法律实体数据。
  • 使用 Openclaw Skills 将专业的银行工作流集成到 AI 代理环境中。
  • 减少金融账户创建初始阶段的手动数据输入。
企业账户开户 工作原理
  1. AI 代理检测到用户启动企业账户开户流程的意图。
  2. 该技能请求特定的数据点,包括法律实体类型和国家(如果未指定,默认为德国)。
  3. 如果提供了文档,AI 客户端会在本地提取所需字段并向用户总结发现。
  4. 该技能呈现所有收集数据的完整摘要供用户查看。
  5. 在用户明确确认后,该技能触发远程 MCP 服务器上的 build_onboarding_link 工具。
  6. 服务器返回一个安全的入驻 URL,AI 将其呈现给用户以完成申请。

企业账户开户 配置指南

要使用此技能,请将远程 MCP 服务器添加到您的客户端配置中。不需要本地二进制文件或环境变量。这种集成是扩展您的 Openclaw Skills 库的一种轻量级方式。

{
  "mcpServers": {
    "vivid-mcp": {
      "type": "http",
      "url": "https://api.prime.vivid.money/mcp"
    }
  }
}

企业账户开户 数据架构与分类体系

该技能严格组织数据以维护隐私和合规性。在工作流中仅处理结构化元数据。

数据类别 处理方法 存储
法律实体数据 结构化字段(类型、国家) 传输至 MCP
上传的文档 仅本地解析 永不存储或发送
入驻 URL 通过远程 API 生成 返回给用户
PII 通过 Vivid 隐私政策处理 无本地持久化
name: business-account-opening
description: >
  Open a Vivid Business account via a remote MCP server. Collects legal
  entity data from the user in chat, then calls build_onboarding_link to
  generate a pre-filled onboarding URL. The tool only creates a link —
  no bank account is opened and no financial data is accessed. No local
  install or credentials required.
version: 0.1.0
disable-model-invocation: true

metadata:
  openclaw:
    emoji: "??"
    homepage: "https://github.com/vivid-money/vivid-mcp"
    disable-model-invocation: true
    requires:
      env: []
      bins: []
      config: []

Business Account Opening

Open a Vivid Business account using a remote MCP server hosted by Vivid Money.

Integration

Property Value
Endpoint https://api.prime.vivid.money/mcp
Transport Streamable HTTP (remote)
Tool build_onboarding_link
Auth None — the endpoint is publicly accessible. The tool only generates a pre-filled onboarding link; it does not create a bank account, access financial data, or perform any privileged operation. Identity verification happens later in the Vivid app.

MCP client config

Add this to your MCP client configuration to connect:

{
  "mcpServers": {
    "vivid-mcp": {
      "type": "http",
      "url": "https://api.prime.vivid.money/mcp"
    }
  }
}

Tool schema

build_onboarding_link accepts a single legal_entity_data object with the basic data The tool returns an onboarding URL. No sensitive financial data is returned.

Trigger

User wants to open a business account or start business onboarding.

Flow

  1. Ask for legal entity type (GmbH, UG, freelancer, etc.) if not provided.
  2. Ask for country if not provided. Default: Germany.
  3. Call MCP to get required fields
  4. If the user uploads a document, extract the fields locally in the AI client — the document itself is never sent to the MCP server. Summarize what was extracted; do not echo raw document contents.
  5. Show the user a summary of all collected data and ask for explicit confirmation before proceeding.
  6. Only after user confirms: call build_onboarding_link with the confirmed data.
  7. Present the returned onboarding URL to the user.

Data handling

  • Documents stay local. Uploaded files are parsed by the AI client. Only the structured fields listed above are sent to the MCP server — never the raw document.
  • No PII stored by the skill. The skill itself does not persist any data. The MCP server creates an onboarding session on Vivid's platform; Vivid's privacy policy governs from that point: https://vivid.money/en-eu/privacy-policy/
  • No credentials in chat. Never ask for or accept passwords, API keys, or bank account numbers.
  • What the tool sends. Only the fields in the schema table above. No file content, no chat history, no device metadata.

Rules

  • Always confirm collected data with the user before calling build_onboarding_link.
  • This skill must only be invoked by explicit user request — never autonomously.
  • Treat uploaded documents as sensitive — summarize only, don't echo contents.
  • On error: ask for missing fields or suggest a different document.