YourICP

Activate a login completed in the browser. Call this after signing in at the login page. Automatically retrieves the auth token and activates it for this session — no copy/paste needed.

Get the download link for a completed audience run. Returns a presigned URL the user can click to download their contact list. RENDERING — MANDATORY, VERBATIM: The response contains a download link already formatted as a markdown link with an angle-bracket destination: [Download ...](<https://...>). Present it exactly as returned. Keep the angle brackets around the URL, do NOT percent-encode or decode any query parameters, and do NOT drop, reorder, or truncate any parameter — every response-content-* and X-Amz-* param must be preserved byte-for-byte. Do NOT rewrite it into a code block, a bare URL, or an HTML anchor; emit the markdown link as the backend sent it.

Fetch all available audience filter categories as an interactive filter picker. Only call this after audience_start has been called and the user chose Option B (interactive filter picker). Do not call this tool to guess or pre-populate filters on behalf of the user. RENDERING — MANDATORY, VERBATIM: The response is usually a complete HTML document. Pass the returned HTML string unchanged to the visualizer/render tool. Do NOT rebuild, restyle, summarize, trim, or hand-author a replacement UI. If the response is plain text instead of an HTML document (this happens on clients that cannot render HTML), simply present that text to the user as-is and let them pick filter values by name — do not look for a visualizer. Render EVERY tab and EVERY chip exactly as received, in the order received, using the exact data-cat and data-val attributes the backend emitted. This includes tabs whose chip list is empty — render the empty tab as-is, do NOT drop it and do NOT invent or backfill chips for it. ALWAYS keep the "Get estimation" button (id="getEstBtn") in the rendered widget. It is the action control the user clicks to run the preview — never remove, hide, rename, or replace it. Do NOT move a chip from the tab/category the backend placed it in. If a value arrives under data-cat="industries", it is rendered and reported under industries — the client must not re-route it to seniority, departments, buying_roles, employee_size, or revenue based on its label. Field placement is the backend's responsibility, not the client's. When the user makes selections, resolve names→keys ONLY via the <script id="filter-key-map"> JSON in the returned HTML, then call audience_preview with those exact keys.

Preview audience size from explicit filter selections made by the user in the filter picker UI. IMPORTANT: Only call this after audience_get_filters has been shown and the user has made their own selections. Never infer or pre-fill filter values — only pass values the user explicitly selected. If the user has not yet seen the filter picker, call audience_start then audience_get_filters first.

Preview audience size from a free-text description the user provided in this conversation. IMPORTANT: Only call this after audience_start has been called and the user has described their target audience in their own words (Option A). Never pre-select or assume filter values — only use criteria the user explicitly stated. If the user has not yet described their audience, call audience_start first.

Entry point for all audience-building workflows. Always call this first when the user wants to find contacts, build an audience, or get a contact list. This tool decides which options to offer based on the connected client: clients that can render the interactive filter widget (e.g. Claude) are offered both (A) describe their target in free text and (B) pick filters interactively; other clients are offered free text only. Present EXACTLY the options contained in this tool's response and nothing more — in particular, do not offer or mention the interactive filter picker unless the response includes it. Do not call audience_quick_preview, audience_preview, or audience_get_filters without calling this tool first.

Start a contact pull run for a built audience. Requires audienceId from the build step and totalContacts from preview. Set phoneValidation to true to also confirm each contact's phone number with a live phone call; it raises the price per contact from $0.05 to $0.19. The file is ready straight away with each phone marked "processing"; call results arrive over the following days, and downloading the run again returns them. If logged in, the run is charged to the account's YourICP billing-token balance (5 billing tokens per contact, 19 with phoneValidation, where 100 billing tokens = $1.00) and returns a runId — call audience_download_run immediately after. Call check_billing_balance first if you want to tell the user the cost before spending. If the balance is short, this returns error "mcp_insufficient_tokens" with required, available and shortfall counts — tell the user exactly how many tokens to top up at app.youricp.com and do NOT retry until they have. If it returns "mcp_no_billing_account", the client is not linked to an account yet and only support can fix it — do NOT retry. If not logged in, card payment is required instead ($0.05 per contact, $0.19 with phoneValidation, capped at $1,000) — this tool returns a checkoutUrl and sessionId, then call check_payment, then audience_download_run with the runId. Card payments start at $0.50; below that it returns error "below_card_minimum" — suggest signing in instead.

Read the YourICP BILLING TOKEN balance this account's runs are charged against. Billing tokens are YourICP's prepaid currency: 100 billing tokens = $1.00, and an audience contact costs 5 billing tokens, or 19 with phoneValidation. They are NOT the auth token — that is the API credential set by set_auth_token. Call this before audience_start_run when the user asks what a run will cost, or after an "mcp_insufficient_tokens" error to confirm the balance. Requires the user to be logged in.

Check the result of a previously submitted contact enrichment job by jobId. Polls every 5 seconds until the job is complete (max 2 minutes). Returns enriched contact data or an error message.

Check whether a Stripe checkout session has been paid and execute the next step. Call this after presenting the checkoutUrl to the user. If status is "pending", wait a few seconds and call again. - If called after submit_lookup: once status is "done" call check_lookup with the returned jobId. - If called after audience_start_run: once status is "done" call audience_download_run with the returned runId.

Set the user's YourICP auth token for this session. Call this when the user pastes their auth token in the chat. This is an API credential, NOT YourICP billing tokens — billing tokens are the prepaid currency a run spends, and check_billing_balance reads them. Once set, the auth token is used for all API requests and card payment is no longer required. To get an auth token, the user can log in at https://mcp.youricp.com/authorize.

DEPRECATED — call set_auth_token instead. Sets the user's YourICP auth token for this session.

Submit a contact enrichment job for one or more email addresses or LinkedIn profile URLs. Provide emails, linkedInUrls, or both. Set phoneValidation to true to also confirm each phone number with a live phone call; it raises the price per contact from $0.02 to $0.19. If logged in, the job is charged to the account's YourICP billing-token balance (2 billing tokens per contact matched, 19 with phoneValidation, where 100 billing tokens = $1.00) and returns a jobId — call check_lookup to retrieve results. check_billing_balance shows what the balance covers. If the balance is short, this returns error "mcp_insufficient_tokens" with required, available and shortfall counts — tell the user exactly how many tokens to top up at app.youricp.com and do NOT retry until they have. If it returns "mcp_no_billing_account", only support can fix it — do NOT retry. If the user is not logged in, card payment is required instead ($0.02 per contact, $0.19 with phoneValidation): this tool returns a checkoutUrl and sessionId — present the URL, then call check_payment. Card payments start at $0.50; below that it returns error "below_card_minimum" — suggest signing in instead. Do NOT retry automatically on failure.