canonical: https://jentic.com/apis/nomadproject.io/nomadproject

# Nomadproject Nomad API

Nomad is a workload orchestrator from HashiCorp that deploys and manages applications across a cluster. The API registers and reads jobs, lists allocations and deployments, manages cluster nodes, and administers ACL tokens and policies, exposing the scheduler that places workloads on available nodes.

## For AI agents

Register and read jobs, inspect allocations and deployments, manage cluster nodes, and administer ACL tokens. Authenticates with an API key sent in the X-Nomad-Token header.

## Scope

Does not provision the underlying cloud servers. Use the Nomad API for jobs, allocations, deployments, node management, and ACL administration within an existing cluster.

## Capabilities

- Register, read, and update jobs
- List and inspect allocations
- List and monitor deployments
- Read and manage cluster nodes
- Bootstrap and manage ACL tokens and policies
- Read cluster and scheduler status

## Use cases

### Job Deployment and Management

An AI agent connected through Jentic can operate a Nomad cluster's workloads. It registers and reads jobs and reads their status back, so an assistant can roll out an application or report on a running job without a manual CLI session.

Example prompt: Register a job and report its resulting status

### Deployment Monitoring

Rollouts need watching. The Nomad API lists deployments and allocations, letting an agent track a deployment's progress and surface which allocations are healthy so a human sees the state of a release at a glance.

Example prompt: List a deployment's allocations and report which are healthy

### Access Control Administration

Cluster access is governed by ACL tokens. The API bootstraps the ACL system and lists and manages tokens, so an agent can audit who holds access and provision or revoke tokens under a controlled policy.

Example prompt: List the current ACL tokens and report their policies

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/acl/bootstrap` | Bootstrap the ACL system |
| GET | `/acl/tokens` | List ACL tokens |
| GET | `/allocations` | List allocations |
| GET | `/deployments` | List deployments |
| GET | `/job/{jobName}` | Read a job by name |

## Key resources

- **Jobs** — Register, read, and update workloads
- **Allocations** — Running instances of a job's tasks
- **Deployments** — Rollout progress for jobs
- **Nodes** — Cluster nodes that run workloads
- **ACL** — Tokens and policies for access control

## Why Jentic

- **Setup:** Wiring the Nomad API by hand means configuring the cluster address, building job specifications, and threading the X-Nomad-Token through every call yourself. Through Jentic you install once, import Nomad from the API Directory, store the token once, and your agent calls the job and deployment operations directly.
- **Permission scoping:** You choose which of the operations your agent may call. You might allow job and deployment reads while blocking job registration and ACL changes, so the agent can monitor the cluster without altering workloads.
- **Credential handling:** Your Nomad token 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.
- **Discovery method:** Agents search Jentic by intent such as 'register a job', and Jentic returns the matching Nomad operation with its input schema so the agent calls it with the right job specification.

## Related APIs

- **Kubernetes** — Container orchestration for deployments, pods, and services
- **DigitalOcean** — Cloud infrastructure for droplets, networking, and managed services
- **Render** — Managed platform for deploying services and jobs

## FAQ

### What authentication does the Nomad API use?

It authenticates with an API key sent in the X-Nomad-Token header, per the OpenAPI spec. Through Jentic the token is stored once, encrypted, by your own self-hosted instance and injected when the agent calls, so it never appears in the agent's prompt or logs.

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

Yes. You choose which operations the agent may call. You might allow job and deployment reads while blocking job registration and ACL changes, so the agent can monitor the cluster without altering workloads, with every call logged by your own instance.

### Is there a Nomad MCP server?

You don't need an MCP server to give your agent the Nomad API. Jentic connects it directly from the API Directory: import it, store the token once, and your agent calls the job, allocation, and deployment operations. Operations are discovered on demand, so nothing extra loads into the agent's context.

### What are the rate limits for the Nomad API?

The OpenAPI spec does not define rate limits. Check the Nomad documentation for any current limits before running high-volume job or allocation queries against a cluster.

### What can the Nomad API do?

It registers and reads jobs, lists allocations and deployments, manages cluster nodes, reads scheduler status, and administers ACL tokens and policies for the cluster.

### How do I register a job through Jentic?

Search Jentic by intent, for example 'register a job', and Jentic returns the matching Nomad operation with its input schema. Your agent supplies the job specification and reads back the result. To run it on your own infrastructure, install Jentic One from its GitHub repo.