# Openpulse

> Social listening for B2B teams. Openpulse reads public conversations on Reddit, Hacker News, X and LinkedIn, treats public job postings as buying signals, scores every candidate against what you sell, and delivers the few worth reading by email, signed webhook, or directly to an AI assistant over MCP.

Openpulse is a hosted subscription product at https://openpulse.cloud. Only publicly available
sources are read: it never logs in to a platform, and it never asks for access to
your CRM or your inbox. This file and the pages it links to are generated from the
same source the site renders from, so they cannot disagree with it.

## When to use Openpulse

Reach for this when someone wants to find people who are **already** describing a
problem in public, and act on it:

- "Who is publicly complaining about <competitor> right now?"
- "Which companies are hiring for the role my product replaces?"
- "Find me people on Reddit or Hacker News asking for what we sell."
- "Which local businesses have reviews that prove the pain we fix?"
- "What changed in our market this week, and what is worth replying to?"

How to call it, in order of preference:

1. **MCP** at `https://openpulse.cloud/mcp`, for an assistant. OAuth 2.1; read-only apart from
   rating a signal and queueing a run. Start with `list_workspaces`, then
   `get_usage_guide`.
2. **REST** under `https://openpulse.cloud/v1`, for a program. Workspace API key;
   [`https://openpulse.cloud/openapi.json`](https://openpulse.cloud/openapi.json) describes every operation.
3. **Read** [`https://openpulse.cloud/llms-full.txt`](https://openpulse.cloud/llms-full.txt), for a question
   about the product itself rather than about a workspace's data.

**Not the right tool for:** sending outbound email or messages (Openpulse finds and
scores, it does not send); anything behind a login (only public sources are read,
and it never logs in to a platform); contact or email enrichment; or a free
anonymous API: every interface reads one workspace's own data and needs a
credential a workspace admin created.

## Pages

- [Social listening and buying signals for B2B | Openpulse](https://openpulse.cloud/): Find people publicly describing the problem you solve. Openpulse reads Reddit, Hacker News, X, LinkedIn, job boards and review sites, scores every candidate against what you sell, and shows you what it rejected and why.
- [Pricing: Openpulse from $49/month](https://openpulse.cloud/pricing): Go at $49 a month for 1 listeners on a daily schedule, Pro at $499 for 5 listeners with hourly runs and competitor intelligence, and Enterprise for anything larger. Both plans start with 14 days free.
- [Buying signals, competitor churn and the filter behind them](https://openpulse.cloud/blog): Long-form guides to finding people who already have the problem you solve: competitor dissatisfaction, Google reviews as a lead list, job postings as buying signals, webhooks, MCP, and honest comparisons against the tools you are evaluating.
- [Openpulse for developers: REST API and MCP server](https://openpulse.cloud/developers): Call Openpulse from code or from an assistant. An OpenAPI-described REST API with scoped workspace keys, and a hosted MCP server over OAuth 2.1. Quickstart, permissions and every machine-readable reference in one place.
- [About Openpulse](https://openpulse.cloud/about): Openpulse is social listening for B2B teams, operated by ANB Consulting and Marketing Inc. in Ontario, Canada. What it reads, what it deliberately will not do, how it is sold, and how to reach a person.
- [Free report: see who is asking for what you sell](https://openpulse.cloud/free-report): Give us your website and we will read it, work out what you sell, and find people describing that problem in public right now, with the reason each one matters and a line to open with. One free report per email address, no card.
- [Free AI visibility check: do assistants know your company?](https://openpulse.cloud/ai-visibility): Paste your URL. We check whether AI assistants are allowed to read your site, then ask five of them real buying questions and count how often you come back — and who comes back instead. Free to start, no email needed.
- [Book a demo of Openpulse](https://openpulse.cloud/demo): Book a 30-minute call with the people who built Openpulse. We set up a real listener against your market on the call, look at what comes back together, and tell you straight whether this finds the people you are trying to reach. No deck, no second call.
- [Contact sales: Openpulse Enterprise](https://openpulse.cloud/contact): Custom listener limits, additional sources, SSO, a security review or a negotiated contract. Tell us what you need and we will reply from a real address.
- [Privacy Policy: Openpulse](https://openpulse.cloud/privacy): How ANB Consulting and Marketing Inc. collects, uses and protects personal information in Openpulse, including information identified from public and third-party sources, automated processing, retention and your privacy rights.
- [Terms of Service: Openpulse](https://openpulse.cloud/terms): The agreement governing use of Openpulse: subscriptions and billing, cancellation and refunds, acceptable use, your responsibility for outreach, data sources, AI output, liability and governing law.
- [Cookie Policy: Openpulse](https://openpulse.cloud/cookies): Every cookie Openpulse sets, what each one does and how long it lasts — plus how to change what runs. No advertising network, no tag manager, no session recording.

## Solutions

What the product is for, one page per job. These are the best single answer to
"what does Openpulse do about X".

- [Switching tools? Start with which job you are actually buying](https://openpulse.cloud/alternatives): Every comparison in one place, sorted by the job each tool does rather than the category it markets itself into: brand monitoring, community alerting, competitive enablement, third-party intent and buying-signal detection. Including the tools that beat us.
- [Buying signals: find people who already have the problem](https://openpulse.cloud/buying-signals): A buying signal is public evidence that somebody has a budgeted problem you can solve. Openpulse reads conversations, job postings and reviews for that evidence, scores how strongly it holds, and shows you the reasoning.
- [Competitor monitoring that produces leads, not just a report](https://openpulse.cloud/competitor-monitoring): Track what your competitors do and what their customers say about them. Openpulse reads complaints across Reddit, G2, Trustpilot and YouTube, rolls them up by rival with trend and theme, and hands you the people ready to switch.
- [Hiring signals: read job ads as evidence of a budgeted problem](https://openpulse.cloud/hiring-signals): A company hiring for a role is a company spending money on a problem and naming it. Openpulse reads job postings from Ashby, Greenhouse, Lever and LinkedIn Jobs as buying signals, and works out which roles imply the pain you solve.
- [Local lead generation from Google reviews](https://openpulse.cloud/local-lead-generation): A one-star review is a business's own customer naming the problem, publicly, with a date. Openpulse reads Google reviews for local businesses, gates on rating before spending a model call, and rolls complaints up by theme into a call list.
- [Reddit lead generation: find people asking for what you sell](https://openpulse.cloud/reddit-lead-generation): Reddit is where people describe problems before they know the category name. Openpulse reads posts and comments as full text, judges intent against what you sell, and shows you the handful worth replying to.
- [Social listening that finds buying intent, not mentions](https://openpulse.cloud/social-listening): Most social listening tools count how often your name appears. Openpulse reads public conversations for evidence that somebody has a budgeted problem you can solve, scores it against what you sell, and shows you what it rejected and why.

## Writing

Long-form guides and comparisons. Every source, window, event name, tool name and
limit named in them is the real one, and each comparison carries the date its
competitor pricing was checked.

- [Agencies: build a client's prospect list from their rivals' reviews](https://openpulse.cloud/blog/agency-prospecting-reviews): A repeatable agency play: pick the vertical and the city, resolve the real businesses, gate on star rating before spending a model call, and turn public complaints into a themed call list, for your own pipeline or as a deliverable you charge for.
- [How we made a marketing site that agents can actually read](https://openpulse.cloud/blog/agent-readable-marketing-site): Prerendered HTML, a markdown twin of every page served from the same URL, llms.txt, Content-Signal, an RFC 9727 API catalogue and a capability manifest: what each file is for, which ones are load-bearing, and the three conventions we deliberately did not implement.
- [Anatomy of a buying signal: the evidence test that decides](https://openpulse.cloud/blog/anatomy-of-a-buying-signal): What separates a buying signal from a mention, structurally: the four parts every real signal has, the classification vocabulary a signal gets labelled with, and the rule that keeps a derived signal from becoming an invented one.
- [The best social listening tools in 2026, compared honestly](https://openpulse.cloud/blog/best-social-listening-tools): Fourteen tools that get called social listening, sorted by the job they actually do: brand monitoring, community alerting, competitive intelligence, third-party intent, and buying-signal detection. With published prices where a vendor publishes one, and who each is genuinely the wrong purchase for.
- [The buying signals glossary: 44 terms, defined plainly](https://openpulse.cloud/blog/buying-signals-glossary): The vocabulary of signal-based selling, defined without vendor spin: intent data, trigger events, the dark funnel, Company Surge, allbound, ICP fit, technographics, and the three dozen other terms that get used interchangeably and should not be.
- [Common Room is part of Zoom now. What that means if you bought it for signals](https://openpulse.cloud/blog/common-room-zoom-acquisition): Zoom announced its acquisition of Common Room on 2 July 2026 and folded it into Zoom Revenue Accelerator. What changed, what the published price is now, which customers this is genuinely good news for, and how to tell whether you are one of them.
- [Connect Openpulse to ChatGPT, Claude and Claude Code](https://openpulse.cloud/blog/connect-mcp-clients): Step-by-step setup for each MCP client, the plan requirements that silently block a correct setup, what the OAuth 2.1 flow is doing behind the consent screen, and the prompts that get useful answers rather than a tool-call loop.
- [Does social listening actually work for lead generation?](https://openpulse.cloud/blog/does-social-listening-work): An honest answer from a vendor: the four conditions under which it works, the five under which it does not, what volume to realistically expect, and why the teams who report it working are usually describing something narrower than the category name.
- [Why your keyword alert is noise: a taxonomy of false positives](https://openpulse.cloud/blog/false-positive-taxonomy): Ten distinct reasons a candidate should be thrown away, in the order it is cheapest to throw it away, and why a system that records which one applied can tell a broken search apart from a working one with nothing to find.
- [Founder-led sales: a 30-minute weekly routine from public signals](https://openpulse.cloud/blog/founder-led-sales-routine): A concrete weekly routine for founders doing their own sales: what to read on Monday, how to decide which three threads are worth an hour, what to write, and the two metrics that tell you whether the motion is working before revenue does.
- [GummySearch shut down. What actually replaces it?](https://openpulse.cloud/blog/gummysearch-alternatives): GummySearch closed to new signups on 30 November 2025 after failing to reach a commercial Reddit API agreement, and deletes all user data on 1 December 2026. What the tool actually did, which replacements do which half of it, and the question to ask any of them before you migrate.
- [Intent data vs buying signals: not the same purchase](https://openpulse.cloud/blog/intent-data-vs-buying-signals): Third-party intent tells you an account is researching a topic. A buying signal is a post you can read and reply to. How Company Surge actually works, what 81% accuracy means in practice, and why teams that buy one and expect the other are disappointed on schedule.
- [Recruiters: three open roles is a company telling you something](https://openpulse.cloud/blog/recruiters-hiring-signals): Job boards tell every agency the same thing at the same time. What separates a recruiter who gets the brief is reading the pattern (role clustering, backfill language, seniority gaps and expansion evidence) from postings everyone can already see.
- [How to find customers on Reddit without getting banned](https://openpulse.cloud/blog/reddit-without-getting-banned): The actual rules (Reddit's Content Policy, the 9:1 reddiquette guideline, and the per-subreddit rules that override both), plus what automation is and is not allowed to do, and the reply pattern that does not read as marketing.
- [Turn your competitor's bad week into your pipeline](https://openpulse.cloud/blog/competitor-dissatisfaction-pipeline): How to build a rivals listener that finds people publicly fed up with a named competitor, roll it up by theme and trend, and push the urgent ones into Slack over a signed webhook.
- [One-star reviews are a qualified lead list](https://openpulse.cloud/blog/google-reviews-local-prospecting): How agencies and local-services vendors use Google reviews as a prospecting surface: resolve real businesses, gate on star rating before spending a model call, and roll complaints up by theme into a call list.
- [A job ad is a company telling you what is broken](https://openpulse.cloud/blog/job-postings-as-buying-signals): How to read hiring, funding and expansion as evidence of a budgeted problem, and why 'one hop, and the evidence must be in the post' is the rule that keeps derived leads from becoming invented ones.
- [Give your AI agent a research tool that reads live buying signals](https://openpulse.cloud/blog/mcp-server-ai-agent-signals): Connect Claude, ChatGPT, Grok or Claude Code to your Openpulse workspace over MCP: how the OAuth 2.1 flow works, what the eight tools do, why there is no create-listener tool, and the prompts that actually work.
- [Openpulse vs Brand24 and Mention: brand monitoring is not lead generation](https://openpulse.cloud/blog/openpulse-vs-brand24-mention): Brand24 and Mention tell you when your name comes up, across a billion sources, with sentiment and reach. Openpulse finds people who have a problem you solve and have never heard of you. Two different jobs that get bought interchangeably.
- [Openpulse vs Common Room: signal detection or identity resolution?](https://openpulse.cloud/blog/openpulse-vs-common-room): Common Room resolves signals to known people across 50+ integrations, from a published $2,500 a month. Openpulse finds public evidence of a budgeted problem, from $49 a month. They solve different halves of the same sentence.
- [Openpulse vs Klue: battlecards for your reps, or leads from your rival's churn?](https://openpulse.cloud/blog/openpulse-vs-klue): Klue is competitive enablement: battlecards, win-loss, arming your sales team from about $15k a year. Openpulse turns complaints about your competitors into a ranked pipeline. Both track rivals; only one produces leads.
- [Openpulse vs Octolens: mention monitoring or buying signals?](https://openpulse.cloud/blog/openpulse-vs-octolens): Octolens counts mentions of your keywords across 15+ platforms. Openpulse derives what to watch from your website and reads posts as evidence of a budgeted problem. An honest comparison, including where Octolens is the better buy.
- [Openpulse vs Trigify: pick a trigger from a list, or derive one from your website?](https://openpulse.cloud/blog/openpulse-vs-trigify): Trigify watches LinkedIn engagement and 16+ preset triggers at the person level, with contact data attached. Openpulse derives what to watch from what you sell, and reads posts as evidence of a budgeted problem.
- [Wire buying signals into your own stack: a webhook and API integration guide](https://openpulse.cloud/blog/webhooks-api-integration-guide): A complete, working integration: verify a signed webhook, dedupe on the delivery id, route by event, push to Slack and HubSpot, and pull history with a scoped API key. With the design reasoning for every header.

## Full text

- [llms-full.txt](https://openpulse.cloud/llms-full.txt): every claim the site makes: the sources
  read, the four listener types with their windows and labels, how candidates are
  judged, how results are delivered, both plans with prices and limits, and the FAQ,
  as one markdown file, so it can be answered from in a single fetch.

## For agents

Not reading: *calling*. These describe the two programmable interfaces and how to
get a credential for them.

- [api.md](https://openpulse.cloud/api.md): the MCP server at /mcp and the REST API under /v1,
  with the scope vocabulary and what an agent is deliberately not permitted to do.
- [openapi.json](https://openpulse.cloud/openapi.json): every REST operation a workspace API key
  can call, with typed parameters and unique operation ids. Generated from the
  server's own route table, so it cannot describe a route that is not mounted.
- [auth.md](https://openpulse.cloud/auth.md): how an automated client registers and what a
  credential is. There is no credential for an agent acting on its own behalf.
- [API catalog](https://openpulse.cloud/.well-known/api-catalog): the same two APIs as a linkset.
- [Capability manifest](https://openpulse.cloud/.well-known/ai-catalog.json): every document on
  this list, as one ARD entry set.

## Optional

- [Sitemap](https://openpulse.cloud/sitemap.xml): the indexable pages, with build dates.
- [Crawler policy](https://openpulse.cloud/robots.txt): AI crawlers are allowed on the public pages,
  and the Content-Signal line there allows search, AI input and training.
- [Contact](mailto:support@openpulse.cloud): a real address, answered by people.