Install Jentic One Beta

Connect the Lambda Cloud API to your agent

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

Launch on-demand GPU instances from a chosen instance type and region

List running instances and retrieve the details of one

Restart or terminate instances when a job finishes

Create and delete filesystems for persistent storage across instances

Manage SSH keys and inbound firewall rules that control instance access

GET STARTED

Start building with Lambda Cloud API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Lambda Cloud API for, with concrete tasks.

★ Spin up GPU compute for an AI agent job

An AI agent integration created through Jentic needs GPU capacity on demand. The Lambda Cloud API lists available instance types, launches an instance in a region, and terminates it when the run finishes, so the agent provisions exactly the compute a training or inference job needs and releases it afterwards.

List instance types, launch one matching the job, then terminate it after the run completes

Persistent storage across instances

Training runs need data that outlives a single instance. The Lambda Cloud API creates filesystems and lists them, so an automation can attach persistent storage to new instances and keep datasets and checkpoints available across launches without re-copying them each time.

Create a filesystem, then launch an instance that mounts it for a training run

Lock down instance access

GPU instances exposed to the internet need controlled access. The Lambda Cloud API manages SSH keys and replaces inbound firewall rules, letting an agent register the right key and restrict inbound traffic to known addresses before a workload starts.

Add an SSH key and replace the inbound firewall rules to allow only a specified address

Key Endpoints

33 endpoints — the lambda cloud api launches and manages on-demand gpu compute instances for training and inference workloads.

METHOD

PATH

DESCRIPTION

GET

/api/v1/instances

List running instances

POST

/api/v1/instance-operations/launch

Launch instances

POST

/api/v1/instance-operations/terminate

Terminate instances

GET

/api/v1/instance-types

List available instance types

POST

/api/v1/filesystems

Create a filesystem

GET

/api/v1/images

List available images

POST

/api/v1/ssh-keys

Add an SSH key

GET

/api/v1/firewall-rules

List inbound firewall rules

GET

/api/v1/instances

List running instances

POST

/api/v1/instance-operations/launch

Launch instances

POST

/api/v1/instance-operations/terminate

Terminate instances

GET

/api/v1/instance-types

List available instance types

POST

/api/v1/filesystems

Create a filesystem

GET

/api/v1/images

List available images

POST

/api/v1/ssh-keys

Add an SSH key

GET

/api/v1/firewall-rules

List inbound firewall rules

Why Jentic?

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

Setup

Wiring Lambda Cloud by hand means handling its API key over bearer or basic auth and registering SSH keys and firewall rules before you can launch an instance. Through Jentic you install once, import Lambda Cloud from the API Directory, store the key once, and your agent calls it.

Permission scoping

Lambda Cloud puts the instance id in the URL path for the detail and update operations, so a rule can limit your agent to specific instances for reads and updates. You choose the operations it may call, so destructive ones like launching or terminating instances are not included unless you add them.

Credential isolation

Your Lambda Cloud API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'launch a GPU instance' or 'list instance types', and Jentic returns the matching Lambda Cloud operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Lambda Cloud API through Jentic.

What authentication does the Lambda Cloud API use?

The Lambda Cloud API authenticates with your Lambda Cloud API key, sent either as a bearer token in the Authorization header or via HTTP basic auth, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt or logs.

Can I launch and terminate GPU instances with the Lambda Cloud API?

Yes. The launch operation starts instances of a chosen type and region, and the terminate operation releases them, so an agent can provision GPU compute for a job and tear it down when the run finishes.

What are the rate limits for the Lambda Cloud API?

The Lambda Cloud API spec notes that requests are generally limited to one request per second, with the instance launch operation limited to one request per 12 seconds. Design agent flows to respect those limits and back off on throttling.

How do I launch a GPU instance through Jentic?

Install Jentic One on your own infrastructure with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then import the Lambda Cloud API from the API Directory and search for 'launch a GPU instance'. Store the API key once and your agent can provision and release instances. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Lambda Cloud MCP server?

You don't need an MCP server to give your agent the Lambda Cloud API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls it, with operations discovered on demand instead of loaded into the agent's context.

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

Yes. The instance id sits in the URL path for the detail and update operations, so a rule can scope the agent to reading and updating specific instances, while destructive operations like launching or terminating stay out of reach unless you add them. Every action it takes is recorded in an audit log.

Lambdalabs Lambda Cloud API

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyCloud InfrastructureComputebearer, basic33 EndpointsREST

For Agents

Launch, list, restart, and terminate GPU instances, manage filesystems, SSH keys, and firewall rules, and open support tickets on Lambda Cloud.

Use for: Launch a GPU instance of a specific type, List my running instances, Terminate an instance when training completes, Create a filesystem and attach it to an instance

Not supported: Does not handle billing, model training code, or data labeling. Use for provisioning and managing GPU cloud instances only.

The Lambda Cloud API launches and manages on-demand GPU compute instances for training and inference workloads. It lets you pick an instance type and region, launch, restart, and terminate instances, attach persistent filesystems, manage SSH keys and inbound firewall rules, browse available images, and open support tickets with attachments. Requests are authenticated with a Lambda Cloud API key.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

97%

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).

100%

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: B+Signals: 4

19%

Example Density

How richly the API is illustrated with examples.

99%

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.

AI-Readiness & Agent Experience

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

Grade: C-Signals: 4

54%

Description Coverage

Coverage of descriptions across API elements.

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.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

35%

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

74%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Lambda Cloud API to your agent

Capabilities

Start building with Lambda Cloud API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Lambdalabs Lambda Cloud API

Jentic AI Readiness Score

Lambda Cloud API

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