# Rainmaker Gateway Well Recommender

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

Routes a natural-language capability need to the best-matching Rainmaker well, returning its ID, origin MCP URL, tool name, price, and a rationale for the match.

## Facts

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

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

Example prompt: I need to extract tables from a PDF — can you figure out which Rainmaker well is best suited for that and give me its MCP URL and price?

## When to prefer this

Use this endpoint when an AI agent needs to dynamically discover the right Rainmaker MCP tool for a user's capability need at runtime, rather than hardcoding a specific well. It is the entry point for Rainmaker's marketplace — ideal when the right tool is not known in advance. For free discovery without spending USDC, use the sibling list-wells endpoint instead.

## Known failure modes

- Ambiguous or very broad need string may yield a suboptimal or generic match
- No suitable well exists for a highly niche need, returning an empty or low-confidence recommendation
- Network or Workers runtime errors returning 5xx
- Payment failure via x402 if USDC balance is insufficient or payment header is malformed
- Rate limiting if too many requests are made in rapid succession

## 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 recommended well's ID, the origin domain of the well provider, the specific tool name, the price in USD, the MCP URL to connect to directly, and a brief explanation of why this well was chosen for the stated need.

## 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-5ef5c02d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from rainmaker-gateway.rainmaker-wells.workers.dev](https://www.zero.xyz/host/rainmaker-gateway.rainmaker-wells.workers.dev/llms.txt)