bloomfilter

What This Skill Does

The bloomfilter skill enables your OpenClaw agent to interact directly with the Bloomfilter domain registration platform. It provides a seamless interface for querying domain availability, retrieving real-time pricing for various TLDs, and executing domain registrations or renewals. The skill leverages the innovative x402 payment protocol, allowing the agent to pay for domain services using USDC on the Base network. Beyond registration, the skill supports full lifecycle management of DNS records, ensuring your domains are correctly pointed to your infrastructure. Authentication is handled securely through EIP-4361 Sign-In With Ethereum (SIWE) messages, ensuring all account-related actions are cryptographically verified and tied directly to your wallet.

Installation

To integrate this skill into your OpenClaw environment, use the following CLI command: clawhub install openclaw/skills/skills/eronmmer/bloomfilter Once installed, ensure your agent environment is configured with an EVM_PRIVATE_KEY to enable the x402-compatible HTTP client to handle USDC payments and SIWE authentication autonomously.

Use Cases

• Automating the purchase of domains for new side projects or deployments.
• Managing DNS zone configurations dynamically for microservices or staging environments.
• Keeping track of domain expiration dates and automating the renewal process via USDC payments.
• Performing bulk domain availability checks across multiple TLDs to support naming research.

Example Prompts

1. "Check if 'ai-agent-demo.xyz' is available and what the registration cost is in USDC."
2. "Register 'my-new-startup.com' for 1 year and set an A record pointing to my server at 192.168.1.1."
3. "List all current DNS records for 'example.com' registered under my account."

Tips & Limitations

• Wait Times: After registering a new domain, please wait at least 30 seconds before attempting to add DNS records to ensure the zone has fully propagated.
• Sequential Operations: Always perform DNS mutations one at a time. Concurrent requests may result in conflicts or API errors.
• Security: Your EVM_PRIVATE_KEY is used exclusively for client-side signing of SIWE and x402 payloads. It remains local to your machine at all times.
• Async Jobs: Some registrations may trigger async provisioning; use the provided job status endpoint if the initial request returns a 202 status code.