# Rainmaker Gateway – Well Recommender

> Rainmaker Gateway – Well Recommender is a paid API for AI agents from rainmaker-gateway.mmelnyk2000.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-30).

Routes a natural-language need to the best-matching Rainmaker 'well' (AI tool/service), returning its ID, origin URL, tool name, price, MCP endpoint, and reasoning for the match.

## Facts

- Endpoint: POST https://rainmaker-gateway.mmelnyk2000.workers.dev/mcp?utm_source=zero.xyz#recommend-well#recommend-well
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/rainmaker-gateway-well-recommender-e57502ba
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MdrW5KdeBu0Gdj5XK6FM9

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability rainmaker-gateway-well-recommender-e57502ba -d '<json body>'
```

Example prompt: I need to find the best Rainmaker well for summarizing long documents — recommend one and give me its MCP URL so I can connect to it directly.

## When to prefer this

Use this endpoint when an agent needs to dynamically discover and route to the best Rainmaker well for a given task without knowing the well catalog in advance. It is ideal for orchestrator agents that need to delegate subtasks to specialized AI tools listed on Rainmaker. If cost is a concern and discovery (not recommendation quality) is sufficient, use the free list-wells endpoint instead. Prefer this over manually browsing the Rainmaker catalog when the task description is in natural language and you want a ranked, reasoned recommendation.

## Known failure modes

- No matching well found for the given query — returns empty or error response
- Ambiguous query leads to a low-confidence or suboptimal match
- Payment of $0.005 USDC via x402 fails if wallet is underfunded or x402 is not configured
- Rate limiting or worker timeout on the Cloudflare Workers edge function
- Stale well catalog — a recommended well may have changed its price or gone offline

## How this service works

Keyword-route a natural-language need to the best Rainmaker well ($0.005 USDC via x402). Returns well id, origin, tool, price_usd, mcp URL, and why. After recommend, open that origin's /mcp directly — gateway does not proxy (avoids double-charge). Free alternative: list-wells.

## Output

Returns a JSON object containing: well_id (unique identifier), origin (the well's base URL to call directly), tool (tool name), price_usd (cost per call), mcp_url (the MCP endpoint to connect to), and why (a short explanation of why this well was recommended for the query). The gateway does not proxy the actual well call — the agent must open the returned origin/mcp URL directly to avoid double-charging.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/rainmaker-gateway-well-recommender-e57502ba/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from rainmaker-gateway.mmelnyk2000.workers.dev](https://www.zero.xyz/host/rainmaker-gateway.mmelnyk2000.workers.dev/llms.txt)