Canopy Deposits for Openclaw

Prepare Canopy crypto deposit intents, provide accurate funding details, and check deposit progress through a remote MCP server.

gkwxz4h9s8-ai
v1.0.0
Oct 3, 2026
0
168
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install canopy-deposits

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install canopy-deposits using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Canopy Deposits?

Canopy Deposits connects an AI agent to Canopy's remote MCP server to prepare crypto deposits for a merchant account, retrieve funding options and addresses, and report detection and settlement status. It is one of the Openclaw Skills for coordinating a human funding flow without handling the blockchain transaction itself: the human funds through Canopy checkout or from their own wallet.

The skill prioritizes accurate, account-specific information. It uses the tools' returned assets, networks, minimums, and settlement details rather than guessing, and it does not sign or submit transactions. Openclaw Skills users can use it to guide a deposit from intent creation through status checks while keeping credentials in the MCP client's secure configuration.

Canopy Deposits Use Cases

  • Prepare a new open-amount or fixed-amount crypto deposit when a user asks to fund a merchant account.
  • Share a hosted checkout link as a straightforward human funding option.
  • Provide a direct deposit address after the user selects an available funding option.
  • Check an existing intent's detection, transfer, or settlement progress.
  • Locate existing deposits or investigate a creation timeout before retrying.
  • Explain returned minimums, fees, net amounts, or below-minimum top-up requirements.

How Canopy Deposits Works

  1. Connect an MCP client to Canopy's remote server and authenticate with OAuth or a securely configured server-side Canopy secret key.
  2. Confirm the server exposes the five required tools: create_deposit, list_deposit_options, get_deposit_address, get_deposit_status, and list_deposits.
  3. For a new deposit, establish the destination from the user or app. Pass destination fields only when provided; never guess a recipient wallet.
  4. For a fixed amount, use an existing intent's settlement rails to identify the rail marked default: true and its decimals. Convert the amount to a positive base-unit integer string; if the required settlement configuration is unavailable, ask for it instead of guessing.
  5. Call create_deposit with supported inputs. Retain the returned intent ID and hosted checkout URL. An open-amount deposit omits priceUnits; oneTime: true requires it.
  6. For direct funding, retrieve this intent's options, show the user the available chain, token, and minimum, and proceed only with an option marked depositIssuable: true.
  7. Request the address using the option's exact returned caip19. Present the complete address with its returned chain name, token symbol, and minimum, and tell the user to send that token on that network.
  8. When asked for progress, read the intent status and report actual detection and per-transfer stages. Detection alone does not mean settlement; include relevant fee or net information and explain any below-minimum status.

Canopy Deposits Setup

  1. Configure an MCP client to use Canopy's Streamable HTTP endpoint: https://www.canopypay.io/api/mcp. Keep the www. hostname; the apex may redirect across hosts and drop the authorization header.
  2. Authenticate through the client's OAuth flow, or provide a Canopy secret key securely through the client's environment or credential configuration. OAuth uses authorization code with PKCE and supports dynamic registration.
  3. Ensure the credential has the required payment_intents:create scope. Publishable keys cannot authenticate to MCP.
  4. Verify the five tools listed in the workflow are available. The endpoint accepts POST and JSON responses; it does not support legacy SSE. GET or DELETE returning HTTP 405 is expected.
  5. Do not request secrets in chat or commit credentials to configuration. If the connection is missing, ask the account owner to connect it through their MCP client; do not invent credentials or access another merchant account.

Documentation: https://www.canopypay.io/agents/mcp
Plain-text contract: https://www.canopypay.io/agents/mcp/raw

Canopy is free to integrate, but that does not mean funding, conversion, blockchain fees, or settlement are free. Refer to tool results and current Canopy pricing when costs matter.

Canopy Deposits Data Schema & Taxonomy

The skill works with structured results from Canopy's MCP tools. Read structuredContent; some clients may expose equivalent JSON through text content. Inputs are strict, and unknown fields are rejected.

Tool Purpose Key inputs or outputs
create_deposit Create or reuse a payment intent Optional priceUnits, oneTime, merchantReference, metadata, and destination fields; retain returned intentId and hostedPageUrl
list_deposit_options Retrieve an intent's funding options, minimums, and settlement rails intentId; use returned option data and the rail marked default: true
get_deposit_address Issue or return an address and start detection for an option intentId and the exact returned caip19
get_deposit_status Read detection and transfer or settlement state intentId; report actual returned stages and relevant fee or net data
list_deposits List intents belonging to the authenticated account Optional limit and cursor

Deposit records and related metadata include intent terms, destination details, and funding or settlement state as returned by Canopy. Destination fields include payoutWallet, payoutNamespace, and payoutChainReference; payoutTokenAddress is optional when a destination wallet is supplied. Do not infer unsupported fields or add fee or treasury inputs.

An active intent may be reused for matching account, destination, and terms. A reused result has created: false; new merchantReference and metadata values are not applied. Different amount or one-time terms can produce idempotency_key_reuse. Without destination fields, each create makes a new intent. After a timeout, check the account's deposits before attempting creation again. Repeating an address request for the same intent and option returns the same address.

Canopy Deposits Advanced Features

  • Supports OAuth authorization code with PKCE and dynamic client registration, as well as securely configured server-side Canopy secret keys.
  • Handles intent reuse and idempotency outcomes; checks existing deposits after a timeout rather than blindly repeating a state-changing request.
  • Uses exact tool-returned asset, chain, token, caip19, minimum, and settlement-rail information instead of relying on hard-coded networks or assumed decimals.
  • Distinguishes deposit detection from settlement and can report per-transfer stages, fees, net amounts, and below-minimum status.
  • Responds to errors by code: correct rejected inputs, resolve authentication or hostname issues, and do not retry not_found against another account.
  • Respects HTTP 429 and Retry-After, and avoids tight automatic status polling.
  • Keeps human authorization and action central: creating an intent or issuing an address changes account state, while the human—not the MCP tools—funds the deposit.
  • Openclaw Skills users should not describe Canopy as stablecoin-only or promise that the sent and received assets match; supported assets and possible bridging or conversion depend on the returned tool data.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*