Skip to content
Hoody.com

The Hoody Agent is an in-container Kit service that exposes a fully HTTP-driven AI coding agent. Every capability — session lifecycle, prompt execution, tool invocation, memory, GitHub integration, workflow orchestration, and observability — is available over a versioned REST API rooted at /api/v1/agent/. There is no separate CLI or websocket layer required to drive an agent; clients can create, steer, fork, and inspect sessions with ordinary HTTP requests.

The Agent is reached through the Hoody proxy at a per-container hostname. Every request authenticates with a Hoody token and is forwarded to the container’s bundled Agent service.

Every Agent endpoint shares the same base URL, parameterised by the owning container:

https://{projectId}-{containerId}-agent-1.{server}.containers.hoody.com/api/v1/agent

The Agent is not the management Hoody API. Requests to https://api.hoody.com or https://api.hoody.com will not reach the Agent and will return a 404 from the management plane.

The Agent API is organised into the following sub-pages. Each page documents the endpoints for one capability area.

Sessions

API Reference →

Create, prompt, fork, cancel, trim, and stream agent sessions.

Models & Providers

API Reference →

List available models and manage LLM providers, including API keys and OAuth pools.

Skills

API Reference →

Skill hub: CRUD operations, install, import, and per-session toggles.

Chat Agents

API Reference →

Create and customise chat-agent definitions, tools, and model bindings.

Memory

API Reference →

Persistent memory items, the project graph, and hybrid recall search.

GitHub

API Reference →

Auth, clone, commit, sync, branches, repositories, and pull requests.

MCP Servers

API Reference →

Configure MCP servers: list with live state, add, enable, remove, import, probe, and reconnect.

Tools

API Reference →

Tool catalogue, schemas, and sessionless or in-session tool runs.

Settings

API Reference →

Agent settings, fusion composites, and BYOA/ACP backends.

All Agent endpoints require a Hoody token passed in the Authorization header:

Authorization: Bearer <token>

Tokens are minted from the Hoody management plane and are scoped to the container whose Agent service is being addressed.