How would you use a crypto signals API?

One thing I added to LiMiT Quant is an API layer, because a signal dashboard should not force every user to stay inside the interface.

The API is designed for practical use cases like:

- pulling BTC, ETH and SOL signal tickets into a private dashboard

- sending alerts to Slack, Telegram or Discord

- connecting signals to internal logs or audit systems

- building a simple bot workflow around structured tickets

- testing signal history against your own market rules

- separating public locked tickets from full key-based access

The current structure supports public locked tickets, full ticket access with a key, Bearer / X-Api-Key authentication, OpenAPI JSON and Swagger documentation.

For builders, the useful part is not just “a signal exists”. It is having a stable structure around direction, pair, access state, confidence, risk levels and ticket fields.

Curious how other technical users would approach this:

Would you use a crypto signals API mainly for alerts, dashboards, bots, or backtesting?