Meter the unit that matters
Count API requests or token-oriented usage for model and content services.
API metering and quotas
Meter backend usage and enforce plan limits.
Measure requests or tokens, attach users to plans, and stop usage at the configured quota—without building the accounting path around every endpoint.
- Requests
- Tokens
- Plan quotas
Productize access
Know what was used and when to say no.
Daptin records usage against configured meters and plan membership. Quota enforcement is the admission boundary; optional credit hooks run after metering when the product also maintains a credit balance.
Attach limits to plans
Define plan allowances and associate members with the commercial tier they use.
Enforce before more work is admitted
Quota checks deny requests once configured usage has been exhausted.
Add product-specific credits
Post-metering hooks can connect successful usage to the application’s own balance or ledger behavior.
Commercial uses
Express the promise behind each plan.
Free and paid tiers
Give trial users a useful allowance and reserve higher limits for members of paid plans.
Internal service budgets
Put explicit consumption boundaries around teams or applications sharing one backend.
AI products
Account for token-oriented work where one request may cost far more than another.
Credit-backed products
Connect recorded usage to an application-owned ledger when plans alone are not the whole commercial model.
Separate controls
Metering answers a product question, not a traffic question.
Plan quota decides whether an identified member still has entitlement to a measured capability. URL rate limiting instead constrains request frequency by client IP and exact path. A serious deployment may use both, but they solve different problems.
Quota enforcement happens before admitting more measured work. Credit hooks happen after metering and are an extension point—not a substitute for the hard quota.