Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.delegare.dev/llms.txt

Use this file to discover all available pages before exploring further.

The official Delegare plugin for OpenClaw gives your AI agents the ability to autonomously execute payments and bypass x402 paywalls. By installing this plugin, your agent gains access to the Delegare tool suite, allowing it to spend funds safely using a pre-authorized AP2 Intent Mandate (SD-JWT-VC) without needing you to approve every transaction.

​
1. Installation

The Delegare plugin is a native OpenClaw extension. Install it directly using the OpenClaw CLI: 
openclaw plugins install @delegare/openclaw-plugin

​
2. Configuration & Authentication

OpenClaw operates as a secure, headless execution environment. Because it cannot natively intercept web-based OAuth redirects, Delegare uses Long-Lived Access Tokens specifically designed for Agent configuration. Getting your agent connected is a simple, one-time setup:
  1. Ask your Agent to Connect Simply tell your OpenClaw agent: “Connect to Delegare.” The agent will invoke the delegare_connect tool, which will instantly reply with a secure, self-service setup link.
  2. Generate your Token Click the link the agent provides (or visit app.delegare.dev/connect/agent?platform=openclaw).
    • Log in securely using your standard Google/Apple account.
    • Delegare will instantly provision a 90-day secure access token for your agent.
  3. Update your Config The dashboard will provide a pre-formatted JSON snippet. Open your OpenClaw gateway configuration file (usually located at ~/.openclaw/openclaw.json) and paste it into your plugins block:
~/.openclaw/openclaw.json
{
  "plugins": {
    "allow": ["delegare"],
    "entries": {
      "delegare": {
        "enabled": true,
        "config": {
          "accessToken": "token_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
        }
      }
    }
  },
  "tools": {
    "allow": ["*"]
  }
}
Note: You can replace "*" in the tools array with specific names like "delegare_fetch" or "setup_spending_mandate" if you prefer strict capability scoping. Restart your OpenClaw gateway to apply the new configuration. Your agent is now fully authenticated!

​
3. 🧪 Testing in the Sandbox

If you are developing a local e-commerce backend and want to test the plugin without using real money, you can easily point your agent to the Delegare Sandbox API. Simply update your config block in ~/.openclaw/openclaw.json to include the Sandbox baseUrl:
~/.openclaw/openclaw.json
{
  "plugins": {
    "allow": ["delegare"],
    "entries": {
      "delegare": {
        "enabled": true,
        "config": {
          "accessToken": "token_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
          "baseUrl": "https://api.sandbox.delegare.dev/v1"
        }
      }
    }
  },
  "tools": {
    "allow": ["*"]
  }
}
(Remember to use a Sandbox Token generated from app.sandbox.delegare.dev if you use the Sandbox API!)

​
4. Usage

Your agent is now economically enabled! Start a new chat session in OpenClaw (so it loads the updated tool context) and try prompting it with tasks that require payment or data retrieval: 
Fetch the data from https://premium-api.com/data. 
If it asks for payment via x402, use your mandate to pay it.

​
Security Features

  • Zero Popups: Once limits are set, the agent handles transaction signing server-side. No wallet popups will interrupt its workflow.
  • Non-Custodial: Your master private key never leaves your device. The agent only receives a tightly scoped, easily revokable session key.
  • Strict Bounds: Every transaction is verified by the Vault backend against the human-defined per-transaction and monthly limits.