交给你的 AI 智能体
把这段提示词复制到 Claude Code、Cursor、Codex 或任何编程智能体中。它会告诉智能体文档在哪里，以及如何使用你的 API 密钥。
Use the Lovely Router data tool "查找带邮箱的 B2B 销售线索" (id `b2b-leads`, B2B database) to get data for me. It returns JSON.
- Docs (read first): https://lovelyrouter.com/docs/tools/run.md and https://lovelyrouter.com/docs/api/tools.md
- Input fields and price: GET https://lovelyrouter.com/v1/tools/b2b-leads (public, no key needed). Price: $0.002 / lead.
- Run: POST https://lovelyrouter.com/v1/tools/b2b-leads/run with a body like `{"input":{"personTitleIncludes":["head of marketing"],"personLocationCountryIncludes":["United States"],"companyIndustryIncludes":["Computer Software"],"hasEmail":true,"totalResults":3},"max_results":10}`. 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 (up to 1000 per 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 with tool "b2b-leads".
- 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, e.g. which places, profiles, keywords or URLs, and the output format>输入
personTitleIncludesstring[]Job titles to match, e.g. ["VP of Sales", "CEO"]. Turn on includeTitleVariants for CEO Chief Executive Officer.
personTitleExcludesstring[]What this does: Removes people with titles matching these terms. Best practice: Use this to remove assistant/junior/intern-style false positives.
includeTitleVariantsbooleanWhat this does: Expands common title equivalents (e.g. CEO Chief Executive Officer). Best practice: Turn ON for broader recall; turn OFF only when you need strict title wording.
seniorityIncludesstring[]What this does: Includes selected seniority levels. Best practice: Pair with Excludes to keep only target decision levels.
functionIncludesstring[]What this does: Includes selected departments/functions. Best practice: Start with 1-2 core functions before broadening.
hasEmailbooleanOnly leads with an email address.
hasPhonebooleanOnly leads with a phone number.
emailStatusIncludesstring[]Email deliverability, e.g. ["verified"].
personFirstNameIncludesstring[]What this does: Includes only leads with these first names. Best practice: Use only when you already know exact names.
personLastNameIncludesstring[]What this does: Includes only leads with these last names. Best practice: Combine with title/company/location to avoid over-restricting.
personLocationCountryIncludesstring[]Country names, e.g. ["United States"].
personLocationStateIncludesstring[]What this does: Includes selected person states/regions. Best practice: Use country + state together for cleaner geography.
personLocationCityIncludesstring[]What this does: Includes only people in these cities. Best practice: Combine with country/state filters so city names are interpreted correctly.
companyNameIncludesstring[]What this does: Includes leads at companies whose names match any entered value. Best practice: Use for account-based targeting (named account lists).
companyIndustryIncludesstring[]Industry names, e.g. ["Computer Software"].
companyKeywordIncludesstring[]What this does: Includes companies whose name/description contains these keywords. Best practice: Use product/problem keywords to find similar companies.
companySizeIncludesstring[]Employee-count buckets, e.g. ["51-200"].
companyDomainIncludesstring[]Company websites without https://, e.g. ["stripe.com"].
companyLocationCountryIncludesstring[]What this does: Includes companies headquartered in the selected countries. Best practice: Use with company state/city filters for precise geo targeting.
companyLocationStateIncludesstring[]What this does: Includes selected company HQ states/regions. Best practice: Use with country/company city for precise HQ targeting.
companyLocationCityIncludesstring[]What this does: Includes companies headquartered in these cities. Best practice: Pair with country/state for cleaner location matching.
annualRevenueIncludesstring[]What this does: Includes companies in selected annual revenue bands. Best practice: Choose bands that match your ideal customer budget.
fundingStageIncludesstring[]What this does: Includes companies in selected funding stages. Best practice: Match stage to your go-to-market motion (startup vs enterprise).
technologiesIncludesstring[]What this does: Includes companies using any of the selected technologies. Best practice: Add 1-3 core tools your ICP uses (e.g. Salesforce, HubSpot). More filters narrow the pool.
totalResultsintegerWhat this does: Sets how many leads to extract in this run. Best practice: Start with a smaller test run (e.g. 200-1000), then scale up once the results look right.
试一试
在代码中调用
了解运行、轮询与计费 →curl https://lovelyrouter.com/v1/tools/b2b-leads/run \
-H "Authorization: Bearer $LOVELY_API_KEY" \
-H "content-type: application/json" \
-d '{"input":{"personTitleIncludes":["head of marketing"],"personLocationCountryIncludes":["United States"],"companyIndustryIncludes":["Computer Software"],"hasEmail":true,"totalResults":3},"max_results":25}'# MCP (agents): suggest_tools → get_tool → run_tool
run_tool({
"tool": "b2b-leads",
"input": {"personTitleIncludes":["head of marketing"],"personLocationCountryIncludes":["United States"],"companyIndustryIncludes":["Computer Software"],"hasEmail":true,"totalResults":3},
"max_results": 25
})费用示例
| 结果 | 运行次数（每次最多 1000 条） | 成本 |
|---|---|---|
| 100 | 1 | $0.20 |
| 1,000 | 1 | $2.00 |
| 10,000 | 10 | $20.00 |
预付费，无需订阅。返回的结果少于请求数量时费用更低。 价格
适用场景
常见问题
查找带邮箱的 B2B 销售线索 API 的价格是多少？
$0.002 / lead。以每次最多 1000 条获取 1,000 条结果，费用为 $2.00。无需订阅：从预付费余额中扣除。
一次运行返回多少条结果？
默认 25 条，每次最多 1000 条。用 max_results 限制单次数量：只为实际交付的结果付费。
需要 B2B database 账号或 API 密钥吗？
不需要。用你的 Lovely Router API 密钥调用工具即可获得 JSON，无需在 B2B database 上做任何设置。
AI 智能体可以使用这个工具吗？
可以。把 Claude Code、Cursor 或任何 MCP 客户端连接到 Lovely Router 的 MCP 服务器：智能体用 suggest_tools 找到这个工具，再用 run_tool 和 id b2b-leads 运行它。
运行失败会怎样？
失败或被停止的运行只为已交付的结果付费，不收调用费。运行开始时会冻结最高费用，结算后释放剩余部分。