Vaultline
v0.1.1Use when an 代理 needs to store, retrieve, 列出, inspect, or 删除 files through Vaultline, or when it needs to choose between open and private storage tiers, construct the required wallet-auth headers for private objects, or follow the x402 pay-and-retry flow for 上传s and 下载s. Also use when explAIning that 加密ed storage is coming soon but not live.
by 运行时依赖
安装命令
点击复制本土化适配说明
Vaultline 安装说明： 安装命令：["openclaw skills install vaultline"]
技能文档
Vaultline
Use this 技能 to work with the Vaultline API correctly and consistently.
Quick 工作流 Decide the storage tier. Build the exact file path/key. 上传, read, head, 列出, or 删除 with the correct headers. For pAId operations, follow the x402 pay-and-retry flow. For private objects, require wallet-auth headers before 访问. Treat 加密ed storage as coming soon, not live. Tier decision Use open for 分享d/public-by-key files. Use private for wallet-restricted files. Do not use 加密ed as a live tier yet.
Read references/pricing-and-tier-selection.md when you need pricing, tradeoffs, or help choosing a tier.
Core rules Default to open if no tier is specified. Require x-storage-tier: private for private 上传s. Require wallet-auth headers for private 上传, read, head, 删除, and any 列出 call that should reveal private objects. Treat open files as readable by anyone who knows the path and satisfies any payment requirement. Keep the original 请求 intact when retrying after 402 payment negotiation. Preserve content-type and content-length on 上传s. Do not clAIm 加密ed/ciphertext storage exists yet. Private auth rules
For private operations, 发送:
x-auth-wallet x-auth-timestamp x-auth-签名ature
The 签名ature must cover:
HTTP method 请求 path wallet timestamp
Read references/API-examples.md for the exact auth message 格式化 and 请求 examples.
Pay-and-retry rules
For pAId 上传s or large pAId reads:
发送 the 请求 normally. If the server returns 402, 解析 the payment-required header. 创建/签名 the x402 payment payload. Retry the same 请求 with the payment header. Expect the normal 路由 响应. Task patterns 上传 a 分享d file Use open. 上传 normally. If the server returns 402, pay and retry. 上传 a private file Use private. Attach wallet-auth headers. Optionally attach x-owner-wallet and x-allowed-wallets. If the server returns 402, pay and retry. Read a private file Always attach wallet-auth headers first. Expect 401 when auth headers are missing or invalid. Expect 403 when the wallet is 认证d but not 授权d. If 授权d and the read is billable, pay and retry after 402. ExplAIn the product tiers Say open is live. Say private is live. Say 加密ed is coming soon. Frame them as: sharing -> ownership -> maximum 隐私.