settld-mcp-payments

What This Skill Does

The Settld MCP Payments skill empowers OpenClaw agents to perform secure, monetized interactions with external tool providers. By bridging the gap between standard Model Context Protocol (MCP) servers and the Settld payment infrastructure, this skill allows agents to execute paid API calls while maintaining strict authorization, quote-bound validation, and verifiable audit trails. Instead of open-ended tool execution, agents follow a professional financial protocol: discovery, quoting, authorization via x402 headers, and receipt generation. This makes the skill ideal for high-value services, such as enterprise search, specialized data queries, or complex automated agreements, ensuring every transaction is transparent and verifiable.

Installation

To integrate this skill, ensure you have Node.js 20+ installed on your system. Use the OpenClaw CLI to install the package directly from the registry: clawhub install openclaw/skills/skills/aidenlippert/settld-mcp-payments. Once installed, configure the mcp-server.example.json file. You must set your SETTLD_API_KEY, SETTLD_BASE_URL, and SETTLD_TENANT_ID within the environment variables. The server itself is invoked via npx -y settld-mcp. We recommend defining these variables in a local .env file to prevent accidental exposure in your terminal history.

Use Cases

This skill is designed for scenarios requiring high accountability and cost-tracking. Key use cases include:

• Monetized Research: Using settld.exa_search_paid for intensive research tasks where each request must be billable.
• Real-time Data Procurement: Fetching proprietary weather or market data through paid endpoints like settld.weather_current_paid.
• Automated Lifecycle Management: Managing end-to-end agreements, from drafting to settlement, using the full suite of agreement tools including create_agreement and resolve_settlement.
• Auditable AI Agents: Generating verifiable receipts and audit-grade artifacts for every tool execution, essential for enterprise-grade financial reporting.

Example Prompts

1. "Call settld.about to verify that our tenant is correctly authenticated and reachable."
2. "Search for the latest 2024 quarterly revenue data using settld.exa_search_paid and provide the x-settld-receipt header once finished."
3. "Initiate an agreement process for the Q4 contract using settld.create_agreement and confirm the status of the settlement run."

Tips & Limitations

• Security: Never output your SETTLD_API_KEY in plain text. Use environment variables exclusively.
• Versioning: Ensure your local MCP runtime is compatible with the latest Settld protocol versions.
• Observability: Monitor your logs for x-settld-* headers; these are vital for debugging payment rejections or quote mismatches.
• Limitations: This skill relies on the presence of a configured Settld tenant. It cannot function as a standalone tool without external backend infrastructure.