How will credits work for the MCP Server & API?

One credit pool per workspace. Resets monthly. Credits are spent the moment a visitor on your site is identified.

What charges: 1 credit when the company is identified, 1 credit when the contact is identified, maximum 2 credits per unique visitor per month.

What doesn't charge: list_warm_visitors reads, list_warm_accounts reads, get_credits_remaining, and the same visitor being identified again within the same calendar month (per-month dedupe).

The dedupe matters more than people expect. Once Jane from Acme is identified on day 5, every subsequent session of hers this month is free. Credits work less like a meter and more like a library card. You're paying for the universe of accounts you've unlocked, not for every read.

Rate limits: 60 requests per minute on free tier, 120 per minute on paid. The server returns HTTP 429 when you exceed; back off about 60 seconds and retry.

When You Run Out of Credits

The MCP returns a structured error your agent can relay verbatim. Reads from list_warm_visitors and list_warm_accounts keep working on everyone already identified. Re-pulling anyone you've already paid for this month keeps working. New visitor identifications get paused until either the calendar month resets or you upgrade.

Heads-up: the credit pool is shared across the whole Warmly product. Running out also pauses visitor identifications and orchestrations in the app itself. The MCP isn't on its own meter.

Upgrades are self-serve via HubSpot payment links. Pick your tier, pay, use the same email as your Warmly account. We bump your tier within one business day. Webhook automation lands later this quarter.