---
name: api.jega.digital
description: api.jega.digital exposes two endpoints: one that returns MCP-style schema metadata describing Jega's API tools, and one that returns a real-time directional trading signal for BTC derived from the spread between spot price and Kalshi-implied price. The host does not support historical queries, multi-asset coverage, or trade execution.
host: api.jega.digital
---

# api.jega.digital

Jega Digital is a small API host offering a schema-discovery endpoint and a single live drift-signal endpoint for BTC. The drift signal compares spot price against Kalshi prediction-market-implied price to produce a LONG/SHORT directional indicator. It is aimed at agents that need a lightweight, pre-computed signal rather than raw market data they must process themselves.

## When to use this host

Use this host when an agent needs a single, pre-computed BTC directional signal based on the spread between spot and Kalshi-implied prices, or when it needs to inspect Jega's MCP tool schema for integration purposes. Do not use this host for historical drift data, multi-asset signals, order execution, raw OHLCV data, or any asset other than BTC. For broader market data needs, prefer dedicated market-data providers. For prediction-market data beyond the implied price already embedded in the drift signal, query Kalshi directly.

## Capabilities

### Schema Discovery

Returns the MCP tool schema for Jega's API, allowing an agent to inspect available tool names, descriptions, and expected input properties before invoking any Jega endpoint.

- **`fetch-mcp-schema`** — Returns the MCP-style tool schema for Jega's API integrations, including tool name, description, and input schema definition.

### Drift Signal

Provides a real-time snapshot of BTC spot price, Kalshi-implied price, computed drift value, and a LONG/SHORT directional signal with verification status.

- **`fetch-drift-signal`** — Returns the current spot price, Kalshi-implied price, drift value, directional signal, and verification status for a market (currently BTC).

## Workflows

### Schema-Validated Signal Fetch

*Use when an agent needs to verify the expected output structure of the drift signal before consuming it, such as during initial integration or after a suspected schema change.*

1. **`fetch-mcp-schema`** — Retrieve the MCP tool schema to confirm the field names and types the drift signal endpoint will return.
2. **`fetch-drift-signal`** — Fetch the live drift signal and validate its output against the schema retrieved in the previous step.

## Skill reference

### `fetch-mcp-schema`

**Jega MCP Schema** — Returns the MCP-style tool schema for Jega's API integrations, including tool name, description, and input schema definition.

*Use when:* Use when an agent needs to discover the MCP tool schema published by Jega Digital, such as to inspect available tool names, descriptions, and expected input properties before invoking a Jega API tool.

*Not for:* Do not use to execute API operations or retrieve live data; this endpoint only returns schema metadata describing a tool, not results from running it.

**Returns:** Returns a single MCP tool schema object with name, description, and an inputSchema object describing the tool's expected inputs.

**Example:** `GET https://api.jega.digital/api/schema/mcp`

---

### `fetch-drift-signal`

**Drift Signal** — Returns the current spot price, Kalshi-implied price, drift value, directional signal, and verification status for a market (currently BTC).

*Use when:* Use when an agent needs a real-time directional trading signal derived from the spread between a spot price and a Kalshi-implied price, including the raw drift value and a LONG/SHORT signal.

*Not for:* Do not use for historical drift data or multi-asset batch queries; this endpoint returns a single current snapshot only.

**Returns:** Returns a JSON object with spot_price, kalshi_implied_price, drift spread, a LONG/SHORT signal, a Unix timestamp, and a verified boolean flag.

**Example:** `GET https://api.jega.digital/api/drift`

---