Credits

A credit pays for one item we find for you: a post, a reaction, a comment, a profile visit or a new follower. A trial includes 3,000 credits.

What a credit buys

Every item costs 1 credit the first time your workspace sees it, wherever it came from: your own team’s posts, a competitor, an influencer, or the extension. Whether the person behind it fits your ideal client does not matter: we have to fetch it to know. Only the people who fit land on your lists.

Item	Credits
A post by your team or a followed source	1 per post
A reaction or a comment on one of those posts	1 each
A profile visit from the extension	1 per visitor per day
A new follower from the extension	1 per follower
A new connection	Free
Fetching something you already have again	Free
Reshares, ads, events, newsletters and articles	Free
Reading anything: people, companies, posts, insights	Free
`rescore`	Free
Work email of a Lead (coming soon)	5 per verified email, on request
Phone number (coming soon)	25 per number found, on request

One person who reacts to three posts is three credits. Someone who unfollows you and follows you again is a new follower. Posts and engagement that another workspace already fetched still cost a credit in this one. Contact details are only looked up for Leads. A person who is not a Lead is skipped and costs nothing.

Your colleagues

Your colleagues themselves never cost a credit: when they like, comment, visit or follow, they do not show up in your list. Your team’s posts, and everyone who engages with them, cost a credit like any other.

When the credit is taken

The credit is taken when the item is fetched, not after the person’s profile is enriched. Spent credits are not refunded: not when enrichment fails, and not when someone takes back a like.When you add a source you choose how much history it fetches: none, the last 7 days or the last 30 days. The estimate counts the posts and their reactions and comments for each option, then the monthly rate.

How many leads that is

That depends on the quality of your sources. We see anywhere from 7% to 35% of the people we find match your ideal client. You see the match rate in the app as well.

Setup

Setup finds your first people. It uses up to 1,500 of the 3,000 trial credits, so your trial never starts empty.

Plans

Two plans, billed monthly in USD. The bundle is credits per month.

Plan	Price per month	Credits per month	Users
Solo	$49	3,000	1
Team	$99	10,000	Unlimited
Team	$179	20,000	Unlimited
Team	$329	40,000	Unlimited
Team	$449	60,000	Unlimited
Team	$699	100,000	Unlimited

Above 100,000 credits a month, talk to us. Solo includes Slack, the email digest, CSV export and MCP. Every Team step adds API keys, webhooks and CRM sync. Neither plan caps the number of sources. Installing the Chrome extension does not count as a user.

Trial

A trial runs 7 days with 3,000 credits, on Solo and on every Team step. A card is needed to start it. What setup used comes out of these. Trial credits lapse when the trial ends. When you convert, what is left of the trial credits lapses and the first monthly bundle replaces it. Trial credits used up early: finding new posts and people pauses until you start the plan.

Balance and reset

The bundle resets on your billing date. Unused credits do not roll over, and there are no top-ups. Read the balance with GET /v1/credits or the MCP tool get_account. Everyone in the workspace can see it.

{
  "data": {
    "has_credits": true,
    "balance": 1455,
    "reserved": 35,
    "bundle": 3000,
    "used_this_period": 1510,
    "credits_used": {
      "posts": 60,
      "engagements": 1210,
      "relationships": 220,
      "contacts": 20
    },
    "leads_this_period": 95,
    "period_start": "2026-10-01T00:00:00.000Z",
    "period_end": "2026-11-01T00:00:00.000Z"
  }
}

What each field means

balance is what is left right now. It can go below zero, see below.reserved is held by work that is queued or running, and already left out of balance.bundle is the monthly bundle of the plan.period_end is when the bundle resets.credits_used splits what this period cost: posts, engagements (reactions and comments), relationships (profile visits and new followers) and contacts (work emails). leads_this_period is how many different people behind those engagements and relationships are a Lead now. It follows your ideal client, so it can change when you edit it. What was charged does not.has_credits is false on a plan that does not run on credits. Every number is then null.

Alerts

At 20% of the bundle left, and again at zero, the owner and admins get a notice in the app and by email. Each alert goes out once per billing period.

When credits run out

Finding new posts and people pauses, on every source and your own team alike. Nothing is deleted.

Nothing new is fetched, enriched or added, and the extension adds no new people.
Everything you already have stays available: leads, lists, exports and syncs.
When the credits come back, finding resumes from that moment. The paused days are not fetched afterwards.

A run that started when the balance was still positive finishes. The balance may then go below zero, and the shortfall comes off the next bundle. When the last payment failed, everything keeps running while the payment is retried. Update your card before the retries run out, or the subscription ends.

Changing plans

Only an owner or admin can change the plan.

Change	When it applies
Solo to any Team step	Immediately
A higher Team step	Immediately, and the extra credits are added right away
A lower Team step	At the next renewal
Team to Solo	At the next renewal, once the workspace has 1 user left

Cancelling keeps the bundle usable until the end of the period.

In the API and MCP

Nothing that costs credits happens without an explicit confirmation.

Ask

Add a source, your own team included, with POST /v1/sources, and optionally history_days (0, 7 or 30, default 7). Without confirm, nothing is added. The answer is a 200 with needs_confirmation, the estimate and the balance.

Show the estimate

Put message or the estimate to the user. first_month includes the chosen history; options gives the first month for each history choice.

Confirm

Once the user agreed, send the same request with confirm: true and the chosen history_days. With a balance of 0 or less the answer is a 402 insufficient_credits.

{
  "needs_confirmation": true,
  "estimate": {
    "history_days": 7,
    "first_month": 222,
    "monthly": 180,
    "options": [
      { "history_days": 0, "first_month": 180 },
      { "history_days": 7, "first_month": 222 },
      { "history_days": 30, "first_month": 360 }
    ]
  },
  "balance": 1420,
  "message": "Adding this source with the last 7 days costs about 222 credits in the first month, then about 180 a month (no history: 180, 7 days: 222, 30 days: 360). Call again with `confirm: true` and the chosen `history_days` once the user agreed."
}

The numbers in estimate are null when no recent posts of the source are known. A source with source_kind: team asks for confirmation like any other. Over MCP, save_source asks the same way but confirms with a confirm_id instead of confirm: true, and states the most it may spend as a ceiling. See Confirmation. See Errors for insufficient_credits.

Get started

Use with Claude

Use the API

Integrations

Webhooks

Changelog

What a credit buys

Plans

Trial

Balance and reset

Alerts

When credits run out

Changing plans

In the API and MCP

​What a credit buys

​Plans

​Trial

​Balance and reset

​Alerts

​When credits run out

​Changing plans

​In the API and MCP

What a credit buys

Plans

Trial

Balance and reset

Alerts

When credits run out

Changing plans

In the API and MCP