Getting started

Requirements

• Chrome or another Chromium browser.
• Optional: your own TypeSafe API key, for the TypeSafe score.
• Optional, Pro product promotion: your own LLM API key (Anthropic, OpenAI or an OpenAI-compatible server) for prefill and reply drafts.

No X API key and no account with us.

Install

On install, the extension asks for Chrome's storage permission and access to pages under https://x.com/*. Other permissions are asked for only when you turn on a feature that needs them.

First setup

1. Open https://x.com.
2. Open the X Post Radar popup from the Chrome toolbar.
3. Add your niche keywords and any mute keywords.
4. Optional: change signal weights and thresholds. Every weight and threshold is editable.
5. Save your settings and scroll your timeline.

Each visible post gets a 0–100 score and a colored badge: high, medium or low priority. The score is computed in your browser from these signals: reach velocity (highest default weight), author reach (next-highest), reply window, discussion intent, reply ratio, keyword match and author verification. A post with almost no engagement cannot reach High, and a reply thread already crowded for the post's reach is pushed down. A post whose author's follower count is unknown is scored without that signal rather than scored as small.

The radar also learns locally from which badged posts you actually engage with.

Keywords

• Niche keywords are the relevance filter. When you set them, posts matching none of them are capped at low priority.
• Mute keywords hide matching posts from the radar.
• Auto-setup keywords (Pro), under Save Settings in the popup, fills the list from your bio plus recent posts and replies on x.com. The analysis stays in the browser, and existing keywords are replaced only after you confirm.
• Learn from my interactions (Pro) combines the newest 50 locally captured posts you liked, replied to or bookmarked with your profile, shows additions and removals, and changes the list only when you keep the review. You can revert the last list from the popup. No keyword learning runs in the background.

TypeSafe score (optional)

Off by default. It adds a second, AI-based score for how likely a reply is to be seen (for example TS 72%) next to the local score.

1. Turn on the TypeSafe score in the popup. Chrome asks for one extra permission, https://api.typesafe.ai/*. If you decline, the toggle switches back off.
2. Enter your TypeSafe API key in the popup's Settings tab. Press Test to check it.

While it is on, each highlighted post is sent to api.typesafe.ai with your key. Exactly these fields are sent: the post's text (truncated at 4,000 characters), your niche keywords, the post's public like, retweet and reply counts, and the post's age in whole minutes (capped at one week). No handles, display names, avatars, links, post IDs or anything about you is sent. Requests are billed to your TypeSafe account; results are cached per post.

Your keys stay in the extension's own IndexedDB storage in this browser, which websites, x.com pages and other extensions cannot read. They are not encrypted on disk.

AI-likelihood check (optional)

Off by default, with its own toggle. It looks for common AI-writing patterns in each visible post or reply and shows how likely it is AI-generated, for example AI 87%. Click it to see the patterns behind the number.

• It runs in your browser. No key is needed and nothing is sent.
• One pattern alone never scores high; several together do. A very short post with no clear sign shows nothing.
• Optionally hide posts at or above an AI-likelihood you choose. Each hidden post has a Show post button. While hiding is on, hidden posts also stay out of Top posts and Find leads.
• With the TypeSafe score also on, Jev (TypeSafe) rates each post too and the two are combined. In that case the text of every visible post is sent to api.typesafe.ai with your key, once per page view, which may increase your TypeSafe usage.

Pro features

• Top posts panel. A floating panel ranks the current page's top 10 posts by Jev (TypeSafe), Algorithm (the local score) or Combined (the average of the two). Algorithm works with TypeSafe off. Pick the panel's theme (System, Light or Dark) in the popup's Settings tab.
• Follower counts on badges.
• Keyword Auto-setup and keyword learning, described under Keywords.
• Product promotion. In the popup's Products tab, press Scan on your product's landing page to build a product profile. In the Leads view of the Top posts panel on x.com, press Find leads to rank the posts collected on the page where one of your products helps. Write draft asks your own LLM for a reply in one of five writing styles; you edit it, copy it, and the post opens on X for you to paste and post yourself. Every request is started by you and uses your own keys.

Buying, restoring and canceling Pro

• Upgrade to Pro in the popup opens ExtensionPay's checkout, on Stripe. Plans: $4.99 per month, $29.99 per year, or $49.99 once for lifetime access. After paying, reopen the popup; it checks your purchase and turns Pro on.
• Restore purchase opens ExtensionPay's login page, which emails you a sign-in link. Use it on another browser.
• Manage plan opens ExtensionPay's management page, where you can cancel. Pro stays active until the end of the paid period.
• Refunds within 14 days of a charge: email contact@luongnv.com with your purchase email address.

Troubleshooting

• The badge shows TS –. The TypeSafe key is missing or rejected, you hit a rate limit, or the network failed. Check the key with Test in Settings. The local score and highlight keep working, and the AI-likelihood falls back to the local pattern score.
• A post is missing from the Jev or Combined view. Those views rank a post only once its TypeSafe score is ready. The Algorithm view still ranks by the local score.
• The popup says "offline". ExtensionPay could not be reached. Pro keeps working for up to 7 days after the last successful check.
• Badges look wrong after an X update. X can change its pages at any time, which can affect scoring until the extension is updated.

Uninstall

Remove X Post Radar from chrome://extensions. Uninstalling removes the data the extension stored in your browser. Data held by TypeSafe, your LLM provider, ExtensionPay or Stripe is kept under their own policies; see the privacy policy.

Back to X Post Radar