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

JarvisLabs Instances API

GPU and CPU instance lifecycle.

JarvisLabs Instances API is one of 5 APIs that JarvisLabs publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 7 operations across 4 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

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

7 operations 4 paths 5 schemas 1 DELETE2 GET1 PATCH3 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.jarvislabs.ai/v1
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

JarvisLabs Instances API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — API token generated at https://jarvislabs.ai/settings/api-keys. In the SDK this is set via jarvisclient.token; the CLI stores it via jl setup.

Paths & Operations 7

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

Instances 7

GPU and CPU instance lifecycle.

GET
/instances
List instances
listInstances → 200401
POST
/instances
Create an instance
createInstance body → 201400401
GET
/instances/{machine_id}
Get an instance
getInstance 1 param → 200401404
PATCH
/instances/{machine_id}
Rename an instance
renameInstance 1 param body → 200401404
DELETE
/instances/{machine_id}
Destroy an instance
destroyInstance 1 param → 200401404
POST
/instances/{machine_id}/pause
Pause an instance
pauseInstance 1 param → 200401404
POST
/instances/{machine_id}/resume
Resume an instance
resumeInstance 1 param body → 200401404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are CreateInstanceRequest (13 properties), Instance (13 properties), ResumeInstanceRequest (5 properties), ActionResult (2 properties). Each schema is shown below with its type and property counts.

Error
object
2 properties
Instance
object
13 properties
ResumeInstanceRequest
object
5 properties
ActionResult
object
2 properties
CreateInstanceRequest
object
13 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jarvislabs-instances-api-openapi.yml Raw ↑

Other APIs JarvisLabs publishes across the network.

JarvisLabs Account API
JarvisLabs Filesystems API
JarvisLabs GPU Types API
JarvisLabs Templates API
Where this information came from

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