Simulations

Simulations answer “what would this cost?” before anything reaches a customer. Use them to check a new plan, compare plans, or test a price change against realistic usage.

Estimate a cost

Send a plan and a usage profile, and Orvlin returns the cost computed with the plan’s prices:

curl -s -X POST "$ORVLIN_API/v1/simulator/compute" \
  -H "Authorization: Bearer $ORVLIN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "planId": "01JX_NEW_PLAN",
    "usage": { "api_calls_total": 150000 },
    "period": "monthly"
  }'

Field	Required	Description
`planId`	Yes	The plan to price. Must exist in your workspace.
`usage`	Yes	Quantity per metric, keyed by metric name.
`period`	No	`monthly` or `annual`.

An unknown plan returns 404.

Simulate from the command line

The CLI runs simulations against your pricing manifest, for a customer or subscription over a period:

orvlin simulate --manifest pricing.yaml --customer cust_acme \
  --period-start 2026-10-01 --period-end 2026-10-31 --output table

See the CLI reference for every option, including price overrides for “what if” comparisons.

Typical uses

New product: price a sample of expected customers before launch.
Evolving pricing: compare the current plan with a proposed one at your real usage levels.
Customer conversations: show a customer what the new plan would cost them.

Use simulation before you schedule a price change. Compare the simulated totals with a preview of the migration, and make sure they agree.

Events and metrics

Customers and access

Subscriptions and pricing

Usage alerting

Invoicing

Collections

Revenue reporting

Integrations and data

Tutorials

Simulations

Estimate a cost

Simulate from the command line

Typical uses

​Estimate a cost

​Simulate from the command line

​Typical uses

Estimate a cost

Simulate from the command line

Typical uses