Execute paid HTTP requests to Zcash-required endpoints via the zimppy CLI.
npx skills add https://github.com/betterclever/zimppy --skill zimppy
Please help me install this Agent Skill. Skill: zimppy Source: https://github.com/betterclever/zimppy/tree/main Command: npx skills add https://github.com/betterclever/zimppy --skill zimppy
The zimppy skill solves the friction of making paid HTTP requests to services that require Zcash payment while keeping the transaction details private from everyone else.
Run the skill to start by checking your wallet status and then discover available paid services before making your first request.
High-intent search queries and answers about installing and using this skill.
To make paid HTTP requests requiring Zcash, you can use an automated 402-charge and session flow that performs the required ZEC payment and retries the original request. This keeps transaction details private while accessing paid REST or SSE endpoints.
The best way to set up a Zcash wallet for private API payments is by running wallet initialization and readiness checks before attempting paid calls. This verifies your wallet status and confirms the wallet is funded prior to executing requests.
Service discovery for paid Zcash API endpoints works by querying the /.well-known/payment path to find running paid services. Once discovered, you can target the correct API endpoint for your specific intent and construct the request URL.
Yes, you can perform optional dry-runs before sending actual Zcash payments to an API. This allows you to handle balance readiness and verify the automated charge or session flow without committing real funds to the paid HTTP service.
No, you do not need to manually handle HTTP 402 payment required responses. The automated flow detects the payment requirement, performs the necessary ZEC charge or session deposit, and automatically retries the original HTTP request.
When using custom session deposits for private payments, you are limited to selecting endpoints from discovered service results and must ensure correct URL construction from those endpoints. Custom deposits are optional and work alongside the standard charge flow for paid REST and SSE endpoints.
Merit-SystemsOnboards AI agents by installing AgentCash core skill and creating wallet for x402 API access.
blueskies1818Search and download GIFs from the Tenor API using curl and jq.
Shamrock2245Search the x402 bazaar for paid API services using BM25 keyword queries.
SignmanalAutomate HTTP 402 payment processing for MPP-compliant APIs.
