Linode APIs for AI Agents
Cloud InfrastructureComputeMixed ProvenanceOAuth 2.0Bearer tokenAgent Ready
For Agents
APIs2 in catalogue
Endpoints799 indexed
AuthOAuth 2.0 / Bearer token
ProvenanceMixed provenance
An agent can provision and manage Linode instances, LKE Kubernetes clusters, NodeBalancers, block and object storage, managed databases, DNS, and firewalls, and read account invoices, payments, and event streams. It works across both the current Akamai Linode API and the earlier Linode API spec using one Bearer credential.
Linode is a developer-focused cloud built on Akamai's network, offering predictable pricing and full IaaS control over Linux compute, managed Kubernetes, and S3-compatible storage. Its API surfaces the whole resource lifecycle, from provisioning a single instance to running multi-node database clusters and account billing audit, through one credential.
Use for: Provisioning and managing Linode cloud infrastructure: Linux instances, LKE Kubernetes clusters, NodeBalancers, block and object storage, managed databases, DNS, firewalls, and reading account billing and event data.
Not supported: CDN edge caching, application performance monitoring, PaaS deployment, email delivery, CI/CD pipelines
Credentials: Both API specs use the same Linode auth model, so a single OAuth 2.0 credential or personal access token presented as a Bearer token works across both.
Across 2 Linode APIs: 1 vendor-official, 1 third-party, all indexed by Jentic and kept validated and agent-ready.
Linode, now part of Akamai, is a cloud infrastructure provider whose APIs let teams provision and operate Linux compute, managed Kubernetes, databases, storage, and networking programmatically. The Jentic directory lists two Linode API specs: the current Akamai Linode API with 449 endpoints across compute, LKE, object storage, databases, NodeBalancers, VPCs, firewalls, DNS, and account billing, and an earlier 350-endpoint spec covering the same core compute, storage, networking, and managed-service resources. Both authenticate with OAuth 2.0 or a personal access token presented as a Bearer credential.
Linode API Catalog
2 APIs across 1 product group.
Cloud Infrastructure2
Akamai: Linode APIProvision and manage Linode cloud resources - VMs, Kubernetes clusters, object storage, databases, networking, and account billing - across 449 endpoints suitable for full-lifecycle cloud automation.~449 endpointsLinode APIProvision Linode instances, manage LKE Kubernetes clusters, configure NodeBalancers, and deploy managed databases.~350 endpoints
Which Linode API should I use?
| I want to... | Use |
|---|---|
| Full current cloud surface including VPCs, firewalls, and detailed account event and billing data | Akamai: Linode API |
| Core compute, Kubernetes, database, and storage provisioning against a stable earlier spec | Linode API |
Install Jentic One Beta
Connect the Linode APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Linode APIs, 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" | sh2
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" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
Once connected, ask your agent something like: “provision and manage Linode cloud infrastructure with an AI agent”.
What AI Agents Can Do with Linode
Each workflow spans multiple Linode APIs. Jentic routes each operation to the right API automatically.
Provision compute across either Linode spec
Create and resize Linode instances whether an agent is pointed at the current Akamai Linode API or the earlier spec, since both expose the instance creation and resize operations with region, plan type, and image parameters.
Example prompt:
Create a Linode instance with region us-east, type g6-standard-2, and image linode/debian11, then poll the instance until it reports running.
APIs used
Akamai: Linode API + Linode API
Stand up a Kubernetes cluster with load balancing
Provision an LKE Kubernetes cluster and a NodeBalancer to distribute traffic across its nodes. Both specs cover LKE cluster creation, node pool scaling, kubeconfig retrieval, and NodeBalancer configuration.
Example prompt:
Create an LKE cluster in us-east with a three-node pool, retrieve its kubeconfig, then create a NodeBalancer with a port 443 configuration fronting the cluster nodes.
APIs used
Akamai: Linode API + Linode API
Deploy managed database with object storage backups
Deploy a managed PostgreSQL or MySQL cluster and create an S3-compatible object storage bucket and scoped access key for backups and application assets, using operations present in both specs.
Example prompt:
Create a managed PostgreSQL cluster in us-east, then create an object storage bucket and issue a read-write access key scoped to that bucket.
APIs used
Akamai: Linode API + Linode API
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Linode APIs by hand means running the OAuth 2.0 flow or a personal access token, sending Bearer headers on every call, and handling retries across a large infrastructure surface. With Jentic you install Jentic One once, add a Linode API from the Jentic directory, store the credential once, and your agent calls either spec.
Permission scoping
Provisioning operations take their configuration in the request body rather than a resource id in the path, so you scope the agent to only the operations it needs. Read-only inventory calls such as listing instances, types, or account events can be enabled while create calls like instance, cluster, or volume creation stay out unless you add them.
Credential isolation
Your Linode OAuth 2.0 credential or personal access token is stored 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 the Jentic directory by intent such as 'provision a Linode instance' or 'deploy a managed PostgreSQL database', 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.
FAQs
Specific to using Linode APIs through Jentic.
What is the difference between the two Linode API specs in the directory?
The directory lists two Linode specs. The current Akamai Linode API carries 449 endpoints across more than 80 resource groups, including VPCs, firewalls, and detailed account event and invoice data. The earlier spec has 350 endpoints covering the same core compute, Kubernetes, database, storage, networking, and DNS resources. For the widest current surface, prefer the Akamai Linode API.
Does one credential work across both Linode specs?
Yes. Both specs use the same Linode authentication model, so a single OAuth 2.0 credential or personal access token presented as a Bearer token covers operations on either. Through Jentic that credential is stored once in your own Jentic One instance and injected at execution time.
What can an agent do across the Linode APIs?
An agent can provision and resize Linux instances, create and scale LKE Kubernetes clusters, configure NodeBalancers, deploy managed PostgreSQL, MySQL, and MongoDB clusters, manage block and object storage, set up DNS and firewalls, and read account invoices, payments, and event streams for billing and audit.
Is Linode the same as Akamai?
Linode was acquired by Akamai and its cloud compute product now runs on Akamai's network. The current spec is titled the Akamai Linode API, while the earlier spec keeps the Linode API name. Both describe the same underlying Linode cloud platform.
Can agents handle both read-only reporting and provisioning?
Yes. Read operations such as listing instances, invoices, and account events support reporting and audit use, while write operations such as creating instances, clusters, databases, and volumes handle provisioning. You choose which of these operations an agent may call.
How does Jentic reduce the work of using the Linode APIs?
Instead of implementing the OAuth flow, choosing hosts, sending Bearer headers, and handling retries by hand, an agent searches Jentic by intent and receives the matching Linode operation with its input schema. The credential stays in your Jentic One instance and is injected at execution time.
If you need a different Cloud Infrastructure vendor
All 4 are in the Jentic catalogue with the same one-credential, intent-search pattern.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.