---
title: "Signal ledger (fired flags with outcomes)"
method: GET
path: "/api/public/signals"
tags: ["Free", "free"]
---

# Signal ledger (fired flags with outcomes)

`GET /api/public/signals`

## Request

- Base URL: `https://coinlobster.com`
- URL: `https://coinlobster.com/api/public/signals`
- Auth: none required

Fired signal-ledger rows over plain HTTP, logged live and never backfilled. Free, matching what the browser and the MCP flag_outcomes tool already give away.

## Query parameters

- `type` string
- `coin` string
- `hours` integer
- `limit` integer

## Response `200`

Success

- object
  - `success` true, required
  - `data` FlagRow[], required
    - `type` string
    - `coin` string
    - `firedAt` integer
    - `price` number: Price at fire time.
    - `outcomes` object: Absent or partial until enough time has passed. Never inferred.
      - `h24` object
        - `ok` boolean: false means the outcome could not be scored cleanly. Do not read `ret`.
        - `ret` number: Fractional return, e.g. 0.012 = +1.2%.
  - `meta` Meta: Present on every /api/ai/v1 response.
    - `timestamp` string, date-time: When this response was assembled, not when the data was measured.
    - `credits_used` integer: Credits this call spent. Absent on free surfaces and on keyless calls.
    - `credits_remaining` integer: Account balance after this call.
    - `deprecation` string: Present when the request used a deprecated form, e.g. the key in the query string.

---

[API](https://skmtc.dev/coinlobster/apis/coinlobster-crypto-data-api.md) · [All operations](https://skmtc.dev/coinlobster/apis/coinlobster-crypto-data-api/llms.txt) · [OpenAPI document](https://skmtc.dev/coinlobster/apis/coinlobster-crypto-data-api/revisions/a62c3a47523a?raw)