Linode API

Name: Linode API
Brand: Linode API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth2, bearer350 EndpointsREST

For Agents

Provision Linode instances, manage LKE Kubernetes clusters, configure NodeBalancers, and deploy managed databases. Covers compute, networking, storage, and DNS across Akamai's global cloud network.

Install Jentic One Beta

Connect the Linode API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Linode 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Linode API.

Provision Linode instances with specified plans, distributions, and SSH keys across 11 global datacenters

Deploy and scale Linode Kubernetes Engine (LKE) clusters with configurable node pools and auto-scaling

Configure NodeBalancers with health checks, session stickiness, and TLS termination for traffic distribution

GET STARTED

Start building with Linode API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Linode API for, with concrete tasks.

★ AI Agent Cloud Provisioning

AI agents use the Linode API through Jentic to provision cloud instances on demand without navigating the Linode Cloud Manager. An agent searches for the instance creation operation, receives the request schema with type (plan), image, region, and root_pass parameters, then executes the call. Linode provisions the instance in under 60 seconds with a public IPv4 address ready for SSH access. Predictable pricing starts at $5/month for the smallest plan.

Create a Linode instance with plan 'g6-standard-2' (4GB RAM), image 'linode/debian11', region 'us-east', and label 'web-app-01' with SSH key authorization

Managed Kubernetes with LKE

Create and operate Linode Kubernetes Engine clusters with configurable node pools, automatic control plane management, and integrated cloud controller for NodeBalancer provisioning. The API handles cluster creation, node pool scaling, kubeconfig retrieval, and version upgrades. Clusters provision in under 5 minutes with nodes distributed across the region for high availability.

Create an LKE cluster named 'production' in us-east with Kubernetes version 1.28 and a node pool of 3 g6-standard-4 nodes with auto-scaling from 3 to 10

Load Balancing with NodeBalancers

Configure NodeBalancers to distribute inbound traffic across multiple Linode instances with health checks, connection throttling, and TLS termination. Each NodeBalancer supports multiple configurations (ports) with backend nodes assigned by IP and port. Health checks detect unhealthy backends and remove them from rotation, while session stickiness maintains user affinity for stateful applications.

Create a NodeBalancer in us-east, add a configuration for port 443 with TLS termination using certificate ID 12345, and add 3 backend nodes on port 8080

Managed Database Deployment

Deploy managed database clusters with automated daily backups, point-in-time recovery, SSL connections, and maintenance windows. The API supports PostgreSQL, MySQL, and MongoDB with configurable cluster sizes from single-node development instances to multi-node high-availability deployments. Credential management, connection string retrieval, and cluster scaling are handled through dedicated endpoints.

Create a managed PostgreSQL 14 cluster named 'app-data' with a g6-dedicated-2 plan, 3 nodes for high availability, and automatic backups in the us-east region

Object Storage Management

Manage S3-compatible object storage for static assets, backups, and media files. The API provides bucket creation, access key generation, and cluster endpoint discovery. Object storage buckets support static website hosting, CORS configuration, and access control lists. Keys can be scoped to specific buckets for least-privilege access in multi-tenant applications.

Create an object storage key with read-write access limited to the bucket 'app-assets' in the us-east-1 cluster

Key Endpoints

350 endpoints — provision and manage linux cloud infrastructure including linode instances, kubernetes clusters (lke), managed databases, nodebalancers, block storage volumes, object storage, and dns across 11 global regions.

METHOD

PATH

DESCRIPTION

POST

/linode/instances

Create a new Linode instance

GET

/linode/instances

List all Linode instances

POST

/lke/clusters

Create a Kubernetes cluster

POST

/nodebalancers

Create a NodeBalancer

POST

/databases/postgresql/instances

Create a managed PostgreSQL cluster

POST

/volumes

Create a block storage volume

GET

/linode/types

List available instance plans and pricing

POST

/object-storage/keys

Create an object storage access key

POST

/linode/instances

Create a new Linode instance

GET

/linode/instances

List all Linode instances

POST

/lke/clusters

Create a Kubernetes cluster

POST

/nodebalancers

Create a NodeBalancer

POST

/databases/postgresql/instances

Create a managed PostgreSQL cluster

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Linode personal access tokens and OAuth credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped Bearer tokens — raw API tokens never enter the agent's context window.

Intent-based discovery

Agents search by intent (e.g., 'deploy a managed PostgreSQL database') and Jentic returns matching Linode operations with full schemas, including valid plan slugs, region identifiers, and engine versions.

Time to first call

Direct Linode integration: 1-2 days for API client setup, OAuth implementation, and error handling. Through Jentic: under 1 hour — search for the operation, receive the schema, execute with automatic token management.

FAQs

Specific to using Linode API through Jentic.

What authentication does the Linode API use?

The Linode API supports OAuth 2.0 and personal access tokens. Personal access tokens are passed as Bearer tokens in the Authorization header. OAuth 2.0 provides scoped access with granular permissions per service (linodes, volumes, domains, etc.). Through Jentic, tokens are stored encrypted in the MAXsystem vault so agents never handle raw credentials.

Can I create a Linode instance with a specific SSH key through the API?

Yes. The POST /linode/instances endpoint accepts an authorized_keys array with public SSH key strings and an authorized_users array with Linode usernames whose profile keys are injected. Keys are added to the root user's authorized_keys file on first boot, eliminating root password authentication.

What are the rate limits for the Linode API?

The Linode API enforces rate limits per endpoint with specific limits varying by operation type. Standard GET endpoints allow approximately 800 requests per minute. Write operations (POST, PUT, DELETE) have lower limits. Rate limit headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset) are included in every response.

How do I deploy a Kubernetes cluster using the Linode API through Jentic?

Search Jentic for 'create kubernetes cluster on Linode'. The agent receives the POST /lke/clusters schema requiring label, region, k8s_version, and node_pools array. Each node pool specifies type (plan slug) and count. After creation, retrieve the kubeconfig via GET /lke/clusters/{clusterId}/kubeconfig to connect kubectl.

Can I resize a Linode instance without data loss?

Yes. The POST /linode/instances/{linodeId}/resize endpoint accepts a new type (plan slug). The Linode shuts down, migrates to appropriate hardware, resizes the disk to fit the new plan's allocation, and reboots. Data on the primary disk is preserved. Downsizing requires the current disk usage to fit within the smaller plan's limit.

How does Jentic simplify Linode infrastructure management for AI agents?

Agents search by intent (e.g., 'provision a 4GB Linux server') and Jentic returns matching Linode operations with full schemas including valid plan slugs, region IDs, and image identifiers. No SDK setup or OAuth flow implementation required — install with pip install jentic and sign up at https://app.jentic.com/sign-up.

Linode API

Connect the Linode API to your agent

Capabilities

Start building with Linode API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs