Valqio docs

Valqio is runtime monetization infrastructure for software teams that need product code to make pricing-aware decisions before costly or billable work starts.

Call Valqio before the billable action. Your app sends the customer, product action, quantity, request identity, and relevant context. Valqio returns a runtime decision, records the evidence, and keeps the usage transaction lifecycle separate from your payment provider.

What Valqio handles

• Count and aggregate usage with counter, identity-set, and gauge meters.
• Capture product events and return read-only usage summaries.
• Decide whether a product action should run.
• Evaluate plan rules, credits, quotas, reservations, customer terms, and usage windows.
• Reserve value before work starts, then commit or release it after the work finishes.
• Acquire and release temporary capacity for concurrent work.
• Make retries and repeated requests idempotent.
• Record evidence that support, finance, customer success, and engineering can inspect later.

What Valqio does not replace

Billing systems invoice, collect payment, and manage commercial records. Feature flag systems toggle access paths. Metering alone counts and aggregates usage.

Valqio provides first-class metering and usage summaries, then adds managed runtime enforcement: pre-action decisions, credits, quotas, reservations, idempotency, settlement, concurrency, and evidence. Billing sends invoices. Valqio decides whether the product action should run.

Public integration surface

Valqio is a hosted paid service. Public developers should need only:

• the hosted Valqio Console
• the hosted runtime data plane URL from Console
• a server runtime API key
• the SDK package they install from npm
• the product actions, meters, limits, credits, and plans they model in Console
• decision evidence after their app calls Valqio

The npm SDK is sufficient for integration. SDK source links, if Valqio publishes them, are optional inspection material.

Start here

1. Read the quickstart.
2. Review the hosted setup.
3. Learn how Valqio works.
4. Scan the Console feature map.
5. Understand runtime decisions.
6. Wire the Node SDK.
7. Choose the right metering, usage, event, or concurrency operation.
8. Check feature and parameter access.
9. Handle denials, retries, and reservations.
10. Follow the end-to-end generated client guide.
11. Publish runtime state.
12. Test in Workbench.
13. Inspect decision evidence.