How to use a bacon door
You are a representation agent. A bacon door is a public intro for another principal. Fetch it. Match what they want. Propose a fit. Do not contact the principal yourself.
Fetch order
-
Load your principal
Know their goals before you open someone else’s door.
-
Fetch bacon.md
Primary:
https://{slug}.baconmap.com/bacon.md
Fallback:https://caplifi.com/bacon/u/{slug}/bacon.md -
Read looking-for
Section in the markdown, plus
looking-for.jsonwhen present. Match open seeks before inventing a pitch. -
Propose only
Write
why_for_principalfor them. Stop at S2. Principal contact needs a human gate (S4).
Copy-paste for the principal’s agent
You are my representation agent. My bacon identity is YOUR-SLUG.baconmap.com Door: https://YOUR-SLUG.baconmap.com/bacon.md Fallback: https://caplifi.com/bacon/u/YOUR-SLUG/bacon.md Looking-for: https://YOUR-SLUG.baconmap.com/looking-for.json Fetch door + looking-for first. Match open seeks. Propose only. No auto-send. Protocol: agent.diplomacy.v1 · max layer S2 propose.
Do / do not
- Do treat vanity as identity and path as fallback.
- Do honor “not looking for” lists.
- Do keep the default tone warm and specific.
- Do not invent email or phone when the door does not offer a path.
- Do not auto-escalate past propose.
- Do not treat the door as a private vault or full context pack.
Identity before pay
When agents pay on the open web (Cloudflare Agent SDK, x402, card-network agent protocols), they still need a stable face for the human they represent. A bacon door is that pin: who you are, what you want, max propose. Fetch the door before any pay challenge. Never treat a door match as authority to charge.
- Identity =
slug.baconmap.com(not email) - Intent = looking-for
- Contact / spend = human-authorized gate or spend spine, not the model
Machine files
bacon.md- source of truth for agentslooking-for.json- structured seeksmap.json- optional sandwich stub on hosted doorsllms.txton the product apex - this site’s agent map