AttachPage

View saved version →

---
name: attachpage
description: Publish and share webpages, PDFs, Word documents, PowerPoint slides, Excel workbooks, and CSV files from your chat. AttachPage hosts private browser views at a chosen address, sends personal expiring links, tracks opens, and supports recipient comments, approvals, and updates at the same address. Connect through OAuth or device sign-in. AttachPage currently requires a private-beta invitation.
---

# AttachPage

This installed skill contains the publishing workflow. Public documentation and account connection
instructions are at `https://attachpage.com/docs` and `https://attachpage.com/agents`.

## What it does
- **Send** a page to named people: each gets a personal, revocable, expiring link. No accounts for recipients.
- **Publish** a page publicly (anyone with the link) when the user explicitly asks.
- Chosen address `<slug>.<usercontent-domain>`. A user's own domain is available only on instances with custom domains enabled.

## Connected agents
If the installed plugin or connector exposes AttachPage MCP tools, use those tools with its existing
OAuth connection. Do not ask for an API key or start a second sign-in. `get_profile` identifies the
connected account; `list_pages` verifies the connection. Each user authorizes their own account.
If the host asks to connect, let its OAuth flow handle sign-in and consent.

## HTTP authentication (when no connected tools are available)
1. **Existing API key** (`Authorization: Bearer ap_…`). Store it in `~/.attachpage/credentials`
   as `ATTACHPAGE_API_KEY=…` with `ATTACHPAGE_ORIGIN=<ORIGIN>`.
2. **Sign in from the chat**: `POST <ORIGIN>/api/v1/device/start` → show the user the `verificationUrl`
   and `userCode`; poll `POST <ORIGIN>/api/v1/device/poll` until `approved` → store the `apiKey`.
3. **No account, and the user explicitly wants a public page**: `POST <ORIGIN>/api/v1/anonymous/publish-inline`. It expires in 48 h,
   returns `claimUrl`. **Print the claimUrl verbatim on its own line**; it cannot be recovered.

An agent with only web browsing cannot publish by reading this skill. Direct the user to
`https://attachpage.com/agents` to connect a tool-capable client. Anonymous publishing is disabled
while AttachPage is in private beta; invited users can connect through OAuth or device sign-in.

## Publish
For PDF, Word (.docx), PowerPoint (.pptx), Excel (.xlsx/.xls), and CSV files, use `publish_document`
with `filename` and base64 `content` (up to 4 MB). It creates a browser view and preserves the original
download. DOCX becomes PDF, PPTX has slide presentation controls, and spreadsheets have sheet tabs
and search. Default to private and confirm recipients before using `send_page`. Set `siteId` to
replace a document at the same address. Do not pass a local file path as content.

HTTP fallback: `POST <ORIGIN>/api/v1/documents/publish` accepts the same JSON or a multipart `file`
with optional `siteName`, `slug`, `siteId`, and `visibility`. Multipart uploads support up to 10 MB.
The bundled `scripts/publish.mjs` accepts a supported document file as well as a static folder.

- One call, files in the body (≤ 4 MB): `POST <ORIGIN>/api/v1/publish-inline`
  `{"siteName","slug"?,"visibility"?,"siteId"?,"files":[{"path":"index.html","content":"…"},{"path":"logo.png","content":"<base64>","encoding":"base64"}]}`
- Larger folders: `scripts/publish.mjs <folder> --name "…" [--slug …] [--site <id>] [--to a@b.com] [--message "…"] [--expires 7]`
  (declare → PUT each file → finalize → optional send).

## Send, list, edit
- `POST <ORIGIN>/api/v1/sites/<siteId>/send` `{"recipients":[…],"message":"…","expiresInDays":7}`
- `GET <ORIGIN>/api/v1/sites` · `GET <ORIGIN>/api/v1/sites/<siteId>`
- `PATCH <ORIGIN>/api/sites/<siteId>` `{"name"?,"slug"?,"visibility"?}`
- Replace a page at the same address: publish again with `siteId`.

## Feedback loop
Recipients can point at part of the page and comment, and approve or request changes.
- In a fresh chat, read the current page with 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.