Skip to documentation
API docs/OverviewChapters +
Documentation/Getting started
v1

Getting started

Eclipse API

Proprietary trading intelligence, ready for your application.

Indicator intelligence for your next build.

Programmatic access to the intelligence behind Eclipse — 7 proprietary indicators computed server-side on closed candles across the entire tracked market. Not just alerts: the live directional state of every indicator on every asset, every state change as it happens, and where different indicators agree. Built to be read by machines managing money.

$129/month or $1199/year. Fully self-serve — an agent can buy a key with two HTTP calls and a payment, with no approval step, no sales call and no human in the loop. 10,000 requests/day.

251
tracked assets
176 crypto · 75 equities & metals
3
timeframes
1h · 4h · 1d
7
proprietary indicators
built and run in-house
5,271
live readings
refreshed every hour

Those numbers are generated from the same constants our compute jobs run on, so they are always exactly what the API serves. Verify them yourself at /api/v1/catalog before you pay us anything.

Choose the feed for your strategy

API coverage, candle timeframes, compute cadence and example uses
FeedConfigured coverageTimeframes & cadenceExample uses
Universe
State, transitions & confluence
251 assets. The state carries 7 indicators, including PerpKit’s trend reading; changes are logged for 6.1h / 4h / 1d candles.
Hourly at :03 UTC. Each timeframe updates when due.
Regime filtering, candidate ranking and signal confirmation.
Alerts
Strategy events
6 assets: BTC, ETH, BNB, SOL, NVDA, TSLA. 7 indicators, including PerpKit.4h / 1d candles.
Computed after the relevant candle closes; events appear when a strategy triggers.
Entry/exit event inputs for swing strategies and paper-trading workflows.

These are closed-candle indicator inputs. Your application supplies execution, position sizing and risk controls. Choose a feed whose candle timeframe matches your strategy; polling more often does not produce faster indicator calculations.

Coverage is generated from the catalog, whose coverage.assets table lists every asset with the timeframes each tier computes for it. It describes configured coverage, not the health or freshness of every reading. Check available history and evaluation guidance before planning a study.

01

Read the market

Fetch the current board, track changes, and find indicator agreement.

02

Connect your agent

Discover Eclipse tools through the Model Context Protocol.

03

Understand the data

Explore signal fields, coverage tiers, and response examples.

04

Get API access

Review pricing, authentication, and request quotas.

Signals are informational outputs of technical indicators, not investment advice or a solicitation to trade. Past signals do not guarantee future performance. Use of this API is governed by the Eclipse terms of use.

Standard API access is self-serve under the published Eclipse terms of use and the pricing and quota on /api/docs/access. No separately negotiated agreement is required for standard access. There is no formal uptime SLA. Redistribution, resale, or custom commercial terms require a separate written agreement through /api/v1/access-request.

Support & access recovery

Search API documentation

↑ ↓ to navigate · Enter to openEsc to close
Eclipse API — Trading Signals for Autonomous Agents