
Agentcash
Call x402/MPP paid APIs with wallet USDC—enrich, scrape, social, media, email, phone—without API keys via the agentcash CLI.
Overview
agentcash is an agent skill most often used in Build (also Validate, Grow) that pays for x402/MPP API calls from a wallet so agents can enrich, scrape, generate media, and message without API keys.
Install
npx skills add https://github.com/merit-systems/agentcash-skills --skill agentcashWhat is this skill?
- Pay-per-call x402/MPP on Base, Solana, and Tempo—no API keys, wallet pays per request
- Documented SERVICE origins: stableenrich, stablesocial, stablestudio, stableupload, stableemail, stablephone, stablejobs
- CLI wallet flows: balance, accounts, redeem, fund via npx agentcash@latest
- Trigger routing: skip search when task matches a listed origin; search only when none fit
- 10+ named SERVICE origins (stableenrich through stablebrowser)
- CLI metadata version 2.2
Adoption & trust: 1.4k installs on skills.sh; 11 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need paid third-party APIs for research or automation but do not want to manage keys, subscriptions, or per-vendor billing for every integration.
Who is it for?
Solo builders shipping agents that need on-demand enrich, scrape, social, email, or media APIs funded by a single USDC wallet.
Skip if: Production backends that require fixed enterprise API contracts, strict SOC2 key custody, or fully offline/air-gapped workflows.
When should I use this skill?
Task matches research, enrich, scrape, x402, mpp, agentcash, or a listed stable* origin—use discover → fetch; search only if no origin fits.
What do I get? / Deliverables
After the skill runs, the agent selects the right stable* origin, checks wallet balance, and executes paid calls with automatic x402 payment.
- Paid API response payloads
- Balance-aware call plan
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Build/integrations because the skill wires agents to external paid services through discover, fetch, and balance commands. Integrations subphase matches pay-per-call third-party APIs (stableenrich, stablesocial, stablestudio, etc.) orchestrated from the agent.
Where it fits
Wire an agent tool chain that discover→fetch calls stablebrowser or stablestudio on demand.
Pull TikTok or Instagram data through stablesocial for a distribution experiment.
How it compares
Wallet pay-per-call integration skill—not a traditional API-key MCP wrapper or self-hosted scraper.
Common Questions / FAQ
Who is agentcash for?
Agent builders who want merit-systems stable* paid APIs via x402 without maintaining separate vendor API keys.
When should I use agentcash?
In Validate when prototyping enrichment or landing research; in Build when wiring agent tools; in Grow when automating outreach, social, or content pipelines—whenever triggers like scrape, x402, or agentcash match a listed SERVICE origin.
Is agentcash safe to install?
It involves network calls and wallet spend—review the Security Audits panel on this Prism page and fund wallets with limits you accept.
SKILL.md
READMESKILL.md - Agentcash
# AgentCash — Paid API Access Call any x402-protected API with automatic wallet authentication and payment. No API keys or subscriptions required. ## Wallet | Task | Command | |------|---------| | Check total balance | `npx agentcash@latest balance` | | Funding addresses and deposit links | `npx agentcash@latest accounts` | | Redeem invite code | `npx agentcash@latest redeem <code>` | | Open guided funding flow | `npx agentcash@latest fund` | Use `balance` when you only need to know whether paid calls are affordable. Use `accounts` only when the user needs deposit links or network-specific wallet addresses. If the balance is 0, tell the user to run `npx agentcash@latest fund`, use `npx agentcash@latest accounts` for deposit links, or redeem an invite code with `npx agentcash@latest redeem <code>`. ## Using Services ### 1. Pick an origin — or search **Check the Available Services table below first.** If any origin clearly covers the task, skip search entirely and jump to step 2 (discover). Examples: | Task | Origin (skip search) | |------|---------------------| | Look up a person or company | `stableenrich.dev` | | Generate an image or video | `stablestudio.dev` | | Get Instagram/TikTok data | `stablesocial.dev` | | Send an email | `stableemail.dev` | | Upload a file | `stableupload.dev` | **Only use search when none of the listed origins fit:** ```bash npx agentcash@latest search "<natural-language query>" ``` Example: `npx agentcash@latest search "send physical mail"` or `npx agentcash@latest search "generate music"` Returns matching origins with endpoints and pricing. Default output is JSON (`--format pretty` for human-readable). ### 2. Discover endpoints on a service ```bash npx agentcash@latest discover <origin> ``` Example: `npx agentcash@latest discover https://stableenrich.dev` Read the output carefully. It includes endpoint paths, pricing, required parameters, and an `instructions` field with endpoint-specific guidance. ### 3. Check a specific endpoint before calling it ```bash npx agentcash@latest check <endpoint-url> ``` Returns the request and response schema plus pricing guidance. Use this before `fetch` to avoid 400 errors from wrong field names. ### 4. Make the request ```bash # POST npx agentcash@latest fetch <url> -m POST -b '{"key": "value"}' # GET npx agentcash@latest fetch '<url>?param=value' ``` `fetch` handles both paid routes and SIWX routes. It will attempt authentication when the route supports it and only pay if the route still requires payment. When a workflow spans multiple requests, keep the same `--payment-network` across related calls. ### 5. `fetch-auth` is a legacy alias ```bash npx agentcash@latest fetch-auth <url> ``` `fetch-auth` still works, but it is a deprecated alias for `fetch`. Prefer `fetch` for all new workflows. ## Available Services Any endpoint that is payment-protected can be accessed with AgentCash. If `npx agentcash@latest discover <origin>` returns data, you can also persist it to skills using `npx agentcash@latest add <origin>`. **Important**: If the user uses a service