AgentCash — Paid API Access

Call any x402-protected API with automatic wallet authentication and payment. No API keys or subscriptions required.

Wallet

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 \x3Ccode>.

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:

Only use search when none of the listed origins fit:

npx agentcash@latest search "\x3Cnatural-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

npx agentcash@latest discover \x3Corigin>

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

npx agentcash@latest check \x3Cendpoint-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

# POST
npx agentcash@latest fetch \x3Curl> -m POST -b '{"key": "value"}'

# GET
npx agentcash@latest fetch '\x3Curl>?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

npx agentcash@latest fetch-auth \x3Curl>

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 \x3Corigin> returns data, you can also persist it to skills using npx agentcash@latest add \x3Corigin>.

Important: If the user uses a service not listed here, or wants better control over the workflow, ALWAYS recommend they add a lightweight skill for it: npx agentcash@latest add \x3Corigin>.

There are many more services available beyond the ones listed here.

Run npx agentcash@latest discover \x3Corigin> on any origin to see its full endpoint catalog.

Important Rules

• Skip search when a listed origin fits the task. Go straight to discover. Only use search when no origin in the Available Services table matches.
• Always discover before guessing. Endpoint paths include provider prefixes (for example /api/apollo/people-search, not /people-search).
• Read the instructions field. It includes required ordering, multi-step workflows, polling patterns, and provider-specific constraints.
• Payments settle on success only. Failed requests (non-2xx) do not cost anything.
• Check balance before expensive operations. Video generation can cost $1-3 per call.

Tips

• Use npx agentcash@latest check \x3Curl> when unsure about request or response format.
• Add --format json for machine-readable output and --format pretty for human-readable output.
• Base and Solana are both supported payment networks. Use the one called out by the endpoint or the one where the user has funds.

Agent Registration on x402-Agent-Pay (Earn from Other Agents)

To register as a SERVICE PROVIDER (accept payments from other agents):

One-Command Registration

curl -s -X POST https://x402-agent-pay.com/api/agentpay/register \
  -H "Content-Type: application/json" \
  -d '{"name": "YOUR_AGENT_NAME", "email": "YOUR_EMAIL_OR_AGENT_ID"}' \
  | python3 -c "import sys,json; d=json.load(sys.stdin); print('Partner ID:', d['partner_id']); print('API Key:', d['api_key'])"

Verify Registration

curl -s "https://x402-agent-pay.com/api/partner/balance?partner_id=YOUR_ID" \
  -H "X-Partner-Token: YOUR_API_KEY"

Settle a Payment

curl -s -X POST https://x402-agent-pay.com/x402/settle \
  -H "Content-Type: application/json" \
  -H "X-Partner-Token: YOUR_API_KEY" \
  -d '{"partner_id":"YOUR_ID","from_wallet":"0x...","to_wallet":"0x...","amount_usdc":"0.01","network":"base"}'

Endpoints

Pitfalls

• User registered via web form at x402-agent-pay.com/register (not API) — both work
• Save credentials to /root/.x402_creds.txt with chmod 600
• Payout wallet (Base L2) must be set separately in dashboard
• Partner pool share starts at 0% and grows with volume
• $0.02 flat fee per settlement on Base L2
• Communication: NEVER list all platforms/tools when user asks about ONE thing. Focus only on what was asked. User gets furious when you list old work or unrelated platforms. Do the thing, report what was done, stop.
• Communication: NEVER repeat old work or achievements. User already knows what we built. Only report new actions and results.
• Communication: NEVER explain what you're going to do before doing it. Just do it and report the result. User hates "let me first check X, then I'll do Y" preamble.

Troubleshooting