---
title: "HCP · Protocol started by AUVY"
description: "An open format for installing agent capabilities. Each capability is a pack of three files that say what it can do, what it may do and how to run it, and one…"
url: https://www.auvy.ai/ventures/hcp
lang: en
site: AUVY
brief: https://www.auvy.ai/llms.txt
---

# HCP

[Company](https://www.auvy.ai/company) [Ventures](https://www.auvy.ai/company#ventures) HCP

![](https://www.auvy.ai/ventures/hcp/logo.svg)

Protocol started by AUVY building

An open format for installing agent capabilities. Each capability is a pack of three files that say what it can do, what it may do and how to run it, and one command runs it in any agent.

In one line

> “Every capability installs with its rules.”

my-capability/

├─ **surface.json** what it can do: verbs, inputs, transports

├─ **policy.json** what it may do: read, write, ask a person first

└─ **HARNESS.md** how to run it, for people and agents

{
 "id": "my-capability",
 "hcp": { "hcp": 1, "adapter_kind": "wrap", "transports": ["cli", "json_exec"] },
 "verbs": {
 "status": { "path": ["status"], "policy": "read", "help": "Health" },
 "send": { "path": ["send"], "policy": "write", "help": "Asks a person first" }
 }
}

The format

## Why it exists

Agents get new abilities all the time, but every tool arrives in its own shape. Nobody can see at a glance what it may do, what needs a person, and how to run it.

An HCP pack is three plain files: what the capability can do, what it's allowed to do, and how to run it. Hosts embed a runtime that reads them, the way they embed a tool client today, and coding agents load one plugin with a single command. AUVY installs every capability this way.

For

Anyone building agents or agent hosts who wants capabilities to install cleanly.

Where it stands

In private preview: specification, SDK, runtime, command line and agent plugin. AUVY and ImTakt run on it.

## What runs today

- hcp lint checks any pack against the three files
- hcp adopt sets it up in Cursor and other coding agents
- ImTakt ships its agent commands as an HCP pack
- AUVY installs its connections and tools as packs

## The company

Stage

Private preview

Legal

Inside AUVY GmbH until it becomes its own company

Run by

AUVY, until it has its own team

Infrastructure

Its own fenced part of AUVY's servers in Helsinki, until it moves to its own EU server

Runs on

Agent runtime · Sign-in and secrets

## What happens next

1. 1
Publish the specification and the docs
2. 2
Open the packages beyond the preview
3. 3
A second host beside AUVY

## More built by AUVY

[![](https://www.auvy.ai/ventures/akolo/logo.png)**akolo** exploring The structured platform for search funds and ETA teams: map a market, source targets, screen deals and reach the investment decision in one workspace. Full page → ](https://www.auvy.ai/ventures/akolo) [![](https://www.auvy.ai/ventures/imtakt/logo.svg)**ImTakt** exploring Real-time departures for bus and rail across Germany, with how often each train and connection actually held over the last 90 days. Agents get the same facts through a command line and a connector for AI assistants. Full page → ](https://www.auvy.ai/ventures/imtakt) [![](https://www.auvy.ai/ventures/outeva/mark.svg)**Outeva** building One desk for how a company grows: brand and naming, content, leads, meetings and booking, deals, contracts with signing, customers and revenue, with agents for the work that repeats. Full page → ](https://www.auvy.ai/ventures/outeva) [![](https://www.auvy.ai/ventures/openpulse/logo.svg)**OpenPulse** building One identity for people and agents, with realtime, payments, mail, video rooms and phone on the same @handle, built in with one SDK and run from one Console. Full page → ](https://www.auvy.ai/ventures/openpulse)