Datum is built for agents as first-class users. Rather than wrapping an API in a chat interface, Datum exposes the same primitives humans use — YAML manifests,Documentation Index
Fetch the complete documentation index at: https://datum.net/docs/llms.txt
Use this file to discover all available pages before exploring further.
datumctl commands, and CRD-based resources — in ways that agents can reason about reliably. This section covers the four surfaces agents use to work with Datum: Skills (procedural know-how), Datum MCP (live API access), llms.txt (doc index), and datumctl (the CLI agents drive directly).
The four agent surfaces
Skills
Self-contained instructions agents load on demand. One skill per Datum resource — install once, agents handle the rest.
Datum MCP
The official Model Context Protocol server. Gives agents authenticated, live access to Datum APIs.
llms.txt
A single index file at datum.net/docs/llms.txt that agents fetch to discover the full documentation surface.
datumctl
The CLI. Agents invoke it directly for any platform action — same surface humans use.
Which one should I use?
| If your agent needs to… | Use |
|---|---|
| Know how to do a Datum task (e.g. attach a domain to an HTTPProxy) | Skills |
| Read or write live Datum resources during a task | Datum MCP |
| Discover what documentation exists | llms.txt |
| Execute commands directly | datumctl |
datumctl or Datum MCP to act, and falls back to llms.txt when it needs deeper context. See Skills to get started.