Plans and limits

Every plan includes a number of leads per billing period. Only real leads count: junk, newsletters, notifications and repeat messages from the same person are free.

PlanPrice / monthLeads includedEach extra leadWorkspacesRequests / s
Free$050— (processing waits)15
Starter$49300$0.15125
Pro$1291,000$0.12325
Agency$3493,000$0.102550
Scalefrom $999from 10,000by contractunlimitedby contract

Prices are in US dollars; GST is added for Australian businesses. See Pricing. Leadveyor is free during the beta.

What counts

  • A lead — a new lead created from a message. When the same person writes again (same email or phone), the message is merged into their lead and is not counted again.
  • Free, up to a generous limit — messages that are not leads (junk, newsletters, notifications): up to 10× your lead allowance per period.
  • Evaluate — POST /v1/evaluate: 200 calls per period are free; after that every 4 calls count as one lead.
  • Generating profiles from a description — 50 per period.
  • Test mode — keys starting with lv_test_ have their own 100 leads per period and don't use your plan's leads.

The period is your subscription's billing month; on Free it is the calendar month (UTC). All workspaces of an account share one allowance.

Check usage

curl https://core.leadveyor.com/v1/usage \
  -H "Authorization: Bearer lv_live_…"
{
  "object": "usage",
  "plan": "pro",
  "periodStart": "2026-11-05T10:00:00.000Z",
  "periodEnd": "2026-12-05T10:00:00.000Z",
  "leads": { "used": 1240, "included": 1000, "percent": 124, "overage": 240, "overageUsd": 28.8, "spendLimitUsd": 129 },
  "nonLeads": { "used": 310, "limit": 10000 },
  "testLeads": { "used": 0, "limit": 100 },
  "evaluations": { "used": 12, "free": 200 },
  "generations": { "used": 1, "limit": 50 },
  "byWorkspace": [{ "workspaceId": "ws_1Bq7Xn4KpRz9Lc2Vt6Hy0Mde", "leads": 1240 }]
}

byWorkspace lets agencies see — and bill — each client's share. With the SDK: await lv.usage.retrieve().

At the limit

Nothing is lost. A message that arrives when the allowance is used up is stored with status: "quota_exceeded" and is not processed. It is processed automatically as soon as there is room again: after an upgrade, after the spending limit is raised, or when the next period starts.

  • Free — processing waits at 50 leads.
  • Paid plans — leads beyond the plan are processed and charged at the plan's price, up to a spending limit per period. The default limit is the plan price (for example, no more than $129 extra on Pro). At the limit, messages wait like on Free. Change the limit in the console under Plan and billing, or with PATCH /v1/billing { "spendLimitUsd": 300 }.
  • Synchronous calls that would exceed the allowance — POST /v1/evaluate, profile generation, creating a workspace beyond the plan — fail with HTTP 402:
{
  "error": {
    "type": "quota_error",
    "code": "quota_exceeded",
    "message": "The Free plan's 50 leads for this period are used up. Upgrade to keep processing.",
    "request_id": "5d1f0c2a-8b7e-4f3a-9c61-2e4b7a9d0f13"
  }
}
CodeWhen
quota_exceededThe period's leads are used up (Free), or test-mode leads are used up.
spend_limit_reachedPaid plan: the spending limit for extra leads is reached.
workspace_limit_reachedCreating a workspace beyond the plan.
generation_limit_reachedThe period's profile generations are used up.

The SDK throws QuotaExceededError for these, and doesn't retry them.

Warnings

At 80% and 100% of the allowance (once per period each), Leadveyor sends a usage.threshold_reached event to every workspace of the account and shows a banner in the console:

{
  "type": "usage.threshold_reached",
  "data": { "object": { "object": "usage_threshold", "threshold": 80, "usage": { "object": "usage", "plan": "starter", "leads": { "used": 240, "included": 300 } } } }
}

Rate limits

API keys are limited per account to the requests per second in the table above. Over the limit the API answers 429 rate_limit_error (rate_limited); wait a moment and retry. The SDK retries 429 automatically.

Changing plans

In the console under Plan and billing (guide), or through the API with an admin key:

  • POST /v1/billing/checkout { "plan": "pro" } — returns a Stripe Checkout url to start a subscription.
  • POST /v1/billing/plan { "plan": "agency" } — upgrades apply right away (the difference for the rest of the month is charged now); downgrades apply from the next period.
  • POST /v1/billing/portal — returns a link to the Stripe portal: card, invoices, cancelling (at the end of the paid period, then the account moves to Free).

See the Billing reference.

Was this page helpful?