Checks_ListReferenceRanges
const url = 'https://dev-api.qualiastudios.dev/v1/accounts/example/checks/example/referenceRanges';const options = {method: 'GET', headers: {'X-API-Key': '<X-API-Key>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://dev-api.qualiastudios.dev/v1/accounts/example/checks/example/referenceRanges \ --header 'X-API-Key: <X-API-Key>'Lists a check’s reference ranges. The check may be - to list every
check’s.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The account id.
The check id.
Query Parameters
Section titled “Query Parameters ”At most this many; 0 means 100, the maximum is 1000.
From a previous response’s next_page_token.
AIP-160 filter. Fields: interface_hash, robot, metric.
Responses
Section titled “ Responses ”OK
Response for Checks.ListReferenceRanges.
object
One page of ranges.
A robot’s reference range for one metric (QUA-2233): the quantiles of its
own episodes, so each episode is checked against its own robot’s takes and
checks stay meaningful across mixed rigs. The population is every KEPT or
UNREVIEWED episode of the workspace on the same robot interface, and a
workspace lists and reads only its own ranges (QUA-2933). The episode
rules’ configuration: only checks/episode-rules has them.
Served by qds-api.
object
Accounts/{account}/checks/{check}/referenceRanges/{reference_range}
The robot interface hash b3:<hex> the population shares.
Accounts/{account}/robots/{robot} when the population is narrowed to one fleet robot; empty for the whole interface.
The metric, as an Episode.Metrics field name.
P05, p10, p25, p50, p75, p90, p95, p99.
Median absolute deviation.
The lower fence the checks use.
The upper fence the checks use.
Episodes in the population.
When it was computed.
Human-confirmed bounds. Each side is independent; calibration preserves them.
Independently confirmed upper bound.
Who confirmed the bounds and when. Absent after clearing them. (— api-linter: core::0140::prepositions=disabled aip.dev/not-precedent: matches the stored confirmation contract. —)
object
What kind of actor it is.
The person’s user id when kind is PERSON; empty otherwise.
The person’s display name at the time, for rendering without a lookup.
The rule code, or the model id (e.g. “gemini-robotics-er”), when not a person.
The run a model or rule finding came from, when it has one.
The API key’s id when a person acted through one; empty for a session. Never the key itself.
Signed identity evidence recorded with the change, kept apart from the principal above. Unset on older records and wherever none was signed.
object
How the principal authenticated.
The user id of a person verified as starting the work: the person of a session, or the person a trusted service’s signed job record names. Empty when nobody was verified.
The initiator’s display name at the time, never their email.
The user id of the key’s creator at the time. Not who used the key.
Who owned the key at the time.
The owning space’s id (a workspace or the organization) when
credential_owner is SPACE.
When the bounds were confirmed. (— api-linter: core::0142::time-field-names=disabled aip.dev/not-precedent: matches the stored confirmation contract. —) (— api-linter: core::0140::prepositions=disabled aip.dev/not-precedent: matches the stored confirmation contract. —)
Empty on the last page.
Example
{ "referenceRanges": [ { "confirmedBy": { "kind": "KIND_UNSPECIFIED", "attribution": { "authentication": "AUTHENTICATION_UNSPECIFIED", "credentialOwner": "CREDENTIAL_OWNER_UNSPECIFIED" } } } ]}default
Section titled “default ”Default error response
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.
object
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
object
The type of the serialized message.
Example generated
{ "code": 1, "message": "example", "details": [ { "@type": "example" } ]}