Logs, usage, and credit

Sign into the Divyam console with the account that created your application’s key. Note your test’s request time and requested model before opening the reporting pages.

Find a request in Logs

1. Select Logs in the left navigation.
2. Set Model to the requested catalog ID, or choose all models while investigating missing requests.
3. Set Period to include the test: Last 24 hours, Last 7 days, or Last 30 days.
4. Leave Status at All statuses to include failures.
5. Find requests matching your test time. The newest requests appear first, with timestamps in UTC.
6. Check the model, endpoint, status, token counts, and latency. Successful requests have a 2xx status.
7. Select View request or View response when those controls are available.
8. Use Load older requests if your test is beyond the loaded rows.

The status filter applies to loaded requests. No matching rows does not prove that no matching request occurred. Continue loading older requests within the selected period when investigating earlier traffic.

Content can be Not recorded. A streamed answer can show Streamed; not stored. Check the answer in your application when the console cannot display it. For tool workflows, inspect recorded continuation requests for the assistant tool call and matching tool result.

Logs show the requested catalog model. They do not identify the backing model for each individual request.

Review Usage

1. Select Usage.
2. Choose the requested model and a period covering your tests.
3. Check Requests, Total tokens, Success rate, and Spend.
4. Change the chart between Requests, Tokens, and Spend.
5. Use By model when available to compare requested models.
6. Review By requested model for the per-model totals.

Reporting can take a few minutes to catch up after a request. Compare the same account, model, and period before investigating differences.

Requested against routed

This view groups requested catalog models against recorded backing models. Select Show the flows for the corresponding table of request counts and shares. The routing view includes failed requests. It is an aggregate view for the selected period.

If the page reports that routed models were not recorded, it cannot identify them for that period. Do not infer the backing model from the completion’s model field.

Check Credits & Billing

1. Select Credits & Billing.
2. Check the currency, remaining credit, Granted, and Spent values.
3. Review the balance after reporting has caught up with your tests.

The current release displays the credit balance. Credit purchases, payment methods, plan changes, payments, and spend-cap controls are marked as forthcoming. If credit runs out, ask your Divyam administrator about continuing the evaluation.

Use Troubleshooting if requests fail or reporting remains missing.