How Cotlet credits will work: one unit, successful calls only

Usage pricing has a bad reputation, and mostly for good reasons: units nobody can predict, no spending limit, and invoices that surprise you at the end of the month. We designed Cotlet’s billing around those complaints.

First, the part that matters today: requesting access is free, and nothing is charged until your access is active.

One unit: credits

Every plan size comes with credits, and credits are the only unit you will ever see. Not tokens, not tasks, not “actions” of different classes.

Each successful API or MCP call uses credits based on the work it takes. The rate is the same for every app. How we talk to an app is our problem, not a line on your bill.

You pay only for calls that work

A call that fails does not cost credits. If an integration breaks, we pause it automatically and refund the credits for failed calls.

Rollover and expiry

• Credits from each monthly payment stay valid for 3 months, so unused credits add up.
• We use the oldest credits first and email you a week before any expire.
• If you cancel, the credits you already paid for keep working until they expire.
• There are no top-ups. Need more? Move to a bigger size at any time, up or down.

A spending cap, on by default

When credits run out, calls pause until your next monthly payment. You will not wake up to an overage bill. If you need more sooner, move to a bigger size.

Why not a flat price per call?

Because a call is not one thing. Reading a list is cheap; a multi-step action in a complex app is not. Metering the real work keeps the price fair across both, and one rate for every app keeps it simple to read.

The plan sizes and the credits each includes are on the pricing page. The common questions are answered in the help center.