Documentation

You have access to the agentcash MCP server for paid x402 API calls.

Use this progressive workflow:

1. Start with mcp__agentcash__discover_api_endpoints on the most likely origin.
2. If no endpoint matches, stop that origin flow and discover another origin.
3. If discovery returns guidanceAvailable=true but guidance is omitted, only re-run with include_guidance=true when domain-level methodology is needed.
4. Before first POST/PUT/PATCH fetch to a selected endpoint, call mcp__agentcash__check_endpoint_schema.
5. Execute with mcp__agentcash__fetch or mcp__agentcash__fetch_with_auth.

Useful origins to probe:
- https://stableenrich.dev
- https://stablesocial.dev
- https://stablestudio.dev
- https://stableupload.dev
- https://stableemail.dev

Tool summary:

  mcp__agentcash__get_wallet_info
  - Get wallet address and USDC balance on Base, Solana, or Tempo
  - Auto-creates wallet on first use (~/.agentcash/wallet.json)
  - Returns deposit link. Check before first paid API call.

  mcp__agentcash__discover_api_endpoints
  - Find x402-protected resources on an origin
  - Returns endpoint summaries plus guidance metadata
  - Use mcp__agentcash__check_endpoint_schema for detailed schema/runtime payment info

  mcp__agentcash__check_endpoint_schema
  - Probe endpoint to check x402 protection and schema
  - Returns pricing, input schema, payment methods
  - Use before POST/PUT/PATCH mcp__agentcash__fetch calls

  mcp__agentcash__fetch
  - HTTP fetch with automatic x402 payment
  - Detects 402 responses, signs payment, retries with payment headers
  - Returns response data + payment details (price, tx hash) if paid
  - For GET requests: pass parameters as query strings in URL (e.g., ?placeId=value)
  - For POST/PUT/PATCH: pass data in the body parameter
  - ALWAYS use this instead of curl/Bash for x402 endpoints

  mcp__agentcash__fetch_with_auth
  - HTTP fetch with automatic SIWX (Sign-In With X) authentication
  - Detects auth requirement, signs wallet proof, retries with credentials
  - For endpoints requiring identity verification without payment

  mcp__agentcash__redeem_invite
  - Redeem an invite code for free USDC on Base, Solana, or Tempo
  - One-time use per code. Returns amount received and transaction hash.


- Fetch rules:
  - For GET requests, include parameters as query strings in the URL (e.g., ?placeId=value); do not use the body parameter.
  - For POST requests, use the body parameter to include the request body.
  - Use mcp tools for paid endpoints, not curl/Bash.

- **IMPORTANT:** All the API endpoints below (Exa, Firecrawl, Clado, Google Maps, Apollo) are accessed via mcp__agentcash__fetch. They are NOT separate MCP tools. Call them like: mcp__agentcash__fetch(url="https://stableenrich.dev/api/clado/contacts-enrich", method="POST", body={...})
- Use the Exa and Firecrawl endpoints as advanced / better WebFetch. They will often return data that would otherwise return only javascript or blocked content.
- If you get a 403 or error when using WebSearch or WebFetch on a website, try with Exa/Firecrawl endpoints immediately as they likely can get around the blockage.
- Use Minerva (/api/minerva/resolve, /api/minerva/enrich) to get LinkedIn profile data, demographics, and personal contact info. Use Clado (/api/clado/contacts-enrich) as a fallback for email/phone enrichment from a LinkedIn URL.
- Use the Google Maps endpoints to find reviews, or other local information. Always attempt to include review information in your findings if relevant.
- **Google Maps text-search/full endpoint:** When calling POST https://stableenrich.dev/api/google-maps/text-search/full, ALWAYS use maxResultCount=1-3, never 5. Using 5 produces too much context. If you get excessive context in the response, retry with maxResultCount=1.
- All these are REST API endpoints called via mcp__agentcash__fetch - do NOT attempt to call mcp__clado__*, mcp__exa__*, mcp__google_maps__*, etc. Those tools do not exist.