generated: '2026-07-21'
method: derived
source: openapi/runai-openapi-original.json
docs: https://run-ai-docs.nvidia.com/api/getting-started/about-the-rest-api.md
note: >-
  Derived from the control-plane OpenAPI and documented API conventions. NVIDIA
  Run:ai publishes no dedicated compliance/certification program page at the run.ai
  domain (its security posture now sits under NVIDIA); therefore no Compliance
  pointer is emitted.
standards:
- id: rest
  conforms: true
  evidence: RESTful design, JSON request/response, standard HTTP methods and status codes.
- id: openapi-3.0
  conforms: true
  evidence: Published OpenAPI 3.0.3 document (openapi/runai-openapi-original.json).
- id: oauth2-client-credentials
  conforms: true
  evidence: Token endpoint POST /api/v1/token uses grantType client_credentials; OAuth2Error schema per RFC 6749 Section 5.2.
- id: jwt-bearer
  conforms: true
  evidence: securityScheme bearerAuth type http scheme bearer bearerFormat JWT; Authorization header.
- id: rfc9457-problem-details
  conforms: false
  evidence: Errors use a custom JSON envelope {code, message, details}, not application/problem+json.
- id: offset-limit-pagination
  conforms: true
  evidence: List endpoints expose limit/offset with a next pointer.
- id: oidc
  conforms: false
  evidence: SSO supports OIDC/SAML for user login, but the API itself authenticates via bearer JWT tokens, not OIDC discovery.
- id: fhir
  conforms: false
- id: fapi
  conforms: false
- id: scim
  conforms: false
- id: odata
  conforms: false