Guides
Inspect evidence
Trace a runtime decision from your app request to Console evidence.
Decision evidence is the proof that Valqio made and recorded a runtime decision for a product request.
Before you run traffic
Make sure your app sends:
- a stable subject key
- a request ID
- an idempotency key
- the generated action key and owning control, or meter being enforced
- quantity
- useful context for support, such as endpoint, workspace, job, model, or feature
Send a request
Call your app endpoint that uses Valqio before product work runs.
Your app response or server logs should include these non-secret identifiers:
- request ID
- idempotency key
- reason code
- reservation ID, for reservation flows
Do not expose API keys or secrets in responses, screenshots, tickets, or support logs.
Open Console
In Console:
- Open Decisions, then select History.
- Search or filter by request ID, subject, action key, or outcome.
- Open the decision detail.
- Confirm the subject, action, quantity, outcome, reason, and usage or billing context.
- Compare the Console evidence with your app logs.
What to verify
| Question | Evidence to look for |
|---|---|
| Did the app call Valqio before work ran? | Request timestamp and app log order. |
| Did Valqio allow or deny? | Decision outcome and reason. |
| Was the right customer checked? | Subject type and key. |
| Was usage counted once? | Idempotency key and usage quantity. |
| Can support explain this later? | Decision detail with request, response, and context. |
Common misses
- The app generated a new idempotency key on retry.
- The API key belongs to the wrong environment.
- The app used a meter key that does not match the published environment.
- Workbench succeeds, but app traffic uses different subject or quantity values.
- The app handles deny as a generic server error instead of a product-specific response.