Interfaces

Skill

How to use the OpenPayment skill in agent workflows to collect requirements conversationally and generate payment links.

The OpenPayment skill is the conversational interface for creating payment links in agent environments such as Codex, Claude Code, Cursor, OpenCode, or OpenClaw.

What the skill does

The skill wraps the same creation model used by the Web UI, CLI, and SDK, but starts from natural language instead of a form or function call.

Its job is to help the agent:

  1. gather the required payment inputs
  2. resolve missing information
  3. choose the correct payment type
  4. run the creation flow
  5. return the payment URL clearly

The payment model does not change. The skill is simply the most ergonomic interface when a human wants to express the request conversationally.

Install

In skill-enabled coding agents

npx skills add https://github.com/noncept/openpayment

In OpenClaw

clawhub install openpayment

Best-fit use cases

Use the skill when:

  • an operator wants to create a payment by describing it in plain language
  • an AI agent should set up a payment during a workflow
  • the user does not know the CLI syntax
  • the creation process should feel guided rather than technical

Example requests that fit the skill well:

  • "Create a 10 USDC payment link for this wallet"
  • "Make a reusable donation link on Base"
  • "Generate a paid proxy link for this protected report"

How the skill thinks about missing information

The skill expects the same core inputs as every other interface:

  • amount
  • recipient wallet
  • payment type
  • network
  • optional description
  • protected resource URL for PROXY

Its documented default behavior is:

  • default type: SINGLE_USE
  • default network: Base Mainnet (eip155:8453)

If the request sounds like testing, the skill should switch to Base Sepolia. If the request implies reuse or flexible amounts, it should help the user choose a better payment type before creation.

What to provide up front

The skill works best when the prompt includes:

  • the amount
  • the recipient wallet address
  • whether the link should be reusable
  • whether the amount should stay fixed or be editable
  • for PROXY, the protected HTTPS resource URL

That lets the agent create the payment with minimal back-and-forth.

Example requests

One-time payment

Create a single-use 25 USDC payment link on Base Mainnet for 0xYourWalletAddress for Order #2048.
Create a reusable variable payment link on Base for 0xYourWalletAddress with a suggested amount of 5 USDC.

Proxy payment

Create a proxy payment for 3 USDC on Base Mainnet for 0xYourWalletAddress that unlocks https://example.com/private/report.

What the skill returns

Like the CLI and SDK, the skill ultimately returns:

  • paymentId
  • the public payment URL

The payer still completes settlement through the hosted OpenPayment checkout.

When to choose Skill vs CLI vs SDK

InterfaceBest when
SkillA human or agent wants a guided conversational workflow
CLIA terminal or script should create the link directly
SDKYour application code should create the link programmatically

If your team is already working inside an agent environment, the skill is often the most natural entry point.