# Lucky CIN Leverage Calculator

> Lucky CIN Leverage Calculator is a paid API for AI agents from lucky-x402.onrender.com, paid per call via x402, $0.3/call, status unknown (last checked 2026-10-29).

Computes a safe maximum leverage verdict for a crypto trade given entry, stop-loss, equity, and risk parameters, with account-survival analysis

## Facts

- Endpoint: POST https://lucky-x402.onrender.com/x402/leverage-calc?utm_source=zero.xyz
- Price: $0.3/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lucky-cin-leverage-calculator-33b3d2bc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FHvgWoXqS3UgUUqsTSOMI

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 lucky-cin-leverage-calculator-33b3d2bc -d '<json body>'
```

Example prompt: I have $2000 in equity and want to trade ETHUSDT with an entry at 3400, a stop loss at 3200, and I'm willing to risk 2% per trade — what's the maximum safe leverage I should use, and can I trade at all?

## When to prefer this

Use this endpoint when you need a principled, risk-first maximum leverage verdict for a crypto derivatives trade rather than a naive position-size formula. It uniquely incorporates exchange instrument data (min notional, actual max leverage from OKX/ByBit), backtested survival statistics (B-035), and a liquidation-beyond-stop invariant. Prefer it over generic position-size calculators when you need to know the binding constraint (survival cap vs risk fraction vs exchange limit) and want an explicit 'tradable' go/no-go verdict.

## Known failure modes

- Missing required fields (entry, equity, symbol, stop_loss) returns a validation error
- Symbol not found on supported exchanges returns an instrument_error in the response
- Stop loss equal to or beyond entry results in zero or negative stop distance, causing a calculation error
- Equity of zero or negative is invalid
- take_profit or risk_per_trade values outside plausible ranges may produce unexpected binding constraints
- Exchange max leverage set below 1 may produce degenerate results
- Network timeout from the Render-hosted service during cold start

## How this service works

crypto-intelligence verdicts (CIN) + creative-judgment/QC + post-gen media-ops — agent-facing

## Output

Returns a 'verdict' field with the maximum safe leverage (e.g. 'MAX 0.67x'), the numeric leverage value, a 'tradable' boolean, the binding limit that constrains the leverage (e.g. risk per trade, survival cap, or liquidation distance), notional USD position size, stop distance percentage, max loss at stop in USD, liquidation distance or a note that none exists below 1x, round-trip cost as a percentage of equity, instrument details (venue, instrument name, max leverage, min notional), and a note summarizing account-survival simulation results from B-035 backtests.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "mode": {
   "type": "string",
   "description": "optional: preserve (default) | target"
  },
  "entry": {
   "type": "number",
   "description": "number"
  },
  "equity": {
   "type": "number",
   "description": "number (USD)"
  },
  "symbol": {
   "type": "string",
   "description": "string, e.g. ETHUSDT"
  },
  "stop_loss": {
   "type": "number",
   "description": "number"
  },
  "take_profit": {
   "type": "number",
   "description": "number (optional)"
  },
  "risk_per_trade": {
   "type": "number",
   "description": "number (optional, fraction, default 0.02)"
  },
  "exchange_max_leverage": {
   "type": "number",
   "description": "number (optional)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "example": {
  "mode": "preserve",
  "note": "Leverage is derived from stop and risk, not chosen. B-035 (ByBit project, 410 daily windows): 20x wiped the account in 179 days, 50x in 50, 100x in 25 — in a rising market. mode=target removes the survival cap but never the liquidation-beyond-stop invariant.",
  "limits": {
   "risk per trade": 0.67,
   "exchange max leverage": 100,
   "costs vs expected move": "not binding",
   "liquidation beyond stop x1.5": 20,
   "measured survival cap (B-035)": 5
  },
  "symbol": "ETHUSDT",
  "binding": "risk per trade",
  "verdict": "MAX 0.67x",
  "leverage": 0.67,
  "tradable": true,
  "checked_at": "2026-10-23T23:30:17Z",
  "instrument": {
   "venue": "okx",
   "instrument": "ETH-USDT-SWAP",
   "max_leverage": 100,
   "min_notional": 2.3756
  },
  "notional_usd": 633.33,
  "method_version": "1.0.0",
  "instrument_error": null,
  "stop_distance_pct": 3,
  "max_loss_at_stop_usd": 19,
  "liquidation_distance_pct": "none at <=1x",
  "liquidation_beyond_stop_x": null,
  "round_trip_cost_pct_of_equity": 0.1067
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lucky-cin-leverage-calculator-33b3d2bc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from lucky-x402.onrender.com](https://www.zero.xyz/host/lucky-x402.onrender.com/llms.txt)