> For the complete documentation index, see [llms.txt](https://ottodata.gitbook.io/ottodata-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ottodata.gitbook.io/ottodata-docs/api-reference/social-reddit-intel.md).

# Social (Reddit intel)

## Social (Reddit intel)

Reddit-derived alpha signals, served as a live read-through from the upstream signal engine. If the upstream is unavailable these endpoints return `503`.

### `GET /v1/social/signals`

Ticker alpha signals extracted from Reddit chatter — each scored on novelty, mention velocity and cross-subreddit spread.

| Parameter             | Type   | Default | Notes                                                                |
| --------------------- | ------ | ------- | -------------------------------------------------------------------- |
| `tickers`             | string | —       | comma-separated, e.g. `NVDA,TSLA`                                    |
| `signal_type`         | string | —       | `ticker_alpha`, `crowded_trade`, `event_mispricing`, `squeeze_watch` |
| `min_alpha`           | float  | 0.0     | 0–1                                                                  |
| `min_narrative_count` | int    | 0       | require multiple independent narratives                              |
| `hood_only`           | bool   | false   | restrict to the 32 Hood tokenized tickers                            |
| `limit`               | int    | 50      | max 200                                                              |

```bash
curl "https://api.ottodata.app/v1/social/signals?hood_only=true&min_alpha=0.5"
```

### `GET /v1/social/regime`

The current market regime inferred from aggregate Reddit behavior (e.g. `mag7_only_rally`, `risk_on_call_chase`) with a confidence score and flags to watch.

### `GET /v1/social/hood-attention`

The join that matters for Hood: for each tokenized ticker, the strongest recent Reddit signal **combined with its live basis** — where social attention and on-chain premium/discount coincide.

| Parameter   | Type  | Default | Notes                    |
| ----------- | ----- | ------- | ------------------------ |
| `min_alpha` | float | 0.0     | 0–1                      |
| `hours`     | int   | 48      | signal lookback, max 168 |

```json
{
  "attention": [
    {
      "ticker": "MU",
      "alpha_score": 0.734,
      "signal_type": "event_mispricing",
      "narrative_count": 3,
      "summary": "A far OTM MU call with Sept 18 expiry…",
      "fanout_size": 1,
      "basis_bps": -58.2,
      "overnight_bps": -317.9,
      "chainlink_px": 875.53
    }
  ]
}
```

{% hint style="info" %}
**Fan-out dedup**: one viral post mentioning 20 tickers produces 20 near-identical upstream rows. Otto collapses those into a single group (`fanout_size` tells you how many tickers the source post touched) so the feed isn't dominated by one post.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ottodata.gitbook.io/ottodata-docs/api-reference/social-reddit-intel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.