A protocol that connects all of your AIs

ASMP · Agent Service Manifest Protocol · v0.1

See it

Lost AIs stay lost.

Without a map of who does what, every AI wanders — searching files, guessing apps, redoing work the last AI already did. That waste never adds up. A smarter chatbot alone won't get you AI that actually learns.

Time Every session starts from zero. Same search, again and again.

Effort Spent hunting for the right app — not doing what you asked.

Learning AIs don't share what they find — so they never build on each other. You never get truly smart AI.

Same question below — first with no map, then with one.

The question

Show me the last five emails, text messages, and phone calls from Joe Stanton.

Before No map — three channels, wrong guesses, still empty-handed

0s

Your AI

0 tokens 0:00 waiting…

The map

Wires appear as your AI hunts email, texts, and calls — no registry, no shortcuts.

After One lookup — three registered tools, results in parallel

—

Your AI

The map

Registry already knows who handles email, texts, and calls — straight to each.

Self-healing

Every miss makes the
next agent smarter.

One gap found → one breadcrumb → every agent after wins.

Without breadcrumbs

The silent failure loop

Same gap. Every session. Registry never learns.

i Agent asks registry "Who handles fleet sync?"

ii Miss — empty result Service exists, not registered

iii Scavenger hunt grep repos · guess ports · ~45 min

iv Reinvent or give up Knowledge dies with the session

45m wasted per agent, per gap

With asmp todo

The self-healing flywheel

One agent pays once. Every agent after inherits the find.

1 Agent queries registry service_find · asmp find

2 Miss — but finds real software conduit on :22 · repo on disk

3 Drop breadcrumb asmp todo conduit --note "…"

4 Promote to manifest asmp.yaml → scan · announce

5 Registry grows +1 service · forever

46 services — compounds with every todo promoted

One painful find First agent hunts. The gap gets documented once.

Free lookups Every agent after gets the answer in milliseconds.

Registry grows One promoted todo. Permanent entry in the map.

Flywheel → Spec

Ship

Every repo ships asmp.yaml.

Scan picks it up. Agents meet it.

Ship it

asmp.yaml at repo root with real capabilities.provides.

Scan finds it

asmp scan syncs into ~/.asmp/services/.

Agents meet it

Announce on start. Query by capability — not ports.

Spec → Scan loop

Install

One command.

~/.asmp/ and a registry on :7700.

terminal

 # bootstrap ASMP on this machine curl -fsSL https://raw.githubusercontent.com/agent-service-manifest-protocol/agentservicemanifest.io/main/scripts/bootstrap-asmp.sh | bash 

Agent prompt → Quickstart

What

One device. Many agents.

MCP · tools. A2A · agents. ASMP · what's on this machine.

Host Profile

Device capabilities and registry policy.

Service Manifest

One YAML per service, written by the builder.

Registration

:7700 — discover, register, extend.

Stack

Below MCP and A2A.

Three protocols. Three questions.

Tool layerMCP

"What tools can I use?"

Agent layerA2A / ACP

"What agents can I talk to?"

Host layerASMP

"What runs here?"

Not a replacement for launchd or k8s — the file they can read.

I

Part One · Host Profile

What this device is, and what it can do.

One YAML file at a fixed path: hardware, capabilities, where manifests live, and who gets to register services.

~/.asmp/host.yaml — personal scope
/etc/hmp/host.yaml — system scope
policy decides who can register, port ranges, and limits

~/.asmp/host.yaml

 asmp: "0.1" kind: host host_id: "daniels-macbook-2026" device_class: personal_compute os:  name: macOS  version: "15.3.1"  arch: arm64 hardware:  cores: 12  ram_gb: 36  gpu: "Apple M4 Pro" capabilities:  - files.local  - email.local  - calendar.local  - networking  - containers  - gpu.inference registry:  path: ~/.asmp/services/  api: http://127.0.0.1:7700 policy:  agent_can_register: true  requires_approval: false  max_services: 100  allowed_ports: "7000-9999"  data_sensitivity_default: medium 

II

~/.asmp/services/inbox-triage.yaml

 # written by the agent that built it asmp: "0.1" kind: service identity:  name: inbox-triage  author: "agent://reeves/mail"  version: "1.2.0" runtime:  exec: "python -m inbox_triage"  restart: on-failure network:  port: 7821  bind: 127.0.0.1 capabilities:  - email.local  - files.local mods:  - name: spam-scorer  author: "agent://eidos/filter" observability:  log_dir: ~/.asmp/logs/inbox-triage display:  label: "Inbox Triage"  icon: mail 

Part Two · Service Manifest

One file per service. Authored by the agent.

Each file in ~/.asmp/services/. Short on purpose — enough to wire ports and restarts, not enough to fill a wiki.

Identity, runtime, network — name, how to start it, which port
Capabilities — what host resources it uses
Observability & display — logs and a human-readable label
Mods — another agent can extend a service it didn't build

III

Part Three · Registration Protocol

A localhost API to register, discover, and extend.

HTTP on 127.0.0.1:7700 only. List services, search by capability, attach mods, remove cleanly. Nothing past localhost.

POST/servicesRegister a new service

GET/servicesList all registered

GET/services/{name}Manifest + runtime state

PATCH/services/{name}Update a manifest

DEL/services/{name}Deregister a service

GET/hostGet the host profile

GET/capabilitiesQuery by capability

POST/services/{name}/modsAttach a mod

Flow

Inventory first.

Ask the registry. Move on.

i

Ask

"Which AIs and MCPs help manage my email?"

ii

Query

GET /capabilities?provides=email.local on :7700.

iii

Match

Registry returns manifests — names, ports, capabilities.

iv

Invoke

Agent calls the right service. No port lottery.

v

Next session

Same inventory. No rediscovery. ~250ms, not ~45s.

Principles

Six constraints.

I

Agents write manifests

Whoever builds the service declares it. The inventory outlives the session.

II

Host-centric

Tied to a device — your Mac, your homelab, your box.

III

Runtime-neutral

launchd, systemd, Docker, k8s — ASMP is the input, not the runner.

IV

Works with MCP & A2A

Tools above, agents beside, inventory underneath.

V

Small surface area

Every field does a job. No manifest the size of a novel.

VI

Mods are first-class

Services can be extended by agents that didn't build them.

Roadmap

What's next.

Spec

JSON Schema

Formalize the manifest schema for validation and tooling.

Implementation

Reference server

The registration API server in Python, bound to localhost.

Migration

Reeves migration

Convert 35+ existing services to ASMP manifests.

Open source

Eidos package

Extract as a framework-agnostic, open-source package.

Interop

MCP bridge

Auto-generate MCP tool manifests from ASMP service capabilities.