Skip to main content
Klipy only charges a token when it delivers a result you accept, or when it spends real money on your behalf — transcribing a meeting, pulling enrichment data. Reading your inbox, drafting follow-ups, surfacing to-dos, and cleaning up your CRM in the background all day is never billed; working alongside Klipy is always free.
No charge ever lands without a moment where you say yes, at a price you can see before you say it. Reject a draft, ignore a suggestion, or let it expire, and it costs nothing.

Why do other pricing models charge you for the wrong thing?

Usage pricing has a bad reputation, and it earned it. The problem is what other models put the meter on. The unexpected part: Klipy does not charge for the AI thinking, for the AI drafting, or for your own typing. It charges at the instant a result crosses from proposed to accepted — and not a moment before.

What exactly is one token in Klipy?

Tokens are legible because each one maps to something you can point at.

1 token

One CRM suggestion you accept — a new contact, a stage change, a logged deal.

2 tokens

One follow-up email you approved and sent.

10 tokens

One hour of a meeting transcribed by the notetaker.

0.5 tokens

One company enriched with fresh firmographic data.
An entire overnight delegation — Klipy working autonomously to clean your pipeline and write five records — is a flat 1 token for the run, no matter how many records it touches. Your own work never counts: creating or updating any CRM record by hand, rewriting a message with AI in the composer, and editing over the API are all free.
There is no create-versus-update distinction and no per-write metering inside an autonomous run. Cheap mechanical writes are free; you pay for the delivered result, once.

When does Klipy actually charge a token?

Every token is spent at a consent point you control:
  • You see the price before you commit. The cost is visible at the accept button, not discovered on an invoice.
  • Rejected and preview work is free. Generating a draft, previewing it, or running a delegation in sandbox mode charges nothing. A run that fails charges nothing.
  • Overage is off by default. If you use up your included tokens, Klipy pauses new work instead of billing you further — nothing bills past your allotment unless you’ve opted in to pay-per-use.
This is why the incentive stays aligned with yours: Klipy only earns when it produces work good enough for you to keep.

How does Klipy avoid a surprise invoice?

The dread with usage pricing is the surprise bill — the death-by-a-thousand-cuts drip of micro-charges you can’t count until the statement arrives. Klipy removes it three ways: no charge without your yes, a default that pauses your account at zero instead of billing past it, and one legible line per autonomous run instead of a stream of tiny charges. Pay-per-use overage exists as an opt-in at a flat $0.10 per token, for accounts that ask for it — off by default for everyone else.
A Tuesday morning. Your weekly pipeline cleanup ran overnight. You wake up to five records updated, three stale deals flagged, and two follow-ups drafted and waiting for your review. The meter shows one line: 1 token. You gave consent once, when you set the delegation up. The work is done, and the bill is exactly what you could have predicted — to the token.

What does Klipy charge for, honestly?

Klipy is not “free to use.” It charges for two things, deliberately:
  1. Results the agent delivers on its own — an accepted suggestion, an approved send, a completed delegation run.
  2. Actions with real marginal cost — meeting transcription and company enrichment, where Klipy pays a provider.
Everything in between — the drafting, the reading, the mechanical CRM writes, and every minute you spend working alongside the agent — is free.

What costs tokens

The exact table: what’s charged, what’s free, and how many tokens each action costs.

What is a token

The unit defined, with human-scale examples.

Plans and limits

Included tokens per seat, and what happens if you use them all.

Managing usage

See your usage, get alerts, and know what happens at zero.
Last modified on July 30, 2026