Integrations

Open Integrations and connect one of these with an API key from your account there:

• Ballast tests the key when you save it by reading your credit balance. The test uses no credits.
• The key is encrypted and never shown again, not even to you. The page shows its last 4 characters and your remaining credits.
• One verifier at a time. Check it again, replace the key or disconnect it from the same page. Owners and admins manage integrations.
• If the verifier refuses the key later, or credits run out, the integration shows the error. Leads keep the free checks until it works again.

Once connected, use Verify on selected leads, or verify every new address at the end of an import. Only addresses the free checks didn't already settle use credits. How the results are used: Leads, verification.

Disconnecting deletes the key. Results you already have stay on the leads.

Reply labels and Write with AI run on Ballast's OpenAI and Gemini accounts by default, with the monthly drafts in your plan. Connect your own OpenAI or Gemini key under Integrations, AI provider and both run on your account instead:

• Reply text and drafts go only to your provider, under your account with them. Nothing falls back to Ballast's keys.
• No monthly draft limit. You pay the provider for what you use.
• Ballast tests the key on save with a request of a few tokens. It is encrypted and never shown again. One AI key at a time.
• If the provider refuses the key later, the integration shows the error and AI features stop until you fix it.

Both start on the provider's cheapest model, the one Ballast runs. Owners and admins can pick a stronger one for Write with AI and for reply labels separately; a new pick is tested with your key first, and the cheapest model stays as the fallback.

Claude, ChatGPT, Cursor and Claude Code connect over MCP. Scripts and other tools use the REST API with an API key, and hear about events through webhooks.