# Mangrove Execution Config Schema

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

Returns the canonical execution configuration schema including default trading parameters, risk settings, transaction costs, and tunable parameter glossary for the Mangrove Agent.

## Facts

- Endpoint: GET https://api.mangrovedeveloper.ai/api/v1/config/execution-config-schema?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mangrove-execution-config-schema-4ee7db30
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__wU4REKMmrMXmXzI_Tle7

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-execution-config-schema-4ee7db30
```

Example prompt: Pull the Mangrove Agent execution config schema so I can see the default ATR period, max risk per trade limits, and transaction cost settings including fee and slippage percentages.

## When to prefer this

Use this endpoint when you need the authoritative, versioned execution configuration schema for Mangrove Agent — specifically to inspect default parameter values, understand valid ranges for tunable parameters, or confirm transaction cost assumptions before backtesting or live trading. Prefer this over documentation pages when you need machine-readable, structured config data for programmatic validation or agent decision-making.

## Known failure modes

- Invalid or unrecognized properties filter returns empty or partial schema
- Network timeout if API is under load
- 402 Payment Required if x402 payment header is missing or malformed
- Schema may be stale if Mangrove Agent version has changed

## How this service works

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

## Output

A JSON object containing: (1) defaults object with numeric values for atr_period, reward_factor, and max_risk_per_trade; (2) param_glossary with per-parameter metadata including type, min/max bounds, tunability status, and human-readable description; (3) transaction_costs object with source label, fee_pct, slippage_pct, and whether costs apply per-strategy.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "defaults": {
   "atr_period": 14,
   "reward_factor": 2,
   "max_risk_per_trade": 0.01
  },
  "param_glossary": {
   "max_risk_per_trade": {
    "max": 1,
    "min": 0,
    "type": "float",
    "status": "tunable",
    "description": "Fraction of account equity risked per trade (0.01 = 1%). Position size is derived from this and the stop distance."
   }
  },
  "transaction_costs": {
   "source": "canon",
   "fee_pct": 0.0085,
   "per_strategy": false,
   "slippage_pct": 0.0025
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mangrove-execution-config-schema-4ee7db30/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)