> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rumorly.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Rumorly reads every "how did you hear about us?" answer, names the source behind it and puts your revenue next to it.

Most B2B customers find you through things analytics can't see: a founder's LinkedIn post, a podcast episode, a friend, an answer from ChatGPT. When they sign up, those visits show up as "Direct". The customer still knows where they heard about you, and many of them say so when you ask.

Rumorly takes those free-text answers and:

1. **Classifies** each one into a channel (AI assistant, founder social, podcast…) and, when the answer names one, a source (ChatGPT, Jake Morrison, Lenny's Podcast).
2. **Writes it back** to Attio, so your CRM has the answer as structured data.
3. **Joins it to Stripe**, so every channel and source has monthly recurring revenue next to it.
4. **Reports** what customers said next to what first-touch attribution credited, so you can see which word of mouth actually pays.

> **[Quickstart](/quickstart)**
>
> Sign up, paste a few answers and see them classified in five minutes.

> **[Concepts](/concepts)**
>
> Channels, named sources, the review queue and how revenue is matched.

> **[Collect answers](/collect/snippet)**
>
> The JS snippet, the REST API, CSV import, Tally and other forms.

> **[API reference](/api-reference/overview)**
>
> Every endpoint, with a playground you can call with your own key.

## How answers get in

Everything goes through one endpoint, [`POST /v1/responses`](/api-reference/responses/record-an-answer). The snippet, form webhooks, CSV import and the Attio sync are ways of calling it without writing code, so a response looks the same however it arrived.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.