Skip to Content
Referenceoo CLI

oo requests

Model requests and their charges.

Model requests and their charges. These commands call the /api/v1/requests routes; oo api routes --path /api/v1/requests shows their inputs and permissions.

oo requests list

List requests

oo requests list [options]
ArgumentRequiredDefaultChoicesDescription
--query NAME=VALUEno

It also takes the connection options.

oo requests get

Show one by ID

oo requests get [options] id
ArgumentRequiredDefaultChoicesDescription
idyesID from oo requests list
--output OUTPUTnowrite response to a protected file (required for a new credential)
--overwriteno

It also takes the connection options.

oo requests failed

Print the failed model calls as JSON, as the Requests page lists them: each with its time, model, key and who it was for, and its error: its kind, the model proxy's error class and status code, and the first line of its message with secrets hidden when retained. Structured diagnostics include the recorded origin, limiter dimension and measurements, budget, retry-after and retry counters. Missing facts are null; attempted_retries is per model group, not total attempts across fallbacks. The period is this month unless --query gives range (today, current_week or current_month), or from and to (its first and last day), and timeZone; userId, model and keyAlias narrow it, and page and pageSize (25, 50 or 100) page it, as oo api route GET /api/v1/requests/failed lists them. Needs requests.read.

oo requests failed [options]
ArgumentRequiredDefaultChoicesDescription
--query NAME=VALUEnoa period, filter or page input; repeatable

It also takes the connection options.

oo requests content

Print a request's content as JSON, as Show on its page does: the prompt, messages and answer (view), with the receipt of the view (receipt). Content kept as it was opens as it is; content encrypted with the Sunport's own key, the Sunport opens. Every view is recorded before the content is released. You see your own requests' content; an administrator sees others' where the Sunport's privacy settings let administrators view content (oo sunport privacy). Content encrypted with a key the customer holds opens only with that key, on the request's page: the Sunport answers request_log_sunport_key_unavailable when it holds no key of its own, and invalid_disclosure when its key doesn't open the content. Content that wasn't captured or that retention removed answers encrypted_content_unavailable or request_content_not_kept. --output keeps it in a protected file instead. Needs requests.content, as a person: their sign-in or personal key, never an agent's (user_identity_required).

oo requests content [options] REQUEST_ID
ArgumentRequiredDefaultChoicesDescription
REQUEST_IDyesthe request's ID (trace_id in oo requests list)
--output FILEnokeep the content in this protected file instead of printing it
--overwriteno

It also takes the connection options.

On this page