Skip to main content
Pylva separates usage reporting from pricing. Your app reports raw usage. Pylva prices it on the server. Pylva is the usage and cost ledger upstream of billing. Use this page to understand the pricing model. For the operational billing loop, see Billing Workflow.

​
Why server-side pricing

Server-side pricing keeps cost accounting consistent when:
  • Providers change rates.
  • Customers have custom contracts.
  • A non-LLM source needs a custom metric price.
  • Historical events need backfill or reconciliation.

​
Pricing sources

Pylva can price:
  • LLM token usage by provider and model.
  • Non-LLM usage by metric, such as characters, requests, seconds, or executions.
  • Customer-specific pricing versions for billing workflows.

​
Unknown pricing

If Pylva receives usage without a known price, it can accept the event and flag the source for pricing setup. This keeps telemetry flowing while making pricing gaps visible. Unpriced usage is excluded from invoices until pricing is configured, so review unknown pricing before billing customers.

​
Billing handoff

Pylva can create reviewable invoice records from customer usage and pricing. Stripe handles payment collection and hosted invoice delivery after you connect Stripe. Pylva is not a payment processor, tax system, accounting system, collections system, or Stripe replacement.

​
Best practices

  • Review unknown pricing tasks before sending invoices.
  • Keep pricing effective dates explicit.
  • Use stable external customer IDs.
  • Audit pricing changes before billing customers.