Skip to main content
Back

Monitor tagged X mentions through native notifications, then use a saved search, a small listening product, or X's pay-per-use recent-search API for untagged brand and competitor terms.

The market still ranges from free manual checks to enterprise listening suites, but X's current developer documentation now describes a credit-based, pay-per-use API with no subscription commitment. That makes a small recent-search poller economically possible, although it still needs engineering, credentials, monitoring, and an alert destination.

Maeve connects X for publishing, but its inbox does not monitor X at all, for the economic reasons below. The answer here is mostly not a paid tool, and the last section says where Maeve fits and where it does not.

Tagged Mentions Are Free, and That Changes the Question

Two jobs hide inside monitoring. Tagged mentions and replies can appear in X notifications without a separate listening subscription, subject to the account's filters and notification settings. Untagged names, misspellings, and competitor terms require search.

The job that costs money is the other one: catching posts that mention your brand without tagging it, watching a competitor's name, or following the replies under someone else's post. That needs search, run on a schedule, by something that does not sleep, and search access is exactly the thing X spent three years pricing.

Before paying, save a native search containing the quoted brand name, common spelling variants, and exclusions for the brand's own account. Saved search is a manual workflow, not a dependable alert channel, so assign a checking cadence. Do not treat Google Alerts as complete X coverage because external search indexing does not guarantee a complete or timely X dataset.

Maeve Inbox

Supported comments, messages, and reviews across Instagram, Facebook, Threads, TikTok, Google Business Profile, and YouTube. X connects for publishing, not monitoring or analytics.

See the Inbox

Plan, preview, and publish in one workflow

What Actually Happened to the Cheap Middle, With the Numbers

X's current documentation says the API uses prepaid, pay-per-usage credits with no subscriptions or minimum commitment. Different endpoints have different prices, and current rates are available in the Developer Console.

As checked in August 2026, Posts read cost $0.005 per resource and ordinary Post creation costs $0.015 per request, with other write types priced differently. The pay-per-use plan is capped at three million Post reads per monthly billing cycle. Recent search covers the recent window documented for that endpoint, not a complete historical archive.

Because X explicitly says prices are subject to change, any automated monitor needs a spending limit and a current-rate check in the console.

The Do-It-Yourself Route

A basic implementation calls the recent-search endpoint on a schedule, stores the newest result ID, passes it back as since_id, deduplicates results locally, and forwards new matches to Slack, Discord, or email. n8n, Make, or a small service can run the loop. X bills returned resources under the current endpoint rules, so set a spending limit and monitor usage. The n8n integration guide covers the surrounding automation choices.

The arithmetic is the point. A brand that gets mentioned 300 times a month costs about $1.50 to watch. The 2,000 mentions that Brand24's entry plan caps you at would cost about $10 on the meter. Even a noisy keyword pulling 10,000 posts a month runs $50, a quarter of the entry price of the nearest subscription tool. The real costs sit elsewhere: a developer account and an app to set up, credits to prepay, a workflow to check on occasionally, and no sentiment, no history dashboards, and no report you can hand a client.

Some tools scrape public X pages rather than using the API. That approach can break when the site changes and may conflict with X's terms or access controls. It is a poor foundation for client monitoring that needs predictable coverage and auditability.

The Paid Options, Priced Honestly

The table uses prices shown on official vendor pages in August 2026. Awario Starter is $49 month to month or $29 a month billed annually. Brand24 Individual is $249 monthly or $199 a month on annual billing. Confirm X coverage, refresh frequency, keyword limits, and mention allowances during the trial because those details can change independently of the headline price.

OptionPriceWhat you get, and the catch
X notificationsFreeTagged mentions and replies can appear here, subject to the account's notification settings and filters. It does not find untagged names.
Saved search in the appFreeFinds untagged terms using the search syntax X currently accepts. Treat it as a manual check rather than a guaranteed alert feed.
XPro (TweetDeck)Included with the eligible Premium+ subscription in your regionLive columns for searches and lists. Check the current regional subscription price and whether the workflow provides the alerts you need.
DIY on the pay-per-use APIUsage based$0.005 per Post read when checked in August 2026, with endpoint-specific rates and a three-million monthly Post-read cap. You build and operate the poller, alert route, storage, and reporting.
Awario$49 monthly or $29 a month billed annuallyA lower-cost listening product. Confirm current source coverage and allowances in its trial.
Brand24$199 a month on annual billing, $249 monthly3 keywords, 2,000 mentions a month, sentiment scoring. The entry plan refreshes every 12 hours, which is not the ping-in-minutes people picture when they buy it.
Scraper-based toolsFree to cheapRead X without the API, so there is no bill and no terms-of-service cover. They can break or be blocked any day.
Brandwatch, Meltwater, TalkwalkerQuotedReal cross-platform listening, trend history, and client-ready reporting. Correct when listening is the deliverable, overkill for a ping when you get mentioned.
The X monitoring market in 2026, from free to a sales call

Ration the Pings

Tier the alerts. Instant notifications only for the tiny list that justifies interrupting you, your brand name, your own handle, competitor launches, and everything else accumulates into one weekly digest you actually sit down and read. Alert on everything and you will start ignoring the channel inside a week, which is worse than having no channel, because you believe you are covered.

Then separate someone is annoyed at us from someone mentioned us, and let the angry ones jump the line. A complaint on X compounds in a way a compliment does not, so the mention you want in minutes is the unhappy one. The practical version is a second, louder route for mentions containing your business's complaint words, refund, broken, worst, whatever yours are, whether that is a separate n8n branch, a storm alert in a listening tool, or a second saved search you check more often than the first.

Set response targets from the risk and service level. A support complaint may need a faster route than a neutral industry mention, while low-priority discovery terms can wait for a digest.

Where We Fit, Which Is Mostly Not Here

Maeve connects X for publishing: the Twitter scheduler queues posts and threads. Maeve does not provide X monitoring or X analytics. Its inbox covers supported comments, messages, or reviews across Instagram, Facebook, Threads, TikTok, Google Business Profile, and YouTube.

So the fit is this: if X is one channel among several and the daily grind is really conversations on Meta platforms plus a steady X posting cadence, a scheduler with an inbox covers most of the week and one of the cheap monitors above covers the X gap. What separates an engagement queue from a listening tool is its own page: the best social media engagement tools. And if the wider question is when any of these line items is worth paying for at all, that judgment lives in how to justify the cost of social media tools.

Use native notifications for tagged activity, a saved search for a manual untagged check, and either a listening product or a pay-per-use recent-search workflow when automation is worth operating. Check the Developer Console's live endpoint rates, cap spend, and test coverage before relying on it for a client.