Skip to main content

settld-mcp-payments

Connect OpenClaw agents to Settld MCP for paid tool calls with quote-bound authorization and verifiable receipts.

Stars
15
Source
dvcrn/openclaw-skills-marketplace
Updated
2026-05-29
Slug
dvcrn--openclaw-skills-marketplace--settld-mcp-payments
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/dvcrn/openclaw-skills-marketplace/HEAD/plugins/aidenlippert--settld-mcp-payments/skills/settld-mcp-payments/SKILL.md -o .claude/skills/settld-mcp-payments.md

Drops the SKILL.md into .claude/skills/settld-mcp-payments.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Settld MCP Payments Skill

This skill teaches OpenClaw agents to use Settld for paid MCP tool calls.

What This Skill Enables

  • Discover Settld MCP tools (settld.*)
  • Run paid tool calls with x402 challenge/authorize/retry flow
  • Return verifiable payment/settlement headers from tool responses
  • Produce audit-grade artifacts and receipts in Settld

Prerequisites

  • Node.js 20+
  • Settld API key (SETTLD_API_KEY)
  • Settld API base URL (SETTLD_BASE_URL)
  • Tenant id (SETTLD_TENANT_ID)
  • Optional paid tools base URL (SETTLD_PAID_TOOLS_BASE_URL)

MCP Server Registration

Use the server definition in mcp-server.example.json.

Server command:

  • command: npx
  • args: ["-y","settld-mcp"]

Required env vars:

  • SETTLD_BASE_URL
  • SETTLD_TENANT_ID
  • SETTLD_API_KEY

Optional env vars:

  • SETTLD_PAID_TOOLS_BASE_URL
  • SETTLD_PROTOCOL

Agent Usage Pattern

  1. Call settld.about to verify connectivity.
  2. For paid search/data calls, use:
    • settld.exa_search_paid
    • settld.weather_current_paid
  3. For agreement lifecycle demo calls, use:
    • settld.create_agreement
    • settld.submit_evidence
    • settld.settle_run
    • settld.resolve_settlement

Smoke Prompts

  • "Call settld.about and return the result JSON."
  • "Run settld.weather_current_paid for Chicago in fahrenheit and include the x-settld-* headers."

Safety Notes

  • Treat SETTLD_API_KEY as secret input.
  • Do not print full API keys in chat output.
  • Keep paid tools scoped to trusted providers and tenant policy.