Mention triage
Every hour Memtro records new mentions. Support asks what people said about the outage; Memtro lists the mentions with engagement so the team can reply to the loudest threads first.
See what your account posted and who is talking about you on X.
Connect an X account to read its profile metrics, recent posts with engagement and impressions, mentions and 7-day search results. Note that the X API is a paid, pay-per-use product: your developer app needs credits before posts can be read.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right X (Twitter) tool, reads what it needs, and answers with the source cited.
Every hour Memtro records new mentions. Support asks what people said about the outage; Memtro lists the mentions with engagement so the team can reply to the loudest threads first.
The founder asks how the launch posts landed. Memtro returns impressions, likes and reposts per post and the mentions they triggered, in one answer.
Questions people ask once X (Twitter) is connected. In agent mode each one also checks the other systems that know about the same people, companies or identifiers.
Teams that get the most from X (Twitter) in Memtro, with the rest of their stack attached.
A record in X (Twitter) is rarely the whole story. Connect the systems that hold the rest and the agent cross-references them by default, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The X (Twitter) tools are the same everywhere.
Clients and agents →Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.