AgentCash Onboarding
Description
Set up AgentCash for pay-per-call access to premium APIs via x402 micropayments. Creates a wallet, optionally redeems invite credits, and installs the core AgentCash skill.
Triggers
- agentcash
- agent cash
- set up agentcash
- onboard agentcash
- install agentcash
- agentcash wallet
- invite code agentcash
- x402
- pay per call
- micropayments api
Instructions
AgentCash gives EloPhanto pay-per-call access to premium APIs via x402 micropayments. This is a one-time setup: wallet creation, optional invite credits, and core skill integration.
Onboarding Flow
When the user wants to set up AgentCash:
Run onboard
If the user has an invite code:
npx agentcash@latest onboard <invite-code>
Without an invite code:
npx agentcash@latest onboard
This creates a wallet and installs the core AgentCash skill. Without a code the user is prompted with a link to deposit or redeem credits later.
Check balance
npx agentcash wallet info
Shows wallet address, USDC balance, and deposit link. If balance is 0, direct the user to https://agentcash.dev/onboard to get free credits.
Redeem a code later (if they skipped it during onboard)
npx agentcash wallet redeem <invite-code>
After Onboarding
Once setup is complete the core AgentCash skill (installed by the onboard command) handles:
- Discovering paid endpoints:
npx agentcash discover <origin>
- Making paid API requests:
npx agentcash fetch <url>
- Wallet management: balance, redeem, deposit
Deposits accepted as USDC on Base or Solana.
Verify
- The intended other agent / tool / channel actually received the message; an ack, message ID, or response payload is captured
- Identity, scopes, and permissions used by the call were the minimum required; over-permissioned tokens are called out
- Failure handling was exercised: at least one retry/timeout/permission-denied path is shown to behave as designed
- Hand-off context passed to the next actor is complete enough that the receiver could act without a follow-up question
- Any state mutated (config, memory, queue, file) is listed with before/after values, not just 'updated'
- Sensitive material (keys, tokens, PII) was redacted from logs/transcripts shared in the verification evidence
Resources
1---2name: agentcash-onboarding3description: AgentCash Onboarding4---5# AgentCash Onboarding67## Description8Set up AgentCash for pay-per-call access to premium APIs via x402 micropayments. Creates a wallet, optionally redeems invite credits, and installs the core AgentCash skill.910## Triggers11- agentcash12- agent cash13- set up agentcash14- onboard agentcash15- install agentcash16- agentcash wallet17- invite code agentcash18- x40219- pay per call20- micropayments api2122## Instructions2324AgentCash gives EloPhanto pay-per-call access to premium APIs via x402 micropayments. This is a one-time setup: wallet creation, optional invite credits, and core skill integration.2526### Onboarding Flow2728When the user wants to set up AgentCash:29301. **Run onboard**3132 If the user has an invite code:33 ```bash34 npx agentcash@latest onboard <invite-code>35 ```3637 Without an invite code:38 ```bash39 npx agentcash@latest onboard40 ```4142 This creates a wallet and installs the core AgentCash skill. Without a code the user is prompted with a link to deposit or redeem credits later.43442. **Check balance**45 ```bash46 npx agentcash wallet info47 ```48 Shows wallet address, USDC balance, and deposit link. If balance is 0, direct the user to https://agentcash.dev/onboard to get free credits.49503. **Redeem a code later** (if they skipped it during onboard)51 ```bash52 npx agentcash wallet redeem <invite-code>53 ```5455### After Onboarding5657Once setup is complete the core AgentCash skill (installed by the onboard command) handles:58- Discovering paid endpoints: `npx agentcash discover <origin>`59- Making paid API requests: `npx agentcash fetch <url>`60- Wallet management: balance, redeem, deposit6162Deposits accepted as USDC on Base or Solana.6364## Verify6566- The intended other agent / tool / channel actually received the message; an ack, message ID, or response payload is captured67- Identity, scopes, and permissions used by the call were the minimum required; over-permissioned tokens are called out68- Failure handling was exercised: at least one retry/timeout/permission-denied path is shown to behave as designed69- Hand-off context passed to the next actor is complete enough that the receiver could act without a follow-up question70- Any state mutated (config, memory, queue, file) is listed with before/after values, not just 'updated'71- Sensitive material (keys, tokens, PII) was redacted from logs/transcripts shared in the verification evidence7273## Resources74- Homepage: https://agentcash.dev75- Onboard / get credits: https://agentcash.dev/onboard