Precleared

Docs ยท Recipes

Check the leads your agent builds in Bitscale before they reach a sequencer

Bitscale builds lead grids and pushes them to sequencers such as Instantly, Smartlead and lemlist. Connect Precleared's MCP server next to Bitscale's, so your agent checks each row's email address before the push.

What you need

  • A Precleared key. Every new key starts with 14 days at 100 checks a day, then your own 100 a day over MCP, no card needed. Get a free key.
  • Bitscale's MCP server, which signs in with OAuth and asks you to pick a workspace. Bitscale's pages differ on who has access, so check yours.

1. Connect both servers

In Claude.ai or the Claude desktop app, open Customize, Connectors, Add connector, Add custom connector. Name it Bitscale MCP, paste https://api.bitscale.ai/mcp, then Add, Connect, pick your workspace and approve. Add Precleared with https://precleared.dev/mcp?src=guide-bitscale, or from the Claude directory. See Bitscale's MCP docs.

In Claude Code, add Precleared with:

claude mcp add --transport http precleared "https://precleared.dev/mcp?src=guide-bitscale" --header "Authorization: Bearer pc_live_..."

2. Give your agent the rule

Paste this into your agent's instructions, a project's instructions or a skill:

Before any Bitscale row is pushed to a sequencer, call Precleared's contact_check once for the row's email address. Send address_source (where you got the address) and sender_country, plus company_name and pitch when you know them.
- ok_to_email: let the row go through to the push. Keep the receipt id in the row.
- consent_needed or blocked: mark the row with update_rows_v1 so it's left out of the push, and note the next_step.
- unknown: hold the row back for now. Supply the missing fact (recipient_country, default_recipient_country if all your prospects are in one country, or company_number), then check again.
Every email must meet footer_text: usually who you are, a postal address and a way to opt out.

What happens to each lead

VerdictWhat your agent does in Bitscale
ok_to_emailLets the row through to the push, keeping the receipt id
consent_needed or blockedMarks the row so it's left out of the push
unknownHolds the row until the missing fact is supplied, then checks again

Good to know

  • Bitscale pushes to sequencers through its integrations, for example lemlist's Add/Update Lead, so the gate is which rows get pushed.
  • Prefer a column to an agent? Bitscale's HTTP API column can call Precleared on every row, the same way as our Clay recipe.
  • Settings come from Bitscale's MCP docs as of 30 October 2026.
  • The ?src=guide-bitscale tag on Precleared's address only tells us which guide you used. It doesn't change your allowance or your results.

Every check has a signed receipt. Open precleared.dev/r/ followed by its id to show a client why an email went out.

Decision support with sources, not legal advice.