sardis-policy

What This Skill Does

The sardis-policy skill provides an advanced, natural language-driven interface for managing spending controls on Sardis-enabled agent wallets. By leveraging sophisticated parsing, it allows users to translate human-readable constraints into immutable on-chain policies. This skill acts as a guardrail layer, preventing unauthorized outflows or excessive spending by defining strict limits on vendors, categories, time windows, and transaction volumes.

Installation

To integrate this skill into your agent environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/efedurmaz16/sardis-policy

Ensure you have configured your environment by exporting your API key: export SARDIS_API_KEY=sk_your_key_here.

Use Cases

• Automated Procurement: Restrict agents to specific vendors like AWS or GitHub while keeping a daily spend cap to prevent billing surprises.
• Operational Guardrails: Implement 'business hours only' rules to ensure agent transactions do not occur during off-peak times or holidays.
• Risk Management: Automatically route large transactions to human approval workflows when they exceed specific dollar amounts.
• Testing & Compliance: Validate transaction rules via dry-runs to ensure compliance before enabling autonomous agent operations in production.

Example Prompts

1. "Create a new spending policy for my agent wallet wallet_abc123. Limit daily spend to $200 and only allow transactions from openai.com and github.com. Block all gambling and crypto-exchange services."
2. "Check if a transaction of $150 to anthropic.com is allowed by my current policy for wallet_abc123 on the base chain."
3. "List all active policies associated with my main operational wallet wallet_abc123 to verify the current restrictions."

Tips & Limitations

• Immutability: Policies are immutable. If you need to update a limit or vendor list, you must create a new version of the policy and migrate your agent's wallet to the new instance.
• Dry-Run Usage: Always utilize the policies/check endpoint before triggering critical agent tasks to confirm the proposed transaction aligns with existing constraints.
• Security: Because policies govern financial movement, ensure your SARDIS_API_KEY is handled with the same security practices as a private key.