florentin
Start free
ProductBillingCredits & balancesMeteringCheckoutCustomer portalAuth & accountsAPI keys & accessTeams & rolesFeature flagsWebhooks & eventsAnalyticsAI-first / MCPStripe integrationMulti-tenant & white-labelTax & currenciesSecurity & fraudImport & migration
SolutionsAI builders & APIsSaaSTools & automationsAgenciesStartupsEnterpriseMonetize an APIUsage-based billingPrepaid creditsSubscriptions & plansOutsource the portalLaunch a partner program
DevelopersQuickstartProvider docsCustomer docsAPI reference (Scalar)Webhooks & eventsAuth, errors, idempotencyMCP / AI agentStatusChangelog
Pricing
Start freeSign in
Home · Use Cases · Use case
Use case

Monetize an API — bill for access.

Give customers their own keys, count usage and bill it — fixed, per use, or both. Florentin connects API keys, metering and billing into one flow.

Start free →See modules

Selling an API means reliably solving three things: who may access, how much was consumed, and how it gets billed. Each is doable on its own, but together they're error-prone — especially when usage has to be counted idempotently and tied to billing and credits.

Florentin connects exactly these three: customer-owned API keys with permissions, usage recording via /credits/consume, and settlement against prepaid credits or a plan. Plus signed webhooks so your app always knows. Payments run through your Stripe integration.

Sound familiar

You don't want to build this yourself.

Selling an API means controlling access, measuring usage and billing cleanly. Florentin connects API keys, metering and billing into one flow.

  • Issue keys with permissions and revoke instantly
  • Record usage idempotently, without double-counting
  • Combine a fixed fee and usage-based billing
How Florentin helps

Monetize an API

✓
Keys & accessPer customer, with permissions, shown once.
✓
Count usageamount + reason via /credits/consume, idempotent.
✓
Bill cleanlyAgainst prepaid balance or a plan, in real time.
✓
Get eventsSigned webhooks for invoices, subscriptions and more.
Matching modules

What's inside

01API keys & accessKeys, scopes, limits — under control.→02MeteringCount what counts — and bill it.→03Credits & balancesPrepaid balances that draw down as they're used.→04BillingEvery billing model — handled cleanly.→05Webhooks & eventsFlorentin events into any tool or automation.→
How it works

In three steps

Issue a key

Per customer, with the permissions you want.

Record usage

Per call via the credits API, idempotent.

Bill

Balance drops, plan settles, invoice via Stripe.

Build it yourself?

What Florentin saves you

Without Florentin

  • ✗ Build key management and hashing yourself
  • ✗ Estimate usage from logs
  • ✗ Risk double-counting from retries
  • ✗ Build your own event delivery with retries

With Florentin

  • + Keys with scopes, preview and revoke out of the box
  • + Exact recording via the credits API
  • + request_id prevents double-counting
  • + Signed webhooks with retries and logs
FAQ

Frequently asked

How do I prevent double-counting on retries?
Via the request_id on /credits/consume — repeated events are detected and not recorded again.
Can I send events to other tools?
Yes — signed webhooks (e.g. invoice.created) route events to your tools and automations (n8n, Make, Zapier) or a custom endpoint. Your app itself reads via the API anyway.
Can I mix fixed and usage-based?
Yes — a base fee plus usage-based billing is possible as a hybrid model.
How do customers issue their keys?
In the white-label customer portal, customers create and rotate their API keys themselves.
Related

Read on

01Earn from your model→02Usage-based billing→03API keys & access→

Build your product. We'll handle the rest.

Accounts, billing, credits, portal, access — integrated. Stripe fully included.

Start free →