Features

Usage and Billing

Lezu measures translation work in translation units.

Free To Organize

  • Projects
  • Keys
  • Locales
  • Environments

What Produces Usage

Translation usage is calculated as:

source characters * target languages = translation units

Example:

2,000 source characters * 3 target languages = 6,000 translation units

Estimate Before Translating

POST /v1/translate/estimate
Authorization: ApiKey lez_...
Content-Type: application/json

{
  "sourceLocale": "en",
  "targetLocales": ["nl", "fr", "de"],
  "items": [
    {
      "id": "home.title",
      "text": "Welcome back"
    }
  ]
}

Read Usage and Credits

GET /v1/usage
GET /v1/billing
GET /v1/billing/credits

Billing summaries show the free baseline account state, purchased credits, monthly credit subscription options, usage caps, and usage information for the current account. Lezu does not sell project, key, locale, or environment tiers. Paid usage is added through one-time credit packs or monthly credit subscriptions.

The dashboard usage page visualizes the same server-side usage records by daily translation units, operation/action amount, and recent immutable actions. The displayed amount is translation units, which maps directly to consumed credits.

Usage Caps

Lezu caps infrastructure-heavy work separately from credits:

  • API requests
  • concurrent import, export, release, and translation jobs
  • import file size
  • stored import/export/release artifacts
  • auth and notification emails
  • queue priority

Credits gate AI translation. Usage caps gate infrastructure and abuse.

Buy Credits

Lezu creates PayPal checkout orders for credit packs. After the buyer approves the order in PayPal, the dashboard or client captures the order through Lezu so the API can verify the completed payment and add credits to the account.

Monthly credit subscriptions should use PayPal recurring subscriptions when implemented. They grant credits every billing cycle and can use a lower per-credit price than one-time packs.

POST /v1/billing/checkout-sessions
Authorization: ApiKey lez_...
Content-Type: application/json

{
  "creditPackId": "credits_100k",
  "successUrl": "https://dashboard.lezu.app/billing/success",
  "cancelUrl": "https://dashboard.lezu.app/billing"
}

The response includes a PayPal approval URL:

{
  "id": "paypal_order_id",
  "status": "created",
  "url": "https://www.paypal.com/checkoutnow?token=...",
  "provider": "paypal",
  "creditPackId": "credits_100k"
}

Capture the approved order:

POST /v1/billing/checkout-sessions/:orderId/capture
Authorization: ApiKey lez_...

Captured purchases appear in the billing ledger as credit_purchase rows and increase purchasedCredits, totalCredits, and remainingCredits.

Relevant Endpoints

Method Endpoint Scope
GET /v1/usage usage:read
GET /v1/billing usage:read
GET /v1/billing/credits usage:read
POST /v1/billing/checkout-sessions usage:read
POST /v1/billing/checkout-sessions/:orderId/capture usage:read
POST /v1/translate/estimate translate:read
Features

More Pages