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

Crusoe Ccr API

The Ccr API from Crusoe — 8 operation(s) for ccr.

Crusoe Ccr API is one of 111 APIs that Crusoe publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 13 operations across 8 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.cloud.crusoe.ai/v1.

13 operations 8 paths 14 schemas 3 DELETE7 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.cloud.crusoe.ai/v1
Resource Areas
1

Paths & Operations 13

Across 8 paths, the API surfaces 13 operations — 3 DELETE, 7 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Ccr 13
GET
/ccr/supported-locations
Lists the locations where container registry repositories can be hosted.
listSupportedLocations → 200401500
GET
/ccr/supported-providers
Lists the upstream registry providers supported for pull-through-cache repositories.
listSupportedProviders → 200401500
POST
/ccr/tokens
Creates a limited-scope token for authenticating to the container registry and returns it.
createCcrToken body → 200400401500
GET
/projects/{project_id}/ccr/repositories
Lists all container registry repositories in the project and returns their details.
listCcrRepositories 5 params → 200400401403500
POST
/projects/{project_id}/ccr/repositories
Creates a container registry repository in the project and returns the created repository.
createCcrRepository 1 param body → 201400401403500
DELETE
/projects/{project_id}/ccr/repositories/{repository_id}
Deletes a container registry repository from the project.
deleteCcrRepository 3 params → 200400401403500
GET
/projects/{project_id}/ccr/repositories/{repository_id}
Returns details for a single container registry repository in the project.
getCcrRepository 3 params → 200400401403500
PATCH
/projects/{project_id}/ccr/repositories/{repository_id}
Updates the upstream registry credentials for a repository in the project.
updateCcrRepositoryCredentials 2 params body → 204400401403500
DELETE
/projects/{project_id}/ccr/repositories/{repository_id}/images
Deletes an image from a container registry repository in the project.
deleteCcrImage 4 params → 200400401403500
GET
/projects/{project_id}/ccr/repositories/{repository_id}/images
Lists all images in a container registry repository in the project and returns their details.
listCcrImages 7 params → 200400401403500
DELETE
/projects/{project_id}/ccr/repositories/{repository_id}/manifests
Deletes a manifest from an image in a container registry repository in the project.
deleteCcrManifest 6 params → 200400401403500
GET
/projects/{project_id}/ccr/repositories/{repository_id}/manifests
Lists all manifests for an image in a container registry repository in the project and returns their details.
listCcrManifests 9 params → 200400401403500
GET
/projects/{project_id}/ccr/repositories/{repository_id}/usage
Returns usage data for a single container registry repository in the project.
getCcrRepositoryUsage 3 params → 200400401403500

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are Repository (9 properties), RepositoryRequest (5 properties), Manifest (5 properties), CcrImage (5 properties). Each schema is shown below with its type and property counts.

Manifest
object
5 properties
ListSupportedLocationsResponse
object
1 property
ListCcrImagesResponse
object
1 property
CCRTokenResponse
object
1 property
CcrImage
object
5 properties
ListRepositoriesResponse
object
1 property
ListManifestsResponse
object
1 property
CCRTokenRequest
object
2 properties
Repository
object
9 properties
RepositoryRequest
object
5 properties
ListSupportedProvidersResponse
object
1 property
UpstreamRegistryCredentials
object
2 properties
RepositoryQuota
object
3 properties
UpstreamRegistry
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

crusoe-ccr-api-openapi.yml Raw ↑

Other APIs Crusoe publishes across the network.

Crusoe Managed Inference API
Crusoe Cloud MCP Server
Crusoe Audit Logs API
Crusoe AutoCluster Operations API
Crusoe Auto Clusters API
Crusoe Billing API
Crusoe Capacities API
Crusoe Container Registry API
Crusoe Custom Image Operations API
Crusoe Custom Images API
Crusoe Disk Operations API
Crusoe Disks API
Where this information came from

This is an independent, third-party profile of Crusoe Ccr 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.