使用场景

读懂 X 帖子下的回复，看产品发布反响如何

Q: 一次运行可以传入多个帖子吗？

postUrls 是列表，所以可以。resultsLimit 的上限是共用的，帖子越多，就应相应调高。

Q: 每条回复里有什么？

文本、作者、互动数据和日期。

以 JSON 收集任意 X（Twitter）帖子下的回复，含文本、作者、互动数据和日期，用来评估对产品发布、公告或投诉的反应。

预付费，无订阅REST 或 MCP一个密钥搞定模型、数据和智能体

无论是你发布产品，还是竞争对手发布产品，公告下的回复都是了解反响最快、最真实的渠道，但没人会逐条去读 400 条回复，而且这个帖子还在不断增长。Lovely Router 替你读。发送帖子链接，每条回复返回一个 JSON 对象，按回复数量从预付费余额中计费。用一个 API 密钥，就能从脚本、每日报告或 AI 智能体中调用。

交给你的 AI 智能体

把这段提示词复制到 Claude Code、Cursor、Codex 或任何编程智能体中。它会告诉智能体文档在哪里，以及如何使用你的 API 密钥。

读懂 X 帖子下的回复，看产品发布反响如何. Use the Lovely Router data tools: each returns JSON and is billed per result.

- Docs (read first): https://lovelyrouter.com/docs/tools/find.md and https://lovelyrouter.com/docs/tools/run.md
- Plan first: POST https://lovelyrouter.com/v1/tools/suggest with `{"task": "<my task in plain words>"}` (free). It returns the tools to run in order, each with an example `input`, the `input_required` fields, an estimated cost and a ready-made `run` request. Replace the example values with my task's; if a field is unclear, read the tool with GET https://lovelyrouter.com/v1/tools/<id>. To browse instead, POST https://lovelyrouter.com/v1/tools/discover searches the catalog.
- Show me the plan and its estimated cost (`total_est_cost_usd`) before running anything large.
- 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`.
- Only delivered results are billed. Keep max_results small on the first run, check the output, then scale up.
- If you support MCP, connect https://lovelyrouter.com/mcp instead (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: <the inputs (links, keywords or accounts) and how many results you need>

工作原理

选出帖子
复制重要帖子的链接：你的发布帖、竞争对手的公告、一条传播开的投诉。
设置上限后运行工具
把链接连同 max_results 发送到 POST /v1/tools/x-replies/run。运行会从你的余额中预留它的最高费用，并以 JSON 返回回复。
梳理大家说了什么
把回复归类为提问、好评、缺陷报告和功能需求，可以手动，也可以交给模型，再按互动量排序。

一次请求获取帖子的回复

获取 X（Twitter）帖子回复在 postUrls 中接受帖子链接，上限填在 resultsLimit：

Shell

curl https://lovelyrouter.com/v1/tools/x-replies/run \
  -H "Authorization: Bearer $LOVELY_API_KEY" \
  -H "content-type: application/json" \
  -d '{
    "input": {
      "postUrls": ["https://x.com/elonmusk/status/1905584213761351970"],
      "resultsLimit": 100
    },
    "max_results": 100
  }'