Credits & billing

Credit lifecycle

1. First token: 500 free credits are granted once, when you create your very first token.
2. Monthly top-up (free plan): on the 1st of each month at midnight UTC, the free portion of every active free-plan token is reset to 500. Unused free credits don't carry over; purchased credits are untouched.
3. Buying credits: one-off packs are credited as soon as the Stripe payment goes through.
4. Subscription plans: monthly credits are added when Stripe's invoice.payment_succeeded event arrives — not when checkout completes.
5. Token rotation: creating a new token revokes the old one and transfers the existing balance. You don't get a new batch of 500 credits.

Deducted before execution

Credits are deducted before each request runs. If your balance is too low, the request is blocked with HTTP 402 (REST) or an error message in content[0].text (MCP).

Automatic refund

If a request fails after the deduction (database error, timeout, 404), the credits are refunded automatically. Refunded cases:

• Timeout or unexpected SQL error
• GET /v1/transactions/:id — 404 transaction not found
• GET /v1/businesses/:siren — 404 SIRET not found

Low-balance indicator

When your balance drops below 20 credits, a note field appears in _credits:

"_credits": {
  "used": 5,
  "remaining": 12,
  "note": "Low credits! Recharge at normi.fr/dashboard/credits"
}

Strict monthly cap

From the API tokens page, you can set a monthly credit cap on your active key. Unlike a low-balance alert, this cap blocks the call before it runs and before anything is charged. It covers MCP calls, REST calls and Normi Pro report overages that use this key.

• The counter follows UTC calendar months and resets on the 1st at 00:00 UTC.
• The cap can be changed or turned off at any time from the dashboard.
• Token rotation keeps the cap and the current month's usage.
• A request that fails after reservation is refunded and doesn't count towards the cap.

Cost per tool