# Mangrove Signal Match

> Mangrove Signal Match is a paid API for AI agents from api.mangrovedeveloper.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-11-04).

Finds the top-k matching trading signals or rules from a library based on a natural language description, optional intent context, and market regime direction.

## Facts

- Endpoint: POST https://api.mangrovedeveloper.ai/api/v1/signals/match?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mangrove-signal-match-5f2a3d8a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UXWw6285VAmW90O4ZongE

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 mangrove-signal-match-5f2a3d8a -d '<json body>'
```

Example prompt: Find me the top 5 TRIGGER signals in Mangrove that most closely match a momentum breakout strategy in a bullish market regime, using a similarity threshold of 0.4.

## When to prefer this

Use this endpoint when an AI agent needs to map a natural language trading strategy or rule description to a pre-existing library of signals, particularly when the agent must dynamically select which Mangrove triggers or filters to activate based on user intent or market regime. Prefer this over manual signal selection when the signal space is large and fuzzy matching is needed.

## Known failure modes

- No matches found if similarity_threshold is set too high relative to available signals
- Invalid role enum value (must be TRIGGER or FILTER) causes validation error
- Empty or vague description may return low-quality or zero matches
- Malformed user_intent object may be ignored or cause a 400 error
- top_k exceeding available signals returns fewer results without error

## How this service works

Developer references for Mangrove Agent, API contracts, MCP and AI integrations.

## Output

Returns a ranked list of up to top_k matching signals (TRIGGER or FILTER type), each with a similarity score and signal metadata, filtered to those exceeding the similarity_threshold. Useful for routing agent decisions to the most relevant pre-defined trading signals or rules.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "role": {
   "enum": [
    "TRIGGER",
    "FILTER"
   ],
   "type": "string",
   "example": "TRIGGER",
   "description": "Signal role"
  },
  "top_k": {
   "type": "integer",
   "default": 5,
   "description": "Number of matches to return"
  },
  "description": {
   "type": "string",
   "description": "Natural language description of the desired signal/rule"
  },
  "user_intent": {
   "type": "object",
   "description": "Optional intent dict (e.g., from intent extractor)"
  },
  "regime_direction": {
   "type": "string",
   "description": "Market regime band"
  },
  "similarity_threshold": {
   "type": "number",
   "default": 0.3,
   "description": "Minimum similarity score to include"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mangrove-signal-match-5f2a3d8a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.mangrovedeveloper.ai](https://www.zero.xyz/host/api.mangrovedeveloper.ai/llms.txt)