Contract
input_schema.json
{
"type": "object",
"required": [
"indicator",
"symbol"
],
"properties": {
"to": {
"type": "string",
"minLength": 1,
"description": "End of time range. Defaults to now when from is set. Accepts Unix seconds (1706745600) or date string (2024-02-01). Example: 2024-02-01."
},
"from": {
"type": "string",
"minLength": 1,
"description": "Start of time range. When set, returns time-series instead of latest value. Accepts Unix seconds (1704067200) or date string (2024-01-01). Example: 2024-01-01."
},
"symbol": {
"type": "string",
"minLength": 1,
"description": "Trading pair as BTC/USDT or bare symbol like BTC. Example: BTC."
},
"options": {
"type": "string",
"minLength": 1,
"description": "Indicator-specific options as comma-separated key:value pairs. Available options by indicator: period — lookback period for rsi (default 14), sma (default 20), ema (default 20), bbands (default 20), adx (default 14), atr (default 14), cci (default 20), dmi (default 14), stoch (default 14), supertrend (default 10). stddev — standard deviation for bbands (default 2). multiplier — multiplier for supertrend (default 3). fast_period — MACD fast EMA (default 12). slow_period — MACD slow EMA (default 26). signal_period — MACD signal smoothing (default 9). Examples: period:7, period:200, fast_period:8,slow_period:21,signal_period:5, period:10,stddev:1.5. Example: period:7."
},
"exchange": {
"enum": [
"binance",
"bybit",
"coinbase",
"kraken"
],
"type": "string",
"default": "binance",
"description": "Exchange for price data. Can be binance, bybit, coinbase, or kraken. Example: binance. Defaults to \"binance\"."
},
"interval": {
"enum": [
"1m",
"5m",
"15m",
"30m",
"1h",
"2h",
"4h",
"12h",
"1d",
"1w"
],
"type": "string",
"default": "1d",
"description": "Candlestick interval — bucket size for each point in the indicator series: 1m, 5m, 15m, 30m, 1h, 2h, 4h, 12h, 1d, or 1w. This endpoint uses interval only; it does NOT accept time_range. Use from/to to bound the series. Example: 1d. Defaults to \"1d\"."
},
"indicator": {
"enum": [
"rsi",
"macd",
"ema",
"sma",
"bbands",
"stoch",
"adx",
"atr",
"cci",
"obv",
"vwap",
"dmi",
"ichimoku",
"supertrend"
],
"type": "string",
"description": "Technical indicator name. Can be rsi, macd, ema, sma, bbands, stoch, adx, atr, cci, obv, vwap, dmi, ichimoku, or supertrend. Example: rsi."
}
},
"additionalProperties": false
}output_schema.json
{
"type": "object",
"properties": {
"data": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Echoes the requested indicator, e.g. 'rsi'."
},
"value": {
"type": "number",
"description": "The indicator's primary value. On a single-number indicator (observed: rsi) this is the whole result; on a multi-component indicator (observed: macd) this mirrors the same number as `values.macd_value`."
},
"symbol": {
"type": "string",
"description": "Echoes the requested trading pair."
},
"values": {
"type": "object",
"properties": {
"macd_hist": {
"type": "number",
"description": "The MACD histogram (macd_value minus macd_signal)."
},
"macd_value": {
"type": "number",
"description": "The MACD line."
},
"macd_signal": {
"type": "number",
"description": "The MACD signal line."
}
},
"description": "Named sub-values, present only for indicators that compute more than one number. Observed only on the MACD fixture (macd_value/macd_signal/macd_hist) and absent entirely from the single-value RSI fixture -- whether other multi-component indicators (bbands, stoch, dmi, ichimoku) use this same field or different key names is unconfirmed from two fixtures.",
"additionalProperties": true
},
"interval": {
"type": "string",
"description": "Echoes the requested candle interval."
},
"updated_at": {
"type": "integer",
"description": "Unix seconds marking when this value was last computed."
}
},
"additionalProperties": false
},
"description": "One entry: the latest computed value for the requested indicator."
},
"meta": {
"type": "object",
"properties": {
"limit": {
"type": "integer",
"description": "Echoes the requested (or defaulted) limit."
},
"total": {
"type": "integer",
"description": "Total values available for the query."
},
"cached": {
"type": "boolean",
"description": "Whether this response was served from the provider's cache."
},
"offset": {
"type": "integer",
"description": "Echoes the requested (or defaulted) offset."
}
},
"additionalProperties": false
}
},
"description": "The indicator response, as returned at routing.responseResultPath ($.output).",
"additionalProperties": false
}Pricing
Every real charge, itemised. A model that quietly omits one is a slow financial leak, so nothing here is rolled up, and a charge that only applies to some inputs says so rather than being added in.
Prices in this catalog are the provider's own list price, not your bill: Omnial MCP charges provider cost plus a platform markup on top, so what you are charged is higher than the figure shown. For the exact amount a specific call will cost, run omnial_execute with dry_run: true; that number includes the markup and is what we hold while the call runs. It is a quote, not a cap on the charge.
| Charge | Rate |
|---|---|
Per call Flat, regardless of what comes back | $0.01638 |
- Cost basis
- Not recorded
This tool's catalog entry does not record how its final bill is determined, so we will not tell you whether its cost is fixed before the call or reported by the provider afterwards. Either way what is held is a quote rather than a cap: you are charged what the call actually costs, bounded at 2x the quote.
- Updated
- Sep 15, 2026