---
title: mobius_trend (Mobius Trend)
description: "mobius_trend API reference: parameters, response fields and example requests."
---

# `mobius_trend` — Mobius Trend

> Category: **Trend** · Composite · 🧪 Möbius Lab

::: tip Reading the response
Use `POST /api/indicators?explain=true` to include interpretation notes at `indicators[responseKey].explain`. Read numeric results from `columns` and `data` in the same object.
:::

This is a trend indicator.

## Parameters

| Parameter | Type | Default |
|------|------|--------|
| `left_bars` | int | `15` |
| `right_bars` | int | `14` |
| `offset` | float | `1.75` |
| `atr_period` | int | `200` |

## Output columns

| Column |
|------|
| `trend` |
| `trend_value` |



## Native features

Set top-level `signals: true` and read `indicators[responseKey].signals`. By default features are evaluated on closed bars: `true` is a positive result, `false` a valid negative result, and `null` unknown. These are not trade instructions.

This indicator supports `include_forming: true`: treat the current final OHLCV sample as complete under the same native rules, returning one set of values, features and objects. The signal table appends `bar_status`: `closed` for closed bars, `forming` for a trial with `confirmed_at_ms=null`. A trial may disappear on later updates or at close. For BYO, still set `last_bar_closed: false`. Close requirements below describe the default mode; trials only admit the final sample without shortening structural windows or model confirmation requirements. See [forming trials](/signals#forming).

History lengths are minimum evaluation requirements, not convergence guarantees. Comparisons use unrounded values and the exact boundaries below. Do not turn `null` into `false` on gaps, invalid dependencies or forming bars in the default mode.

| Feature column | Kind | Rule | Meaning | History / validity |
| --- | --- | --- | --- | --- |
| `mobius_trend.reversal_up` | `event` | Previous trend=-1; current trend=1. Initialization is not a reversal. | Reuses the ATR-offset pivot state machine; a close crossing the relevant confirmed pivot changes direction. No pivot-time backfill. | atr_period + left_bars + right_bars + 2 contiguous bars with valid direction and active reference on both bars. |
| `mobius_trend.reversal_down` | `event` | Previous trend=1; current trend=-1. Initialization is not a reversal. | Reuses the ATR-offset pivot state machine; a close crossing the relevant confirmed pivot changes direction. No pivot-time backfill. | atr_period + left_bars + right_bars + 2 contiguous bars with valid direction and active reference on both bars. |

See [feature requests](/compute#native-features) for the format and examples. `/api/chart` also accepts `signals: true`, marking confirmed events by default. With `include_forming`, trial events also produce markers tagged `bar_status=forming`; states are not drawn on every bar. See [feature charts](/compute#feature-chart).

## Example call

```bash
curl -X POST -H "Authorization: Bearer mq_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "exchange": "binance",
    "market":   "perp",
    "symbol":   "BTCUSDT",
    "interval": "5m",
    "limit":    100,
    "signals":  true,
    "calc":     [{"name": "mobius_trend", "params": {"left_bars": 15, "right_bars": 14, "offset": 1.75, "atr_period": 200}}]
  }' \
  https://api.mobiusquant.ai/api/indicators
```

## Full interpretation guide

Field meanings, interpretation rules and usage notes are
documented in Chinese at:

[mobius_trend (中文详情)](https://docs.mobiusquant.ai/zh/indicators/mobius_trend)

## Related indicators

[alligator](./alligator) · [alma](./alma) · [ema](./ema) · [hma](./hma) · [hmm_regime](./hmm_regime) · [lsma](./lsma) · [mcginley_dynamic](./mcginley_dynamic) · [parabolic_sar](./parabolic_sar)
