Skip to main content
An agent holds the configuration a run needs: the environment it acts in, the model that drives it, and optional skills and instructions. Start with a pre-built agent from H, or create your own. Names are scoped to your organization: the agents, skills, and environments you create are visible only within it. H’s pre-built agents and environments live under the reserved h/ namespace (for example h/web-surfer-flash and h/browser); they are available to every organization and read-only, so modifying one returns 403. Agents you create have no prefix.

Pre-built agents

H maintains a catalog of configured agents under the h/ namespace. You can run them as-is, with no setup. Pre-built agents that delegate to subagents (such as h/deep-search-pro) build on Multi-agent.
List them anytime with GET /api/v2/agents:
Reference one by name when you create a session, and the platform supplies its full configuration:

Configure an agent

Each environments, skills, or subagents entry is either a string catalog id or an inline object. A reference keeps the definition central and reusable. An inline object is handy for one-offs. For exact field constraints, see Create an agent.

Create your own

Create an agent once, then reference it by name in every session:

Context auto-compaction

Long sessions outgrow the model’s context window, so every agent compacts its own history automatically. Nothing to configure, and it can happen several times in one session.

Endpoints

The list is paginated (page, size) and returns an items / page / total envelope. Sort it with sort=created_at or sort=agent_name, prefixed with - for descending.