agents-infra_skill

This skill helps you manage AI agent infrastructure including phone, email, compute, and domains with seamless x402 payments.

Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill agents-infra

_meta.json290 B
SKILL.md12.2 KB

Overview

This skill provides infrastructure APIs for AI agents: phone numbers, SMS, voice calling, email inboxes, compute (VPS), domain registration and DNS. It supports pay-as-you-go via an on-chain x402 payment flow (USDC on Solana or Base) or persistent agent tokens. The API is RESTful and designed for automated agent orchestration and integrations.

How this skill works

You register an agent to receive a bearer token, or call paid endpoints directly and satisfy a 402 response with an on-chain USDC transfer and Payment-Signature header. Endpoints cover phone number search and provisioning, SMS send/read, full voice call control (TTS, play audio, DTMF, record, transfer), email inboxes, compute server lifecycle, and domain/DNS management. Webhooks deliver inbound SMS, voice events, and inbound email events for realtime workflows.

When to use it

Provision phone numbers and SMS for agents that need real-world contact
Automate outbound and inbound voice calls with TTS and DTMF handling
Create managed agent compute instances (VPS) for models and services
Register domains and manage DNS for agent-hosted services
Provision inboxes and process inbound/outbound email programmatically

Best practices

Register an agent and save the bearer token for repeated authenticated calls
Use webhooks to handle inbound SMS, voice events, and incoming email rather than polling
Pre-upload your SSH public key; servers use a zero-access design so private keys remain private
Call billing-required endpoints to retrieve a 402 payload and perform the on-chain USDC payment as instructed
Power off servers before resize operations and monitor server status via the status endpoint

Example use cases

An agent provisions a phone number, places TTS calls to deliver reminders, gathers keypad responses, and records confirmations
A support bot receives SMS, looks up user data, and replies via the SMS send endpoint
Spin up a VPS, deploy an agent runtime over SSH, and expose a webhook URL registered to receive call and email events
Register a domain for an agent service and programmatically update DNS records when servers change IPs

FAQ

Call any paid endpoint, receive a 402 Payment Required with on-chain instructions, then submit a USDC transfer on Solana or Base and include the Payment-Signature header to complete the request.

Do you store my SSH private key?

No. You upload only your SSH public key. The platform uses a zero-access design and cannot access your private key.