Search X (Twitter) posts
X (Twitter)Tweets matching search terms, hashtags or from given handles: text, author, engagement, date. Each search term takes X's advanced search operators (from:, since:, min_faves:, filter:, lang: …).
Get X (Twitter) profiles
X (Twitter)Profile details for X/Twitter handles: bio, followers, following, verification, counts.
Get X (Twitter) post replies
X (Twitter)Replies to X/Twitter posts by URL: text, author, engagement, date.
Hand it to your AI agent
Copy this prompt into Claude Code, Cursor, Codex or any coding agent. It tells the agent where the docs are and how to use your API key.
Use the Lovely Router X (Twitter) data tools to get data for me. They return JSON and are billed per result.
- Docs (read first): https://lovelyrouter.com/docs/tools.md and https://lovelyrouter.com/docs/tools/run.md and https://lovelyrouter.com/docs/api/tools.md
- Tools for this:
- `x-search`: Search X (Twitter) posts ($0.000388 / tweet)
- `x-profile`: Get X (Twitter) profiles ($0.000375 / profile)
- `x-replies`: Get X (Twitter) post replies ($0.000375 / reply + $0.00075 / call)
- Run: POST https://lovelyrouter.com/v1/tools/<id>/run with `{"input": {...}, "max_results": N}`. A 200 has the finished run with `items`; a 202 means it is still running, so poll the `poll` path until `status` is `succeeded`, `failed`, `timed_out` or `stopped`.
- Each tool takes its own input fields: read them with GET https://lovelyrouter.com/v1/tools/<id> (public, no key needed) before the first run.
- If you support MCP, you can instead connect the server https://lovelyrouter.com/mcp (Streamable HTTP, same key; https://lovelyrouter.com/docs/tools/mcp.md) and use suggest_tools, get_tool and run_tool.
- Auth: read my API key from the LOVELY_API_KEY environment variable and send it as `Authorization: Bearer $LOVELY_API_KEY`. Never print or commit the key. If it is not set, ask me to create one at https://lovelyrouter.com/app/keys.
- Billing is prepaid: every call is charged to my balance, so test with a small request before running anything large.
- Every docs page is plain Markdown; the full index is https://lovelyrouter.com/llms.txt.
My task: <describe the data you need and the output format>Run one from code
How runs, polling and billing work →curl https://lovelyrouter.com/v1/tools/x-search/run \
-H "Authorization: Bearer $LOVELY_API_KEY" \
-H "content-type: application/json" \
-d '{"input":{"searchTerms":["\"gemini argon\" min_faves:50 -filter:replies since:2026-10-01 lang:en"],"maxItems":20,"queryType":"Top"},"max_results":10}'Each tool page lists its input fields and an example input. Agents can use every tool over MCP: MCP server
Frequently asked questions
What data can I get from X (Twitter)?
3 tools: Search X (Twitter) posts, Get X (Twitter) profiles, Get X (Twitter) post replies. Each returns JSON and has its own page with its input fields and price.
Is this a Twitter scraper?
Yes. If you searched for a Twitter scraper, an X scraper or a Twitter search API, this is it: Post search, profiles and replies from X (Twitter), as JSON.
How much does it cost to scrape X (Twitter)?
Each tool has its own price per result, from $0.00038. You pay only for results delivered, from a prepaid balance with no subscription.
Do I need a X (Twitter) account or API key?
No. You call the tools with your Lovely Router API key and get JSON back; there is nothing to set up on X (Twitter).
Can AI agents use these tools?
Yes. Connect Claude Code, Cursor or any MCP client to the Lovely Router MCP server and the agent picks the right tool with suggest_tools and runs it with run_tool.
Can I use the data any way I like?
You are responsible for using the data lawfully, including privacy law when results contain personal data. See the Acceptable Use Policy.