Where to look
| Role or purpose | Scope and access permissions |
|---|---|
| Personal requests and charges | Provisioned usage and billing view: inspect requests and charges accessible to your current account. |
| Organization administrators | Provisioned organization view: review authorized member usage and distinguish organization totals from member spending. |
| Platform management logs | Internal administration view: restricted to authorized platform administrators; customer accounts cannot view site-wide data. |
What request records contain
- Subject to page permissions and recorded fields, inspect timestamps, models, token breakdowns, actual CNY charges, request IDs and outcomes. Charges are associated with the pricing rules applicable when the request started.
- Authorized views may show source IP, User-Agent and entry route. uk-api, jp-api and hk-api identify entry routes, which differ from the selected upstream supply channel and do not prove inference location.
- NAT, proxies and network conditions can affect IP addresses, and clients can set User-Agent. These are diagnostic signals rather than verified identity or device evidence. Missing historical fields cannot be reconstructed without evidence.
Management audit and body archives
Management operations integrated with the audit mechanism generate audit events. Request-archive configuration, reading, export and deletion have corresponding records. Management audit differs from model billing and does not imply a complete trail for every page click.
Ordinary usage logs are not full prompt archives. Request-body archiving has its own per-account policy and permissions and can retain request content when enabled. Web conversations, canvas data, operational access logs and formal backups have separate handling rules.
Troubleshoot by request ID
- Capture the X-Oneapi-Request-Id response header, timestamp with timezone, domain, model and HTTP status. For streaming failures, also keep the final received event.
- Filter authorized records by time, model and request ID. For 429 responses, inspect rule, scope, limit, window_seconds, retry_after and Retry-After to distinguish key, account, organization or upstream limits.
- Send support a redacted error description and request ID. Exclude full keys, authorization headers, passwords and unrelated user input. Treat exported logs as sensitive business material.
Related rules are set out in the DAYWORLD Terms of Service, Privacy Policy, and Data Processing Information. For clarification or enterprise documentation, contact the operator via the Contact page.