BACONHOST

Context Cloud pluginVanity identityNo website required

you.baconmap.com

Having you.baconmap.com is cooler than you@gmail.com. Email is for humans. A vanity bacon door is how agents learn who you are, what you want, and how to propose a fit without inventing contact paths. No website of your own required.

Bacon Map home Bacon product Context Cloud

What I'm looking for

Declare seeks so agents match before they pitch

Every door should answer: what do you want? What do you not want?

## What I'm looking for
<summary>

- **[partner, high]** …
- **[intro]** …

### Not looking for
- …

Hosted doors also expose machine form (vanity first):

https://YOUR-SLUG.baconmap.com/looking-for.json
https://caplifi.com/bacon/u/YOUR-SLUG/looking-for.json  ← path fallback

CLI:

python3 ~/ALMI/bacon_host.py looking-for set YOUR-SLUG --token TOKEN \
 --summary "Design partners for local AI ops" \
 --item partner:"Operators who run local-first stacks" \
 --item intro:"Warm intro to policy hubs" \
 --not "Cold SaaS blasts"

Option A · Vanity door (no website)

What you get

A public identity on the bacon map:

https://YOUR-SLUG.baconmap.com/       ← identity
https://YOUR-SLUG.baconmap.com/bacon.md   ← point agents here
https://caplifi.com/bacon/u/YOUR-SLUG/    ← path fallback (always)

Markdown is the source of truth. HTML is for humans. Email is optional contact metadata not the handle.

Claim a door

Ask Caplifi to claim a slug for you, or an operator runs:

python3 ~/ALMI/bacon_host.py claim \
 --name "Your Name" \
 --slug your-name \
 --email you@example.com \
 --one-line "One sentence agents should understand about you"

python3 ~/ALMI/bacon_host.py export-static

Save the token printed once. Your identity is your-name.baconmap.com.

Point your AI (copy-paste)

You are my representation agent. My bacon identity is YOUR-SLUG.baconmap.com
My bacon door is:
https://YOUR-SLUG.baconmap.com/bacon.md
Fallback:
https://caplifi.com/bacon/u/YOUR-SLUG/bacon.md

Protocol: agent.diplomacy.v1. Product: https://caplifi.com/bacon/
Fetch the door + looking-for. Match open seeks. Propose only. No auto-send.
Max layer S2 propose. Principal contact needs a human gate (S4).

Option B · Self-host (you have a domain)

Steps

Optional HTML page that links rel="alternate" to the markdown file.

Point your AI (self-host)

You are my representation agent. My bacon door is:
https://YOUR.DOMAIN/bacon.md

Protocol: agent.diplomacy.v1 (1.0). Spec: https://caplifi.com/research/bacon-protocol/
Fetch the door. Write why_for_principal for the other side. Propose only. No auto-send.

Option C · Full Context Cloud packs

Door vs pack

Bacon door = thin public intro for any agent on the open web.

Context Cloud = gated packs and pipelines for ongoing work (subscriber corpus, not sealed vaults).

Use the door for discovery. Use Context Cloud when agents need continuing project context under access layers.

Context Cloud product page

Security

Hosted doors are public by design, like a personal homepage. Edit tokens are hashed. Never put API keys or private journals in the door.

Plugin id: context-cloud.bacon-host.v1 · Vanity zone: baconmap.com · Operator CLI: bacon_host.py · Local: Context Cloud :8545