siwa

What This Skill Does

SIWA (Sign-In With Agent) is a specialized authentication framework designed for the ERC-8004 standard, enabling AI agents to interact with web services using their verifiable onchain identity. Unlike traditional OAuth or API keys, SIWA allows agents to prove their identity through cryptographic signatures, ensuring that every request originates from an authorized, registry-tracked agent. The skill provides a robust SDK for managing agent-side signing, handling multi-chain requests, and processing automated x402 payments when services require a fee for access. By integrating this into OpenClaw, your agent gains the ability to authenticate securely with decentralized platforms, verify its provenance, and handle sophisticated payment flows without manual intervention.

Installation

To integrate SIWA into your agent, use the OpenClaw CLI tool. Run the following command in your terminal within your project root:

clawhub install openclaw/skills/skills/buildersgarden/siwa

Once installed, ensure your environment variables are configured to support your chosen signer (e.g., private keys, Privy, or Circle). You must also register your agent on-chain as per the ERC-8004 specification to begin the authentication process.

Use Cases

1. Decentralized API Access: Agents can authenticate against private APIs that require identity verification, ensuring only registered agents can consume services.
2. Automated Micro-payments: Using x402 payment flow, agents can automatically purchase compute, data, or content from services that require payment upon request, retrying automatically upon 402 error headers.
3. Cross-Agent Collaboration: Agents can verify each other's identity before exchanging sensitive data or collaborating on tasks, preventing spoofing.

Example Prompts

1. "Authenticate with the BuildersGarden API using my configured Privy signer and fetch the latest market analytics."
2. "Attempt to request the premium content from the service at api.example.com; handle the x402 payment header automatically if triggered."
3. "Sign a verification message for the current session to ensure my agent identity is linked to this workspace interaction."

Tips & Limitations

• Security First: Always keep your agent's private keys in a secure environment; consider using a Keyring Proxy with 2FA for production-grade security.
• Registry Requirements: Ensure your agent is properly registered on the ERC-8004 registry, as services will reject authentication attempts from unregistered addresses.
• Monitoring: Monitor your agent’s wallet balance if using x402 payments to ensure it has enough funds to cover expected service fees.
• SDK Support: The SDK includes modules for Next.js, Express, Hono, and Fastify, making it flexible for both client and server implementations.