Satellite storage nowcast, scored against EIA prints, walk-forwardTwenty five signals across energy, every one with its method publicEvery value knows when it became knowable
SYENE

API docs

The public API mirrors every visibility=public signal. Create a key in Settings; the plaintext is shown once and stored hashed. Free keys read data delayed one week; Pro keys read current values. Quotas: 1k, 10k, and 100k requests per month by tier.

Authentication

Send the key in the X-API-Key header. Missing or revoked keys return 401 with the next action; a spent monthly quota returns 429.

curl -H "X-API-Key: sk_..." \
  https://api.syene.ai/v1/public/signals

curl -H "X-API-Key: sk_..." \
  "https://api.syene.ai/v1/public/signals/energy.x.storage_divergence/series"

Python

The typed client is on PyPI. Systematic customers live in dataframes, so the series hop to polars is one call.

pip install syene-client

from syene_client import SyeneClient

client = SyeneClient(api_key="sk_...")
for signal in client.signals():
    print(signal.id, signal.units)

df = client.frame("energy.x.storage_divergence")  # polars

CSV export

Every signal on your plan exports as CSV with event and knowledge timestamps, so your own backtests can honor point-in-time the way ours do.

# Signed-in customers, any signal on the plan:
curl -H "Authorization: Bearer <session>" \
  "https://api.syene.ai/v1/signals/energy.refining.crack_321/export.csv" -O

Endpoints

  • GET /v1/public/signals
  • GET /v1/public/signals/{id}/series
  • GET /v1/signals/{id}/export.csv
  • GET /v1/methodology
  • GET /v1/status

The full OpenAPI schema ships with the terminal; ask and alert endpoints are session-scoped and documented in-product.

The API serves research data. Nothing in it is investment advice.