Skip to main content
Usage Caps stop activity at a configured meter threshold. Agents should set caps before load tests, media uploads, queue fan-out, and paid usage.

​
Cap-setting workflow

1

Find the meter and plan fields

tovuk pricing --json
tovuk deploy --dry-run --json
Use products[].meter_details, products[].limit_fields, and dry-run meterPlan entries to pick the meter, period, and cap command before traffic depends on a paid capability.
2

Set caps before traffic

tovuk limits set worker_requests --period day --value 100000 --notify-at-percent 80 --json
tovuk limits set object_storage_egress_bytes --period month --value 1000000000000 --notify-at-percent 80 --json
Pass --notify-at-percent <1-100> to choose when Tovuk warns before a hard stop. If the flag is omitted, the CLI uses 80 percent.
3

Watch usage during tests

tovuk usage --json
Compare current usage, configured caps, and billingEstimate.lineItems before load tests, backfills, and media imports continue.
4

Open billing deliberately

tovuk billing checkout --json
tovuk billing portal
Show the hosted checkout URL only when a human chooses higher paid capacity. Use the billing portal for invoices, payment methods, and subscription changes.
5

Remove stale caps

tovuk limits delete worker_requests --period day --json
Delete a cap only after confirming replacement limits or accepted paid capacity.

​
Dashboard

The dashboard Usage view is available at https://tovuk.com/account/usage or https://tovuk.com/<handle>/usage. It includes the same hard-cap action as tovuk limits set and the same removal action as tovuk limits delete, backed by the same API routes and rate limits as the CLI. It shows copyable tovuk limits set commands with --notify-at-percent and copyable tovuk limits delete commands for the selected meter. It also opens the same hosted checkout flow as tovuk billing checkout --json for upgrades and the same hosted billing portal flow as tovuk billing portal for invoices, payment methods, and subscription changes.

​
Agent commands

tovuk usage --json
tovuk limits set worker_requests --period day --value 100000 --notify-at-percent 80 --json
tovuk limits set worker_cpu_ms --period day --value 1000000 --notify-at-percent 80 --json
tovuk limits set object_storage_egress_bytes --period month --value 1000000000000 --notify-at-percent 80 --json
tovuk limits delete worker_requests --period day --json

​
API

  • GET /v1/usage
  • PUT /v1/usage/caps/{metric}
  • DELETE /v1/usage/caps/{metric}/{period}

​
Meters

Usage Caps support these public meters:
  • worker_requests
  • worker_cpu_ms
  • worker_transfer_bytes
  • static_transfer_bytes
  • sqlite_rows_read
  • sqlite_rows_written
  • sqlite_storage_bytes
  • kv_reads
  • kv_writes
  • kv_deletes
  • kv_lists
  • kv_storage_bytes
  • queue_operations
  • state_requests
  • state_duration_gb_milliseconds
  • state_sqlite_rows_read
  • state_sqlite_rows_written
  • state_sqlite_storage_bytes
  • object_storage_bytes
  • object_storage_class_a_operations
  • object_storage_class_b_operations
  • object_storage_egress_bytes
  • build_minutes
  • log_events
Last modified on June 3, 2026