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 / Linode / Linode API
Linode API logo

Linode API

Browse all Linode APIs
57
AI ReadinessFoundational (C)57/100
See full scorecard
Community OpenAPI document · agent-readyCloud InfrastructureComputeoauth2, bearer350 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

Use for: I need to create a Linode instance with Debian in the us-east region, List all running Linodes in my account with their IP addresses, Set up a managed MySQL database cluster with automatic backups, I want to create a Kubernetes cluster with auto-scaling node pools

Not supported: Does not handle CDN configuration, email delivery, or CI/CD pipelines - use for cloud infrastructure provisioning, managed services, and network configuration only.

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. The API provides 350 endpoints covering compute, networking, storage, and managed services with OAuth 2.0 and personal access token authentication.

Jentic One on GithubView OpenAPI Document

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.

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%2Flinode.com%2Flinode" | 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%2Flinode.com%2Flinode" | 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

Manage block storage volumes with attachment, detachment, and resize operations for persistent data

Deploy managed database clusters (PostgreSQL, MySQL, MongoDB) with automated backups and failover

Configure DNS zones and records with full domain management and zone import/export capabilities

Access and manage object storage buckets and keys for S3-compatible file storage

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

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

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.

L

Linode API

- Foundational (C)
57/100
45
Foundational Compliance
70
Developer Experience & Jentic Compatibility
57
AI-Readiness & Agent Experience
43
Agent Usability
75
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
45

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 4
81%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

99%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

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.

70

Developer Experience & Jentic Compatibility

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

Grade: B+Signals: 4
36%

Example Density

How richly the API is illustrated with examples.

93%

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.

57

AI-Readiness & Agent Experience

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

Grade: CSignals: 4
67%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

99%

OperationId Quality

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

61%

Summary Coverage

Coverage of summaries across operations/tags/info.

43

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D-Signals: 1
43%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

75

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1
75%

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 Linode API by hand means running its OAuth2 authorization-code flow or personal access token, choosing between the v4 and v4beta hosts, sending Bearer headers on every call, and handling retries yourself. Through Jentic you install once, import the Linode API from the API Directory, store the token once, and your agent calls it.

Permission scoping

These provisioning calls take their configuration in the request body rather than a resource id in the URL path, so limit the agent to the operations it needs, such as GET /linode/instances or GET /linode/types for read-only inventory. You choose the operations it may call, so create calls like POST /linode/instances, POST /lke/clusters, or POST /volumes are not included unless you add them.

Credential isolation

Your Linode personal access token or OAuth credential is stored once, encrypted, by your own Jentic One instance and injected as the Bearer header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'deploy a managed PostgreSQL database' or 'create a NodeBalancer', and Jentic returns the matching Linode operation with its input schema, including valid plan and region identifiers, 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 offers similar developer-focused cloud with more managed services but comparable pricing

Choose DigitalOcean when the user needs App Platform (PaaS) or prefers the DigitalOcean ecosystem. Choose Linode for Akamai's network backbone, competitive pricing on high-memory instances, and LKE Kubernetes.

Alternative

Render API

→

Render provides PaaS deployment while Linode offers full IaaS control over infrastructure

Choose Render for zero-config web service deployment from Git. Choose Linode when you need full VM access, custom networking, and the flexibility of IaaS.

Complementary

Netlify API

→

Netlify handles frontend deployment and CDN while Linode manages backend compute and databases

Use Netlify alongside Linode for JAMstack architectures - Netlify serves the static frontend, Linode runs the API backend and managed databases.

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 your Jentic One instance 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 run it through Jentic One, the self-hosted execution layer.

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

Yes. Because you run Jentic One yourself, you decide which Linode operations your agent may call, and only the ones you add are available to it. You can keep the agent read-only by granting just inventory calls like GET /linode/instances and GET /linode/types, while withholding provisioning calls such as POST /linode/instances, POST /lke/clusters, and POST /volumes. Since these calls take their configuration in the request body rather than a resource id in the URL path, scoping is done at the operation level, and your stored token is injected only when an allowed operation runs.

GET STARTED

Start building with Linode API

Explore with Jentic One
View OpenAPI Document