# Hearl

> Hearl collects what people say about your product on X, Reddit and Hacker News, filters out the noise with AI, and gives each post an owner, a deadline and a clear outcome.

Hearl is a shared inbox for public conversations about a product. It collects posts and replies from X, Reddit, Hacker News, Xiaohongshu, Weibo, Zhihu, Bilibili, YouTube, App Store and Google Play reviews, and GitHub issues, uses AI to judge whether each post is about the product, whether it needs a reply and how urgent it is (each judgment comes with a probability), and lets a team assign one owner, add collaborators, set due dates and record outcomes. It reads each thread to track whether the team replied and whether the user followed up, and notifies the team by email or webhook (Slack, Feishu, WeCom, DingTalk, Discord or any JSON endpoint). Hearl does not post replies itself.


Last verified: 2026-11-14

## Key facts

- Platforms: X, Reddit, Hacker News, Xiaohongshu, Weibo, Zhihu, Bilibili, YouTube, App Store and Google Play reviews, and GitHub issues ([channels](https://hearl.org/channels))
- Filtering: AI judgments with probabilities; posts it isn't sure about go to a review list instead of being dropped
- Collection: daily on Free, hourly on paid plans, every 15 minutes for up to 5 products on Enterprise
- Pricing: Free $0; Individual $19/month and Enterprise $299/month with a monthly allowance and usage-based overage; Team $15/seat/month (minimum 3 seats); 14-day Team trial
- Notifications: email digest and signed webhooks (HMAC-SHA256), checked every 15 minutes
- Languages: English, 简体中文, 日本語, 한국어, Español, Français, Deutsch, Português, Русский, العربية

## Product

- [Home](https://hearl.org/): what Hearl does and who it is for ([Markdown](https://hearl.org/index.md))
- [Pricing](https://hearl.org/pricing): plans and limits ([Markdown](https://hearl.org/pricing.md))
- [Docs](https://hearl.org/docs): workspace setup, products and sources, AI filtering, the inbox, statuses, notifications and billing, in 10 languages ([llms.txt for the docs](https://hearl.org/docs/llms.txt))

## Channels

- [X](https://hearl.org/channels/x): Mentions of your accounts, replies under your posts, and follow-ups after you answer
- [Reddit](https://hearl.org/channels/reddit): New posts in your subreddits and threads anywhere that name your product
- [Hacker News](https://hearl.org/channels/hacker-news): Stories and Show HN posts that name your product, with their comments
- [YouTube](https://hearl.org/channels/youtube): New videos that name your product and the comments under them
- [Xiaohongshu](https://hearl.org/channels/xiaohongshu): Notes that name your product and the comments under them
- [Weibo](https://hearl.org/channels/weibo): Weibo posts that name your product and their comments
- [Zhihu](https://hearl.org/channels/zhihu): Questions, answers and articles that name your product
- [Bilibili](https://hearl.org/channels/bilibili): Videos that name your product and the comments under them
- [App Store](https://hearl.org/channels/app-store): New App Store reviews of your app, with the rating
- [Google Play](https://hearl.org/channels/google-play): New Google Play reviews of your app, with your developer replies
- [GitHub](https://hearl.org/channels/github): Open issues in your repository and their comments

## Before you act for a user

Ask what is still unclear: which product, which view or time range, whether they want a summary, a list or changes applied, and who should own new work. Read first; change owners, states or due dates only after the user agrees. Hearl never posts publicly, so draft replies go into internal notes.

## Machine endpoints (no key needed)

- [Collection status](https://hearl.org/api/status): per-channel success rate over 30 days and the last run, as JSON ([page](https://hearl.org/status))
- [OpenAPI](https://hearl.org/api/v1/openapi.json), [MCP server card](https://hearl.org/.well-known/mcp/server-card.json), [agent skill](https://hearl.org/.well-known/agent-skills/hearl/SKILL.md), [auth.md](https://hearl.org/auth.md)

## When something fails

401 means the key is missing or revoked (create a new one under Agents & API); 403 means a read-only key was used for a write; 400 names the field that is wrong. For 429 or 5xx, retry once, then check https://hearl.org/status and tell the user. Support: the email on the home page footer.

## For AI agents

Agents can read and work a team's Hearl inbox: summary, inbox views, full threads with Hearl's AI judgments, assigning owners, states, due dates and internal notes. Hearl never posts publicly; agents leave draft replies as notes.

- [Hearl for AI agents](https://hearl.org/agents): MCP server, CLI, agent skill and REST API, with workflows ([Markdown](https://hearl.org/agents.md))
- MCP server: https://hearl.org/mcp (Streamable HTTP, Bearer key; [server card](https://hearl.org/.well-known/mcp/server-card.json))
- CLI: `npx hearl` (login, summary, inbox, show, assign, done, note; `mcp install` configures Claude Code, Cursor and Claude Desktop)
- [Agent skill](https://hearl.org/.well-known/agent-skills/hearl/SKILL.md): when to use Hearl, how to connect, triage and reply-drafting workflows
- [OpenAPI](https://hearl.org/api/v1/openapi.json): the /api/v1 endpoints
- [auth.md](https://hearl.org/auth.md): how an agent gets a workspace API key (read-only or read-write)
- [API catalog](https://hearl.org/.well-known/api-catalog) and [AI catalog](https://hearl.org/.well-known/ai-catalog.json)

## Use cases

- [Track Reddit posts about your product](https://hearl.org/use-cases/reddit-monitoring): Hearl reads your subreddits and site-wide Reddit search, uses AI to drop unrelated posts, reads the full comment tree to see whether your team replied, and puts a thread back in the inbox when the original poster follows up. ([Markdown](https://hearl.org/use-cases/reddit-monitoring.md))
- [Never lose an @mention on X](https://hearl.org/use-cases/x-mentions): Hearl collects posts that mention your X accounts and replies under your own posts, removes ads, fetches the post each reply answers, flags the ones worth answering and gives each one an owner. ([Markdown](https://hearl.org/use-cases/x-mentions.md))
- [Follow Hacker News threads about your product](https://hearl.org/use-cases/hacker-news): Hearl searches new Hacker News posts for your keywords, reads the whole comment tree, marks your team's replies, nudges you when someone follows up, and handles HN in the same inbox as X and Reddit. ([Markdown](https://hearl.org/use-cases/hacker-news.md))
- [Support customers in communities you don't own](https://hearl.org/use-cases/community-support): Hearl gives public questions on X, Reddit and Hacker News an owner, a due date and a recorded outcome, keeps the conversation on the original platform, and reopens it when the user writes back. ([Markdown](https://hearl.org/use-cases/community-support.md))

## Other languages

- [简体中文](https://hearl.org/zh)
- [日本語](https://hearl.org/ja)
- [한국어](https://hearl.org/ko)
- [Español](https://hearl.org/es)
- [Français](https://hearl.org/fr)
- [Deutsch](https://hearl.org/de)
- [Português](https://hearl.org/pt)
- [Русский](https://hearl.org/ru)
- [العربية](https://hearl.org/ar)

## Optional

- [Full text for LLMs](https://hearl.org/llms-full.txt)
- [Privacy](https://hearl.org/privacy) and [Terms](https://hearl.org/terms)