Skip to main content
Percify API calls spend the same credits as the app, from your account balance. The REST API has no balance endpoint, so you track spending in three places: the creditsSpent field on every generation, the stats on the developer page at app.percify.io/home/developer, and the check_usage tool of the MCP server, which returns your remaining balance.

Where to see what you spent

Monthly figures count the current calendar month. Used this month and monthCredits leave out failed runs, whose credits were refunded.

Cap what a key can spend

Set a Monthly credit cap when you create a key on the developer page. A run that would take the key past its cap is refused before it is charged:
429 Too Many Requests
The count resets at the start of each calendar month. To change a cap, create a new key with the new cap and revoke the old one.

What happens when credits run out?

A run your balance cannot cover is refused with 400 and nothing is charged. The message starts with Not enough credits, then names the credits the run needs, your current balance and the top-up link https://app.percify.io/billing. Add credits with Top up credits on the developer page or at app.percify.io/billing. Plans, credit packs and billing are explained in Plans and payments.

Check the balance from an agent

MCP clients can ask for the balance directly. A check_usage call returns JSON like this:
monthApiRuns counts runs started with an API key. monthRuns also counts generations started in the Percify app.

Estimate cost

Know a run’s price before it spends.

Authentication

Create keys with a monthly cap.

How credits work

What credits buy across Percify.

Not enough credits

Fix a blocked generation.
Last modified on September 16, 2026