Agents
Edge Agent API
Let AI agents deploy, manage, and monitor your infrastructure. Built for how LLMs think.
On this page6 sections
How it works#
You give your agent an access code and the URL, and it takes it from there:
- You → “Here’s my Edge agent code, deploy this app.”
- Agent → Discovers capabilities, deploys, reports back.
- You → “How’s it doing?”
- Agent → Checks metrics, reports status, suggests optimisations.
Three principles make this work:
- Discovery-first: The agent learns what it can do, what limits exist and what’s already deployed before taking any action.
- Budget-aware: Every response includes cost context. Set soft or hard budget caps so the agent operates within your limits.
tell_userfield: Every response includes a human-readable summary the agent can relay directly to you. No interpretation needed.
Quick start#
- Go to Account → Agent Access and create an agent access code.
- Give your AI agent the code and the URL:
https://edge.network/agent. - The agent calls the discovery endpoint to learn what it can do.
- The agent deploys, manages and monitors your infrastructure.
Designed for agents#
Unlike standard cloud APIs designed for humans or scripts, the Edge Agent API is built from the ground up for how LLMs work:
- Dry run everything: Preview any action before committing with the
X-Dry-Run: trueheader. - Project-based: Group resources by purpose (VM + CDN + DNS = one project). Health-check, scale or tear down everything at once.
- Errors as guidance: Error responses include actionable suggestions and a
tell_userfield explaining what the user should do. - Idempotent: All mutating endpoints support idempotency keys for safe retries.
Available products#
| Product | What agents can manage |
|---|---|
| Compute | VMs, scaling, metrics |
| CDN | Deployments, domains, cache |
| Storage | Buckets, uploads, objects |
| DNS | Zones, records, propagation |
| Shield | Bot protection (free) |
| Assist | AI answers, grounded |
OpenAPI specification#
The full Agent API surface is published as OpenAPI 3.0, with typed schemas ready for function calling.
Something unclear or out of date? Tell us