Infrastructure your AI agent already knows how to use.
CLI-first. SSH-based. JSON by default. Every rdc command is designed for autonomous agents — no GUI, no browser automation, no custom integrations needed.
Illustrative output; actual runs may include extra logs. CLI reference: rdc machine
AI agents are powerful — but most infrastructure fights them
Your AI coding assistant can write, test, and debug code autonomously. But when it needs to deploy, check status, or manage infrastructure, it hits a wall: GUI-only dashboards, OAuth browser flows, unstable APIs, and responses that blow the context window.
Three steps to agent-managed infrastructure
Configure
Drop an AGENTS.md template into your project root. Your AI assistant reads it on startup and knows every rdc command.
Discover
Run rdc agent capabilities to get a structured JSON command tree. The agent knows what's available without documentation.
Operate
Deploy, monitor, rollback — all through CLI commands with JSON output. No GUI, no browser, no custom integration.
Why rdc is built for AI agents
Every design decision in Rediacc prioritizes machine-readable interfaces. Non-TTY detection auto-switches to JSON. The consistent envelope format means agents parse every response the same way. SSH-based auth means no OAuth flows or token management.
Built for autonomous infrastructure management
Zero integration effort
Drop AGENTS.md in your project. Your AI assistant immediately knows every available command, flag, and workflow.
Context-window friendly
JSON responses average ~200 tokens. The --fields flag lets agents request only the data they need. No wasted context.
Safe by default
--dry-run previews destructive operations. --yes enables automation. Agents can deploy confidently with built-in guardrails.
A message for you
Let your AI agent manage your infrastructure
Install the CLI. Add the AGENTS.md template. Your AI assistant handles the rest.
Get Started Free