TGSS API
Programmatic access to the engine behind the terminal.
API keys
A key is shown once, when it is created. After that only its prefix, because it is stored hashed and cannot be recovered.
| Key | Label | Tier | Used | Limit | Status | Last used |
|---|
Usage
Calls over the last 30 days, and the most recent requests.
Recent calls
| When | Instrument | Timeframe | Status | Time |
|---|
Playground
Runs against the live endpoint with a key you paste. Real calls, so they count against your allowance.
Choose an instrument and send a request.
Docs
One endpoint, one header.
Request
curl -X POST https://api.ethoryx.io/v1/tgss/signal \
-H "X-API-Key: tgss_your_key_here" \
-H "Content-Type: application/json" \
-d '{"symbol":"BTC/USD","interval":"1D"}'
Authorization: Bearer tgss_... works too.
What comes back
The engine's output: the next-bar prediction, direction and confidence, the thresholds the rule is judged against, a plain-language takeaway, and the walk-forward accuracy record with every scored bar.
Raw price history is not included. TGSS sells its own
analysis, not a market data feed. Add "include_series": true for the
most recent 60 bars as plotting context.
Limits
Calls count against a monthly allowance that resets on the 1st. A request that
fails because you asked for an unknown instrument still counts, because it still
cost us the work. Over the allowance the endpoint returns 429 with the
reset date.
Without a key the endpoint stays open at 200 requests per hour, which is enough to try it and not enough to build on.