How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

NVIDIA Run:ai Registry API

Use an images registry to enable the listting of repositories and tags that can be used as a data source location for data sets that are relevant to the workload being submitted.

NVIDIA Run:ai Registry API is one of 62 APIs that NVIDIA Run:ai publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Registry. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 7 operations across 4 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version latest.

Requests are made against a single base URL, https://app.run.ai.

7 operations 4 paths 23 schemas 1 DELETE4 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
latest
Base URL
https://app.run.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

NVIDIA Run:ai Registry API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Bearer authentication

Paths & Operations 7

Across 4 paths, the API surfaces 7 operations — 1 DELETE, 4 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Registry 7

Use an images registry to enable the listting of repositories and tags that can be used as a data source location for data sets that are relevant to the workload being submitted.

GET
/api/v1/asset/registries
Get registries
list_registries 1 param → 200401403503
POST
/api/v1/asset/registries
Create a registry asset
create_registry body → 201400401403409503
GET
/api/v1/asset/registries/{AssetId}
Get a registry
get_registry_by_id 1 param → 200401403404503
DELETE
/api/v1/asset/registries/{AssetId}
Delete a registry asset
delete_registry 1 param → 204400401403404503
PUT
/api/v1/asset/registries/{AssetId}
Update a registry asset
update_registry 1 param body → 200400401403409503
GET
/api/v1/asset/registries/{AssetId}/repositories
Get the repositories in the registry
get_repositories 2 params → 200400401403404503
GET
/api/v1/asset/registries/{AssetId}/repositories/tags
Get the repositories tags in the registry
get_repository_tags 3 params → 200400401403404503

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are AssetReadOnlyFields (11 properties), AssetCreationFields (7 properties), WorkloadSupportedTypes (5 properties), RegistrySpec (4 properties). Each schema is shown below with its type and property counts.

RegistryUpdateRequest
object
1 property 2 required
Scope
string
The scope in which an asset can be used. The highest scope, system, is intended for internal purposes only.
RegistryCreationRequest
object
2 properties 2 required
AssetDescription
stringnull
The description of the asset.
AssetUpdatableFields
object
2 properties 1 required
CredentialKind
string
The kind of credential used.
AssetMeta
AssetCreationFields
object
7 properties 1 required
Error
object
3 properties 2 required
AssetReadOnlyFields
object
11 properties 6 required
AssetId
string
Unique identifier of the asset.
AssetName
string
The name of the asset.
AssetCreationRequest
RegistryListResponse
object
1 property 1 required
UpdateCount
integer
the value of an update counter of a data in the system.
Repositories
object
1 property 1 required
AssetKind
string
The kind of the asset.
AssetUpdateRequest
RegistrySpec
object
4 properties 4 required
Registry
object
2 properties 2 required
WorkloadSupportedTypes
objectnull
5 properties
RepositoryTags
object
2 properties 2 required
ClusterIdOptional
stringnull
The id of the cluster.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

runai-registry-api-openapi.yml Raw ↑

Other APIs NVIDIA Run:ai publishes across the network.

NVIDIA Run:ai Access Keys API
NVIDIA Run:ai Access rules API
NVIDIA Run:ai Administrator Command Line Interface API
NVIDIA Run:ai AI Applications API
NVIDIA Run:ai Applications API
NVIDIA Run:ai Clusters API
NVIDIA Run:ai Compute API
NVIDIA Run:ai ConfigMap API
NVIDIA Run:ai Credentials API
NVIDIA Run:ai Departments API
NVIDIA Run:ai Distributed API
NVIDIA Run:ai Distributed Inferences API
Where this information came from

This is an independent, third-party profile of NVIDIA Run:ai Registry API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.