CUDO Compute API

✓ Official Vendor SpecCloud InfrastructureComputebearer122 EndpointsREST

For Agents

Provision and manage GPU and CPU virtual machines, disks, networks, and object storage on the CUDO Compute cloud. Useful for AI agents that orchestrate ephemeral training, inference, or batch jobs on green compute.

Use for: I want to provision a GPU virtual machine on CUDO Compute, Spin up a temporary VM for a fine-tuning job, List my running CUDO virtual machines, Terminate an idle GPU instance to save cost

Not supported: Does not handle managed databases, container registries, or DNS - use for CUDO Compute virtual machines, disks, networks, and object storage only.

The CUDO Compute API is a REST interface to the CUDO Compute cloud, a sustainable GPU and CPU cloud provider. The API covers the full lifecycle of cloud resources: virtual machines, disks, images, networks, object storage, and clusters, plus the supporting plane of projects, billing accounts, and API keys. Resource-oriented URLs use predictable path patterns, JSON request and response bodies, and standard HTTP verbs and status codes. Authentication is via a bearer token sent in the Authorization header.

Jentic One on Github View OpenAPI Document

Install Jentic One Beta

Connect the CUDO Compute API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CUDO Compute API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcudocompute.com%2Fcudocompute" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcudocompute.com%2Fcudocompute" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with CUDO Compute API.

Provision GPU or CPU virtual machines and start, stop, or terminate them via the /v1/projects/{projectId}/vms operations

Attach, detach, and resize block storage disks for VM workloads

Manage virtual networks and security groups for isolated agent fleets

Create and manage object storage buckets and credentials for model artefacts

GET STARTED

Start building with CUDO Compute API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use CUDO Compute API for, with concrete tasks.

★ On-Demand GPU Provisioning for Training Jobs

An ML training agent can request a GPU virtual machine, run a job, store the resulting checkpoint to CUDO object storage, and terminate the VM, all through the API. Billing-account spend endpoints let the agent abort if the project is over budget. Useful when training jobs are bursty and the team does not want to keep an expensive GPU running between runs.

Call POST /v1/projects/{projectId}/vms with a GPU machine type, run the training script, then DELETE the VM when the run completes.

Multi-Tenant Inference Fleet

A platform that serves AI inference can manage a fleet of CUDO VMs scaled by demand. Use the network and security-group endpoints to isolate tenants, attach object storage for model weights, and rotate API keys per tenant. CUDO's spend reporting lets the platform price inference accurately per customer.

Provision N GPU VMs in a project network, attach the model checkpoint disk, and register them behind the inference router.

Cost-Aware Batch Compute

A research team running nightly batch jobs can have an agent watch the billing-account spend endpoints and decide how many CUDO VMs to launch within the day's budget. Combine /v1/billing-accounts/{billingAccountId}/spend/details with the VM lifecycle endpoints to keep nightly batch runs within a fixed monthly cost.

Call GET /v1/billing-accounts/{billingAccountId}/spend/details, then provision additional VMs only if remaining budget exceeds the cost of one machine-hour.

AI Agent Integration via Jentic

An infrastructure agent can use Jentic to discover the CUDO Compute operations it needs without reading 122 endpoint definitions. Jentic stores the bearer token and exposes operations like 'create a GPU VM' and 'list virtual machines' as semantic tools so the agent picks the right call from natural-language intent.

Use Jentic search for 'provision a GPU virtual machine', load the CUDO Compute /v1/projects/{projectId}/vms create schema, and execute it for the project.

Key Endpoints

122 endpoints — the cudo compute api is a rest interface to the cudo compute cloud, a sustainable gpu and cpu cloud provider.

METHOD

PATH

DESCRIPTION

GET

/v1/api-keys

List API keys

POST

/v1/api-keys

Create an API key

GET

/v1/billing-accounts

List billing accounts

GET

/v1/billing-accounts/{billingAccountId}/spend/details

Get billing account spend details

POST

/v1/billing-accounts/{id}:add-permission

Add a billing account permission

GET

/v1/api-keys

List API keys

POST

/v1/api-keys

Create an API key

GET

/v1/billing-accounts

List billing accounts

GET

/v1/billing-accounts/{billingAccountId}/spend/details

Get billing account spend details

POST

/v1/billing-accounts/{id}:add-permission

Add a billing account permission

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the CUDO Compute API by hand means placing the bearer token in the Authorization header, targeting the rest.compute.cudo.org host, and handling retries across more than a hundred endpoints yourself. Through Jentic you install once, import the CUDO Compute API from the API Directory, store the token once, and your agent calls it.

Permission scoping

CUDO Compute puts the billing account id in the URL path (/billing-accounts/{billingAccountId}/...), so a rule can pin your agent to one billing account: it can read spend details for that account and nothing else. You choose the operations it may call, so ones like adding a permission or creating API keys are not included unless you add them.

Credential isolation

Your CUDO Compute bearer token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'provision a GPU virtual machine' or 'read billing account spend', and Jentic returns the matching CUDO Compute operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using CUDO Compute API through Jentic.

What authentication does the CUDO Compute API use?

CUDO Compute uses a bearer token in the Authorization header. You generate the key in the CUDO Compute console under API keys. Through Jentic the token is held in your encrypted Jentic One instance and never enters the agent's prompt or model output.

Can I provision a GPU virtual machine with the CUDO Compute API?

Yes. POST /v1/projects/{projectId}/vms with a body that selects a GPU machine type, an image, and a region creates a new VM. You can pair this with the disks, networks, and object-storage operations to set up a full training environment.

What are the rate limits for the CUDO Compute API?

The OpenAPI spec does not publish specific rate limits, but CUDO applies sensible per-account throttling on control-plane operations. Batch large fleet provisioning steps and back off on 429 responses.

How do I list my running VMs with the CUDO Compute API through Jentic?

Run pip install jentic, search Jentic for 'list CUDO Compute virtual machines', load the schema for the /v1/projects/{projectId}/vms list operation, and execute it with the project ID. Jentic injects the bearer token from your Jentic One instance so the agent never handles the raw key.

How do I track spend on a CUDO billing account?

Call GET /v1/billing-accounts/{billingAccountId}/spend/details. The response gives a breakdown of usage and cost so a cost-aware agent can decide whether to launch more VMs within the day's budget.

Is the CUDO Compute API free?

The API itself is free to call once you have a CUDO account. Charges come from the underlying compute, storage, and network resources on a usage-based pricing model published in the CUDO Compute console.

Can I limit what my agent is allowed to do with the CUDO Compute API?

Yes. Because you run Jentic One yourself, your own rules decide which CUDO Compute operations and credentials the agent may use. CUDO Compute puts the billing account ID in the URL path, so a rule can pin the agent to a single billing account, letting it read spend details for that account through GET /v1/billing-accounts/{billingAccountId}/spend/details and nothing else. You choose the operations it can call, so sensitive ones like creating API keys via POST /v1/api-keys or adding a billing-account permission stay out of reach unless you explicitly allow them.

CUDO Compute API

Connect the CUDO Compute API to your agent

Capabilities

Start building with CUDO Compute API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs