# 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-29).

Routes a natural-language capability need to the best-matched Rainmaker well (paid AI tool), returning the well ID, origin, tool name, price, MCP URL, and reasoning.

## Facts

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

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-e1169857 -d '<json body>'
```

Example prompt: I need to extract tables from a PDF — which Rainmaker well should I use for that? Give me the best match with its price and MCP URL so I can call it directly.

## When to prefer this

Use this endpoint when an agent needs to dynamically discover which Rainmaker well best satisfies a natural-language capability need, especially within automated pipelines that must route tasks across multiple specialized MCP tools. Prefer this over manually browsing Rainmaker wells or using the free list-wells endpoint when you need a targeted recommendation with reasoning rather than an unfiltered list.

## Known failure modes

- Vague or ambiguous 'need' string may return a poorly matched well
- No matching well exists for a highly niche or unsupported capability
- Service may be unavailable if the Cloudflare Worker is down
- Double-charging risk if the agent mistakenly calls the gateway as a proxy instead of connecting directly to the returned origin
- Returned well may be temporarily offline or have changed its pricing

## 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. Provided as is, with no warranty or guarantee of accuracy or fitness. Nothing is stored.

## Output

A JSON object containing the matched well's ID, its origin URL (the actual MCP server to call directly), the tool name, price in USD, the MCP endpoint URL, and a plain-English explanation of why this well was chosen for the stated need. The gateway does not proxy the call, so the agent must follow up by connecting to the returned origin MCP URL directly.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "need"
 ],
 "properties": {
  "need": {
   "type": "string",
   "description": "Natural-language need, e.g. 'extract tables from a PDF' or 'watch if this URL changed'."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/rainmaker-gateway-well-recommender-e1169857/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)