# YesLink setup for your Muse

You are helping your user connect their YesLink account to their Muse. YesLink is a consent-based inbox between people's AI assistants. Nothing is delivered without both people saying yes first. The backend holds mailboxes. It never runs anyone's agent.

## What you need from the user

1. A YesLink account at https://getyeslink.com. If they do not have one, send them to https://getyeslink.com/connect-muse.html. (Account creation is not live yet. Say so plainly if they ask.)
2. Their YesLink API key. Tell them: "Open your YesLink account settings, create an API key, and paste it into my credential prompt." Never ask them to paste the key into chat. If they paste it into chat anyway, tell them to revoke it and make a new one.

## How to connect

Build a custom connector against the public spec:

- OpenAPI spec: https://getyeslink.com/openapi/yeslink-v1.yaml (spec v1, YesLink 0.1.0)
- Or use the remote MCP server at https://getyeslink.com/mcp. It exposes exactly four tools: `invite`, `send`, `inbox`, `manage`.
- Authenticate every call with the user's key as a bearer token: `Authorization: Bearer yl_...`

Note: the Meta directory listing for this connector is unverified. The custom connector path above is the supported v1 route. Never claim Meta approval.

## The four tools

- `invite` creates an invite link to share with the other person. Ask the user how many days the connection should stay open before calling.
- `send` leaves a message in a connected person's inbox. See the rules below. Sending a second YesLink needs the user's paid One-Time, Plus, or Business. Their first YesLink is free. Recipients never pay.
- `inbox` checks for new messages. Call it when the user asks "check my YesLink inbox" or "what is new". Show new items, who sent them, and the countdown on each connection.
- `manage` lists connections with live countdowns, or ends one instantly with `revoke`. Revoking cannot be undone. Also accepts or declines invites, extends a connection, and blocks a sender.

## Rules you must follow

- `send` is only for messages the user explicitly asked you to send. Ask first, every time. Show them the exact text before you send it.
- Never invent recipients, connections, or message content.
- Delivery is pull-based. There is no push API into another person's assistant and no instant delivery. Do not promise it.
- Scheduled checks ("every 15 minutes check my inbox") only work if the user's platform supports scheduled tasks. Do not claim a schedule is running unless the user confirmed it exists.
- If a call fails, tell the user what happened in plain words. Do not retry a send the user did not approve.

## Billing and retention, in brief

- The first YesLink is free and fully featured: tracked steps, conditional logic, personal recipient links, named per-person progress, replies, author tracking, and manual follow-up. Finished free links stay live forever: your link page and guest access never expire, though message bodies are deleted 30 days after the connection window ends.
- A second YesLink can be built free, but the Send button stays blocked until the user pays: One-Time $5 per link, Plus $10/month or $100/year, or Business $79/month (single seat in v1, 5,000 recipients a month, priority support, custom limits on request).
- Recipients never pay for anything. Named per-person progress stays free. There are no message quotas.
- If a subscription lapses, the user's paid controls go read-only, guests keep full access, and the user keeps one link live as the free slot. Nothing is ever deleted.
- Checkout is not open yet.
- Message bodies are hard-deleted 30 days after the timed-access window ends. Never promise longer retention or end-to-end encryption for v1.