---
title: "Overview"
description: "What Mentio is, how a mention travels from a platform to your inbox, and the five ways to build on it."
canonical: https://docs.mentio.dev/
markdown: https://docs.mentio.dev/index.mdx
---

# Overview

What Mentio is, how a mention travels from a platform to your inbox, and the five ways to build on it.

Mentio is social listening for developer platforms, built API-first. You tell it which words to watch (your product, your competitors, your space); it fetches every new post that contains them from Bluesky, Hacker News, Reddit, X, GitHub, Stack Overflow, DEV, YouTube, LinkedIn and news, scores each one for relevance, sentiment and intent, and gives you a structured feed you can query, triage and get pushed wherever you work.

## How a mention gets to you

1. **Ingest.** Each platform is polled on its own cadence; Bluesky is a live firehose. A post is stored once, however many workspaces track the same term.
2. **Match.** The post is matched against every keyword that wants it, per workspace and per platform.
3. **Classify.** A model reads your company profile and scores the match: relevance from 0 to 100, sentiment, intents such as `buy_intent` or `complaint`, and a one-line note.
4. **Deliver.** Relevant mentions reach your alert rules as they happen, or once a day as a digest, through Slack, Telegram, email or a signed webhook.

Every matched mention counts toward usage, relevant or not; only relevant ones are delivered. [How it works](/how-it-works) has the cadences and the lifecycle.

## Six ways in

<Cards>
  <Card title="REST API" description="Every capability under one set of conventions. The dashboard is one client of it." href="/api" />

  <Card title="SDKs" description="TypeScript and Python, one typed call per endpoint, generated from the OpenAPI document." href="/sdks" />

  <Card title="CLI" description="Every endpoint as a mentio command, plus a live feed for scripts." href="/cli" />

  <Card title="MCP server" description="The same operations as tools for Claude Code, Cursor, VS Code and any MCP client." href="/mcp" />

  <Card title="Webhooks" description="Signed JSON for every mention or digest an alert rule produces." href="/webhooks" />

  <Card title="OpenClaw" description="A ClawHub skill so OpenClaw works the feed from natural language." href="/integrations/openclaw" />
</Cards>

All of them are skins over the same operations and the same OpenAPI document. A field means the same thing everywhere, and the reference, the SDK, the CLI and the MCP tool list are regenerated together, so they cannot disagree.

## The model

| Resource            | What it is                                                                                                                                                                                                | Reference                                             |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- |
| Keywords            | The terms you track: `brand`, `competitor` or `topic`, optionally limited to some platforms, with matching rules (required and excluded terms, excluded authors, case) and a classifier hint of their own | [/v1/keywords](/api/keywords/list-keywords)           |
| Filters             | The noise rules of the whole workspace: excluded terms and authors, GitHub repositories, subreddits. Applied before a mention is stored, so a rejected post is never billed                               | [/v1/filters](/api/filters/get-filters)               |
| Mentions            | One post matched to one keyword, with its classification (and your verdict on it), and your triage: `open`, `ignored` or `done`, an assignee, a snooze, a note                                            | [/v1/mentions](/api/mentions/search-mentions)         |
| People              | The authors behind the mentions, with reach and public profile, plus your tags, notes and mutes                                                                                                           | [/v1/people](/api/people/list-people)                 |
| Segments            | Saved filters over people, evaluated live                                                                                                                                                                 | [/v1/segments](/api/segments/list-segments)           |
| Alerts and channels | Rules (what to watch; instant, daily or weekly) times channels (Slack, Telegram, email, webhook)                                                                                                          | [/v1/alerts](/api/alerts/list-alerts)                 |
| Analytics           | Four reports over one window: summary, series, breakdown, share of voice                                                                                                                                  | [/v1/analytics](/api/analytics/get-analytics-summary) |
| Company             | The profile the classifier reads (description, use cases, competitors, guidelines), the biggest lever on relevance                                                                                        | [/v1/company](/api/company/get-company)               |
| Members             | The team: who is in, with their role, and the invitations on their way. Reads take any credential; changes need a signed-in owner or admin                                                                | [/v1/members](/api/members/list-members)              |
| Usage               | The prepaid balance, the daily burn, the keywords it pays for and the matches that bill                                                                                                                   | [/v1/usage](/api/usage/get-usage)                     |
| API keys            | `read` or `write`, each bound to one workspace, with an optional expiry; `GET /v1/whoami` says which one is talking                                                                                       | [/v1/api-keys](/api/api-keys/list-api-keys)           |

## Start here

* [Quickstart](/quickstart): a keyword, the company profile, a search and a triage in five calls.
* [Authentication](/authentication) and [Conventions](/conventions): keys, scopes, envelopes, ids, timestamps, errors.
* [Alerts](/alerts) to get mentions pushed; [Billing](/billing) for how the prepaid balance works.