Install Jentic One Beta

Connect the Crusoe Cloud API Gateway to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Crusoe Cloud API Gateway, 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%2Fcrusoecloud.com%2Fcrusoecloud" | 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%2Fcrusoecloud.com%2Fcrusoecloud" | 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 Crusoe Cloud API Gateway API.

Provision GPU and CPU VM instances individually or in bulk under a project

Manage instance groups and instance templates for repeatable VM topologies

Create and resize persistent disks, attach and detach them from VMs

Configure VPC networks, subnets, and firewall rules per project

Set up Infiniband networks and partitions for high-bandwidth GPU clusters

GET STARTED

Start building with Crusoe Cloud API Gateway API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Crusoe Cloud API Gateway API for, with concrete tasks.

★ GPU Training Cluster Provisioning

Spin up a multi-node GPU training cluster by bulk-creating VM instances, attaching shared disks, and connecting them to an Infiniband partition for high-bandwidth interconnect. Crusoe Cloud exposes Infiniband as a first-class resource, which most general-purpose IaaS APIs do not.

POST /projects/{project_id}/networking/ib-partitions to create the partition, then POST /projects/{project_id}/compute/vms/bulk-instances with eight VMs referencing that partition.

Cost-Aware Inference Fleet

Manage an inference fleet that scales up during the day and down overnight by combining instance-groups for fleet topology with PATCH calls to change VM state. Pull /organizations/usage to verify cost trends after each scaling cycle.

PATCH /projects/{project_id}/compute/instance-groups/{instance_group_id} to resize the group at 8am, reverse the change at 8pm, and read /organizations/usage to confirm spend.

Per-Project VPC Hardening

Keep each Crusoe Cloud project's network surface tight by listing VPC firewall rules, removing unused entries, and patching the remainder to use up-to-date CIDRs. Useful for ongoing security hygiene as engineering teams roll on and off projects.

GET /projects/{project_id}/networking/vpc-firewall-rules, identify rules with overly broad source ranges, and PATCH each to a tighter CIDR.

Image and Template Catalog Sync

Mirror Crusoe Cloud's available VM images and instance templates into an internal catalog so platform teams can decide which images are blessed for production use. Updates are detected by diffing the listing endpoints on a schedule.

GET /compute/images and GET /projects/{project_id}/compute/instance-templates, diff against the cached catalog, and surface any new images or templates for review.

Agent-Driven GPU Operations

Allow an AI ops agent to handle GPU infrastructure chores - provisioning, attaching disks, opening firewall rules - through Jentic so the Crusoe access token stays in the vault and only scoped requests reach the runtime.

Search Jentic for 'provision a GPU virtual machine', load the create-VM operation, and execute it with the chosen VM type and project ID.

Key Endpoints

95 endpoints — the crusoe cloud api gateway exposes 95 endpoints covering the full crusoe cloud product surface: vm instances and instance groups, vm templates, vm types, instance images, persistent disks, snapshots, vpc networks, subnets, firewall rules, infiniband networks and partitions, load balancers, organisations, projects, usage and billing, identities, ssh keys, tokens, and capacity lookups.

METHOD

PATH

DESCRIPTION

POST

/projects/{project_id}/compute/vms/instances

Create a VM instance

POST

/projects/{project_id}/compute/vms/bulk-instances

Bulk create VM instances

POST

/projects/{project_id}/storage/disks

Create a persistent disk

POST

/projects/{project_id}/networking/vpc-firewall-rules

Create a VPC firewall rule

POST

/projects/{project_id}/networking/ib-partitions

Create an Infiniband partition

POST

/projects/{project_id}/networking/load-balancers

Create a load balancer

GET

/organizations/usage

Read project-level usage

GET

/locations

List available Crusoe Cloud locations

POST

/projects/{project_id}/compute/vms/instances

Create a VM instance

POST

/projects/{project_id}/compute/vms/bulk-instances

Bulk create VM instances

POST

/projects/{project_id}/storage/disks

Create a persistent disk

POST

/projects/{project_id}/networking/vpc-firewall-rules

Create a VPC firewall rule

POST

/projects/{project_id}/networking/ib-partitions

Create an Infiniband partition

POST

/projects/{project_id}/networking/load-balancers

Create a load balancer

GET

/organizations/usage

Read project-level usage

GET

Why Jentic?

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

Setup

Wiring the Crusoe Cloud API Gateway by hand means setting its token-based Authorization header and threading VM, disk, firewall-rule, and load-balancer provisioning calls across projects yourself. Through Jentic you install once, import the Crusoe Cloud API Gateway from the API Directory, store the token once, and your agent calls it.

Permission scoping

Crusoe Cloud puts the project id in the URL path (/projects/{project_id}/compute/vms/instances), so a rule can pin your agent to one project: it can provision instances, disks, and networking there and nothing else. You choose the operations it may call, so bulk instance creation or firewall-rule changes are not included unless you add them.

Credential isolation

Your Crusoe Cloud 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 'create a storage disk', and Jentic returns the matching Crusoe Cloud operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Crusoe Cloud API Gateway API through Jentic.

What authentication does the Crusoe Cloud API Gateway use?

The OpenAPI specification does not declare a security scheme. In practice Crusoe Cloud uses an API access token issued from the Crusoe console - pass it in the Authorization header. Through Jentic the token is stored encrypted in the vault and never enters the agent prompt.

Can I provision a GPU VM with the Crusoe Cloud API?

Yes. POST /projects/{project_id}/compute/vms/instances creates a new VM in the target project. Use POST /projects/{project_id}/compute/vms/bulk-instances when you need many VMs at once, for example to spin up a training cluster.

How do I set up an Infiniband partition for a GPU cluster through the Crusoe Cloud API?

First GET /projects/{project_id}/networking/ib-networks to find an existing Infiniband network, then POST /projects/{project_id}/networking/ib-partitions to create a partition that VMs in the cluster can join.

How do I track an async VM creation operation?

VM creation returns an operation_id. Poll GET /projects/{project_id}/compute/vms/instances/operations/{operation_id} until the operation reaches a terminal state, then call GET /projects/{project_id}/compute/vms/instances/{vm_id} for the running VM.

What are the rate limits for the Crusoe Cloud API?

The OpenAPI specification does not document numeric rate limits. Watch for HTTP 429 responses and contact Crusoe Cloud support before running high-frequency provisioning loops.

How do I provision a GPU VM through Jentic?

Run pip install jentic, search 'provision a GPU virtual machine', load the create-VM operation, and execute it with your project_id and VM type. Jentic injects the Crusoe access token automatically.

Can I limit what my agent is allowed to do with the Crusoe Cloud API?

Yes. Because you run Jentic One yourself, your own rules decide which Crusoe Cloud operations and credentials the agent may use. Crusoe Cloud puts the project id in the URL path, such as /projects/{project_id}/compute/vms/instances, so you can pin the agent to a single project and let it create VMs, disks, and networking there and nothing else. You pick the exact operations it may call, so higher-impact actions like bulk instance creation via /projects/{project_id}/compute/vms/bulk-instances or firewall-rule changes stay off unless you add them.

Crusoe Cloud API Gateway

AI ReadinessFoundational (D)44/100

See full scorecard

Community OpenAPI document · agent-readyCloud InfrastructureComputeapiKey95 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Provision and manage GPU and CPU VMs, networking, storage, and projects on Crusoe Cloud's GPU-focused IaaS platform.

Use for: Provision a new GPU VM instance in a Crusoe Cloud project, Bulk create 8 H100 instances under project proj_abc, List every Crusoe Cloud location available for resource hosting, Attach a persistent disk to a running VM

Not supported: Does not handle in-VM workload orchestration, container runtime, or model training framework code - use for cloud infrastructure provisioning and management only.

The Crusoe Cloud API Gateway exposes 95 endpoints covering the full Crusoe Cloud product surface: VM instances and instance groups, VM templates, VM types, instance images, persistent disks, snapshots, VPC networks, subnets, firewall rules, Infiniband networks and partitions, load balancers, organisations, projects, usage and billing, identities, SSH keys, tokens, and capacity lookups. The base URL is https://api.crusoecloud.com/v1alpha5 and most resources are scoped under a project_id path segment.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C+Signals: 4

86%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

42%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

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

Grade: ASignals: 4

51%

Example Density

How richly the API is illustrated with examples.

95%

Example Validity

Percentage of examples that conform to their schemas.

75%

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.

AI-Readiness & Agent Experience

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

Grade: FSignals: 4

11%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

63%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

86%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

72%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Crusoe Cloud API Gateway to your agent

Capabilities

Start building with Crusoe Cloud API Gateway API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Crusoe Cloud API Gateway

Jentic AI Readiness Score

Crusoe Cloud API Gateway

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness