Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Cloud Infrastructure / CUDO Compute API
CUDO Compute API logo

CUDO Compute API

61
AI ReadinessAI-Aware (B-)61/100
See full scorecard
Official vendor OpenAPI document · agent-readyCloud 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 GithubView 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.

1

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
2

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

Track spend and usage at the billing-account level via /v1/billing-accounts/{billingAccountId}/spend/details

Provision and rotate API keys via /v1/api-keys for credential isolation per agent

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

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

C

CUDO Compute service

- AI-Aware (B-)
61/100
74
Foundational Compliance
63
Developer Experience & Jentic Compatibility
45
AI-Readiness & Agent Experience
78
Agent Usability
50
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

0%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

45

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4
23%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

58%

Summary Coverage

Coverage of summaries across operations/tags/info.

78

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A-Signals: 1
78%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

50

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1
50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

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.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

DigitalOcean API

→

DigitalOcean is an alternative cloud for general-purpose VMs and managed services.

Choose DigitalOcean when the workload is general-purpose CPU and managed databases; choose CUDO Compute when the priority is GPU access and sustainable energy.

Alternative

Linode API

→

Linode (Akamai) provides similar cloud compute primitives at a different price and region mix.

Use Linode for global CPU compute with Akamai's network; use CUDO Compute when you specifically want GPU instances on a green cloud.

Alternative

Paperspace API

→

Paperspace specialises in GPU notebooks and ML workflows, overlapping with CUDO's GPU VMs.

Choose Paperspace for managed ML notebooks and Gradient pipelines; choose CUDO Compute for raw GPU VM provisioning with full network control.

Alternative

Hetzner Cloud API

→

Hetzner Cloud is a low-cost alternative for CPU VMs and storage.

Use Hetzner for inexpensive CPU VMs in Europe; use CUDO Compute when GPUs and global GPU regions are required.

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.

GET STARTED

Start building with CUDO Compute API

Explore with Jentic One
View OpenAPI Document