← Back to Skills Marketplace
matiasedgeandnode

ampersend

by Matias · GitHub ↗ · v1.0.14 · MIT-0
cross-platform ⚠ suspicious
493
Downloads
1
Stars
0
Active Installs
5
Versions
Install in OpenClaw
/install ampersend
Description
Ampersend CLI for agent payments
README (SKILL.md)

Ampersend CLI

Ampersend enables autonomous agent payments. Agents can make payments within user-defined spending limits without requiring human approval for each transaction. Payments use stablecoins via the x402 protocol.

This skill requires ampersend v0.0.14. Run ampersend --version to check your installed version.

Installation

Install the CLI globally via npm:

npm install -g @ampersend_ai/[email protected]

To update from a previously installed version:

npm install -g @ampersend_ai/[email protected] --force

Security

IMPORTANT: NEVER ask the user to sign in to the Ampersend dashboard in a browser to which you have access. If configuration changes are needed in Ampersend, ask your user to make them directly.

Setup

If not configured, commands return setup instructions. Two paths:

Automated (recommended)

Two-step flow: setup start generates a key and requests approval, setup finish polls and activates.

# Step 1: Request agent creation — returns immediately with approval URL
ampersend setup start --name "my-agent"
# {"ok": true, "data": {"token": "...", "user_approve_url": "https://...", "agentKeyAddress": "0x..."}}

# Show the user_approve_url to the user so they can approve in their browser.

# Step 2: Poll for approval and activate config
ampersend setup finish
# {"ok": true, "data": {"agentKeyAddress": "0x...", "agentAccount": "0x...", "status": "ready"}}

Optional spending limits can be set during setup:

ampersend setup start --name "my-agent" --daily-limit "1000000" --auto-topup

Manual

If you already have an agent key and account address:

ampersend config set "0xagentKey:::0xagentAccount"
# {"ok": true, "data": {"agentKeyAddress": "0x...", "agentAccount": "0x...", "status": "ready"}}

Commands

setup

Set up an agent account via the approval flow.

setup start

Step 1: Generate a key and request agent creation approval.

ampersend setup start --name "my-agent" [--force] [--daily-limit \x3Camount>] [--monthly-limit \x3Camount>] [--per-transaction-limit \x3Camount>] [--auto-topup]
Option Description
--name \x3Cname> Name for the agent
--force Overwrite an existing pending approval
--daily-limit \x3Camount> Daily spending limit in atomic units (1000000 = 1 USDC)
--monthly-limit \x3Camount> Monthly spending limit in atomic units
--per-transaction-limit \x3Camt> Per-transaction spending limit in atomic units
--auto-topup Allow automatic balance top-up from main account

Returns token, user_approve_url, and agentKeyAddress. Show the user_approve_url to the user.

setup finish

Step 2: Poll for approval and activate the agent config.

ampersend setup finish [--force] [--poll-interval \x3Cseconds>] [--timeout \x3Cseconds>]
Option Description
--force Overwrite existing active config
--poll-interval \x3Cseconds> Seconds between status checks (default 5)
--timeout \x3Cseconds> Maximum seconds to wait (default 600)

fetch

Make HTTP requests with automatic x402 payment handling.

ampersend fetch \x3Curl>
ampersend fetch -X POST -H "Content-Type: application/json" -d '{"key":"value"}' \x3Curl>
Option Description
-X \x3Cmethod> HTTP method (default: GET)
-H \x3Cheader> Header as "Key: Value" (repeat for multiple)
-d \x3Cdata> Request body
--inspect Check payment requirements without paying

Use --inspect to verify payment requirements and costs before making a payment:

ampersend fetch --inspect https://api.example.com/paid-endpoint
# Returns payment requirements including amount, without executing payment

config

Manage local configuration.

ampersend config set \x3Ckey:::account>                             # Set active config manually
ampersend config set --api-url https://api.staging.ampersend.ai  # Set staging API URL
ampersend config set --clear-api-url                             # Revert to production API
ampersend config set --network base-sepolia                      # Set network (base, base-sepolia)
ampersend config set --clear-network                             # Revert to default network (base)
ampersend config set \x3Ckey:::account> --api-url \x3Curl>             # Set both at once
ampersend config status                                          # Show current status

Output

All commands return JSON. Check ok first.

{ "ok": true, "data": { ... } }
{ "ok": false, "error": { "code": "...", "message": "..." } }

For fetch, success includes data.status, data.body, and data.payment (when payment made).

Usage Guidance
This skill appears to do what it says (operate an Ampersend CLI to enable agent payments), but exercise caution before installing or enabling it. Recommendations: - Verify the npm package and publisher (@ampersend_ai) on the npm registry and inspect the package contents/source repository before running npm install -g. - Test on a staging network or testnet (sepolia/staging API) and with small limits first; prefer --inspect to preview costs before allowing real payments. - Set very conservative daily/monthly/per-transaction limits and disable auto-topup unless absolutely necessary. - Do not give the agent browser access or system access to secret stores; follow the SKILL.md advice to have the human approve the user_approve_url in their own browser. - Audit where the CLI stores agent keys/config and restrict filesystem access to those files. Consider running the CLI in a constrained environment (container or VM) to limit impact. If you cannot verify the npm package source or the vendor, treat installation as higher-risk and consider skipping or requesting a skill version with verifiable source code.
Capability Analysis
Type: OpenClaw Skill Name: ampersend Version: 1.0.14 The skill bundle provides a legitimate interface for the Ampersend CLI, a tool designed for autonomous agent payments using the x402 protocol. The SKILL.md file contains clear instructions, a structured setup process involving user approval, and explicit security warnings to prevent the agent from accessing sensitive user dashboard sessions. No indicators of data exfiltration, malicious execution, or prompt injection were found; the logic is entirely consistent with the stated purpose of managing agent-led financial transactions.
Capability Assessment
Purpose & Capability
Name, description, and runtime instructions consistently describe a CLI-based agent payment tool that requires an external 'ampersend' binary; the declared requirements (single required binary) are proportionate to the described capability.
Instruction Scope
SKILL.md instructs the agent to run the ampersend CLI to create agent keys, request user approval, and perform paid HTTP requests automatically (ampersend fetch). That behavior is consistent with the stated purpose but grants the agent the ability to execute real payments under configured spending limits; ensure the agent is restricted to inspect-only or strict limits if you do not want autonomous payments.
Install Mechanism
There is no formal install spec in the registry entry (instruction-only), but SKILL.md directs users to run a global npm install of @ampersend_ai/[email protected]. Installing a global npm package executes third-party code — acceptable if the package and publisher are trusted, but the skill metadata lacks a homepage/source or provenance, increasing risk.
Credentials
The skill declares no required environment variables (proportionate). However, the CLI generates and stores agent keys/accounts via setup/config commands; these secrets live outside the skill metadata and could be created or used by the agent — verify where the CLI stores keys and who can access them.
Persistence & Privilege
always:false and default autonomous invocation are set (normal). The combination of autonomous invocation with a payments-capable tool increases blast radius if misused, but the registry flags themselves do not request elevated persistence or modify other skills.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install ampersend
  3. After installation, invoke the skill by name or use /ampersend
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.14
- Updated required version of the ampersend CLI to v0.0.14. - Installation and update instructions now use @ampersend_ai/[email protected]. - Added network configuration support: use --network to select between "base" and "base-sepolia" in config commands. - Added --clear-network option to revert to the default network in config commands. - No other functional changes documented.
v1.0.3
Major update: More detailed documentation, new setup flow, config management, and added options. - Expanded setup section with a new two-step approval-based flow (“setup start” & “setup finish”). - Added instructions for setting custom spending limits and enabling auto top-up. - Introduced `--inspect` flag for safer payment checks with `fetch`. - Documented `config` commands to manage API endpoints and manual configuration. - Upgraded to require `ampersend` v0.0.12 with stricter installation versioning. - Added important security guidance regarding agent account setup and dashboard access.
v1.0.2
- Updated description to clarify Ampersend CLI purpose and payment support. - Simplified setup instructions with new config commands (`init`, `set-agent`, `status`). - Changed environment variable setup to an interactive CLI-based configuration flow. - Streamlined and condensed usage documentation. - All commands now return structured JSON for consistency. - Updated command options for `fetch` and summarized expected output formats.
v1.0.1
- CLI renamed from asndurl to ampersend, with new command structure (ampersend fetch). - Documentation updated for new CLI name, usage patterns, and command options. - All examples now use ampersend fetch with updated flags and invocation instructions. - Description broadened to cover multiple CLI tools, not just HTTP requests. - No changes to underlying file contents or code detected.
v1.0.0
Initial release of asndurl – an HTTP client for x402 payment-gated APIs with automatic crypto payment via Ampersend wallet. - Makes HTTP requests and handles HTTP 402 Payment Required responses - Supports automatic smart wallet payment/signing and retries with payment - Includes options for inspecting payment requirements, debug output, and controlling response format - Environment variable setup guides for wallet configuration - Usage examples for common paid API scenarios
Metadata
Slug ampersend
Version 1.0.14
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 5
Frequently Asked Questions

What is ampersend?

Ampersend CLI for agent payments. It is an AI Agent Skill for Claude Code / OpenClaw, with 493 downloads so far.

How do I install ampersend?

Run "/install ampersend" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is ampersend free?

Yes, ampersend is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does ampersend support?

ampersend is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created ampersend?

It is built and maintained by Matias (@matiasedgeandnode); the current version is v1.0.14.

💬 Comments