mag3nt-com/openclaw-skill

Name: openclaw-skill
Author: mag3nt-com

Openclaw Skills

★ 1 langJavaScript licenseMIT updated2026-06-07

overview

mag3nt-pay is an agent payment skill that enables AI agents to autonomously pay for APIs that return HTTP 402 Payment Required errors. It works by detecting payment protocols from response headers, decoding the payment challenge, and settling the transaction using USDC via Mag3nt virtual cards. The skill supports Base, Solana, and most EVM networks, allowing agents to handle micropayments and subscriptions without human intervention. It is compatible with OpenClaw, Hermes Agent, and any framework following the agentskills.io standard.

Automates payments for HTTP 402 responses using USDC
Supports Pay Link, x402, MPP, and AP2 protocols
Compatible with OpenClaw, Hermes Agent, and agentskills.io standard

full readme from github

mag3nt-pay — Agent Payment Skill

Give your AI agent a wallet. This skill teaches agents to autonomously pay for any API that returns HTTP 402 — using USDC via Mag3nt virtual cards. Supports Base, Solana and most EVMs. Compatible with OpenClaw, Hermes Agent, and any framework supporting the agentskills.io standard.

Install

OpenClaw:

openclaw skill install mag3nt-pay

Hermes Agent:

hermes skills tap add mag3nt-com/openclaw-skill

Manual (any agentskills.io framework): Copy the mag3nt-pay/ directory into your agent's skills folder.

Setup (60 seconds)

Get a free API key at mag3nt.com
Create an agent card in the dashboard
Fund it with USDC (Base, Solana, or any supported EVM)
Set your env vars:

export MAG3NT_API_KEY=mag3nt_live_your_key
export MAG3NT_CARD_ID=mag3nt_your_card_id
export MAG3NT_CARD_TOKEN=tok_your_card_token

Test it:

openclaw agent --message "Check my Mag3nt card balance"

What It Does

When your agent calls any API and gets back an HTTP 402 Payment Required, this skill automatically:

Detects the payment protocol from response headers
Decodes the challenge (amount, recipient, network)
Checks the agent's card balance
Pays using the correct protocol (x402, MPP, AP2, or Pay Link)
Retries the original request with the payment receipt

The agent handles all of this without human intervention.

Supported Protocols

Protocol	Header / Signal	Use Case
Pay Link	`paylink` object in 402 body	Universal — any merchant
x402	`PAYMENT-REQUIRED` header	Single pay-per-request
MPP	`WWW-Authenticate: Payment`	Streaming micropayments
AP2	`AP2-Challenge` header	Recurring / mandated payments

How It Works

Your Agent                    Paid API                   Mag3nt
    │                            │                         │
    ├── GET /api/data ──────────►│                         │
    │◄── 402 + challenge ────────┤                         │
    │                            │                         │
    │  [mag3nt-pay skill activates]                        │
    │                            │                         │
    ├── Check balance ──────────────────────────────────────►
    │◄── Balance: $50 USDC ─────────────────────────────────┤
    │                            │                         │
    ├── Pay $0.10 ──────────────────────────────────────────►
    │◄── Receipt: tx_abc123 ────────────────────────────────┤
    │                            │                         │
    ├── GET /api/data ──────────►│                         │
    │   + X-Payment: tx_abc123   │                         │
    │◄── 200 OK + data ──────────┤                         │
    │                            │                         │

Example Conversations

Pay Link (most common):

You:   "Run a background check on this company via screening.example.com"

Agent: Calling the screening API...
       Received HTTP 402 — Pay Link detected in response body.
       Amount: 0.10 USDC | Merchant: screening.example.com
       Card balance: 49.90 USDC — sufficient.
       Settling Pay Link PL_abc123...
       Payment settled. Retrying request...
       Done. Here are the screening results: [...]

x402 (single pay-per-request):

You:   "Fetch the climate risk report from data.example.com"

Agent: Calling the data API...
       Received HTTP 402 — x402 protocol detected (PAYMENT-REQUIRED header).
       Amount: 0.25 USDC | Recipient: 0x1BD3...9D00
       Card balance: 49.65 USDC — sufficient.
       Payment settled. Transaction: tx_8f2a...
       Retrying with receipt...
       Done. Here's the climate risk report: [...]

MPP (streaming micropayments):

You:   "Stream inference results from compute.example.com"

Agent: Calling the compute API...
       Received HTTP 402 — MPP protocol detected (WWW-Authenticate header).
       Amount: 0.05 USDC per request | Session-based billing.
       Card balance: 49.40 USDC — sufficient.
       Payment session opened. Session: sess_7d1e...
       Streaming results: [...]

AP2 (recurring mandate):

You:   "Subscribe to the real-time market feed at data.example.com"

Agent: Calling the market feed API...
       Received HTTP 402 — AP2 protocol detected (AP2-Challenge header).
       Amount: 1.00 USDC | Mandate: recurring, max 5.00 USDC/day.
       Card balance: 48.40 USDC — sufficient.
       Mandate executed. Transaction: tx_3c9f...
       Market feed connected: [...]

Directory Structure

mag3nt-pay/
├── SKILL.md              # Skill definition (frontmatter + instructions)
├── references/
│   ├── setup.md          # SDK configuration and credentials
│   ├── balance.md        # Balance check before paying
│   ├── x402-pay.md       # x402 single-request payments
│   ├── mpp-pay.md        # MPP streaming micropayments
│   ├── ap2-pay.md        # AP2 mandate-based payments
│   └── paylink-pay.md    # Pay Link universal payments
└── scripts/
    └── quickstart.mjs    # Run a balance check in one command

Quick Test

After setting your env vars, run the quickstart script directly:

node mag3nt-pay/scripts/quickstart.mjs

This checks your card balance and confirms the SDK is working.

Requirements

Node.js 18+ or Python 3.8+
@mag3nt/sdk (npm) or mag3nt (PyPI)
A Mag3nt account with a funded agent card

License

MIT — see LICENSE