Skip to main content
A token is Klipy’s unit of metering. One token pays for one piece of work Klipy delivers on its own, or one unit of something with real cost behind it. You spend a token only at the moment you approve, accept, or trigger that work — never while Klipy is generating a draft, thinking through a plan, or waiting for you to decide.
No create-vs-update distinction, no per-click metering. A charge lands once, at the moment you say yes.

​
From token to result

Each token maps to something concrete you can picture: A delegation run stays at 1 token no matter how much it does inside that run. If an overnight cleanup updates five CRM records, that’s still one token — the writes are absorbed into the flat per-run charge, not billed separately.

​
What never costs a token

  • Klipy generating, drafting, or previewing anything — a suggestion, a message, a delegation plan
  • You rejecting a suggestion, or letting one expire unused
  • Any CRM write you make yourself: creating or updating contacts, companies, deals, todos, notes, or stage changes
  • Composing or rewriting a message yourself with AI’s help, then sending it
  • A sandbox or preview delegation run, or a run that fails
The rule underneath all of this: a charge lands only at a consent moment, at a price you could see before you gave it. Klipy is never billed for its own thinking, and never billed for your labor.

​
Next

What costs tokens

The complete, exact list of every action that does and doesn’t cost tokens.

Plans and limits

How many tokens come with each plan, and what happens if you use more.
Last modified on July 30, 2026