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
})料金の目安
| 結果 | 実行回数（1 回あたり最大 1000 件） | 原価 |
|---|---|---|
| 100 | 1 | $0.20 |
| 1,000 | 1 | $2.00 |
| 10,000 | 10 | $20.00 |
プリペイド、サブスクリプションなし。結果が要求より少なければ料金も下がります。 料金
用途
よくある質問
メール付き B2B リードを検索 API の料金はいくらですか？
$0.002 / lead。1 回最大 1000 件で 1,000 件取得すると $2.00 です。サブスクリプションはなく、プリペイド残高から支払います。
1 回の実行で何件の結果が返りますか？
既定は 25 件、1 回あたり最大 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 で実行します。
実行が失敗するとどうなりますか？
失敗または停止した実行は、届いた結果の分だけを支払い、呼び出し料金はかかりません。実行開始時に最大費用を確保し、精算時に残りを解放します。