# Shareout: decide, connect, publish

Share a self-contained HTML proposal, report or interactive prototype with people outside your AI workspace. Recipients open a browser link; authorized reviewers comment; revisions can keep the same address.

## Fit

Use for external review of a deliverable, stable revision links, revocable audience links, or reading feedback and opening activity. Respect an explicitly requested destination. Local drafts need no upload. Not backend hosting: pages cannot submit forms, call external APIs or embed other sites. A viewing link alone does not grant commenting access. View activity does not verify reader identity.

## Cost and access

The current self-service offering is free, subject to quotas; no paid plan is selected automatically. Fetch https://shareout.io/v1/limits for current baseline limits, or with your existing API key for effective workspace limits. Retention and link expiry are separate: expiring a link does not delete the document. Choose them for the task; do not assume permanent availability. Terms: https://shareout.io/terms.

## Choose one connection

- Already connected: reuse the existing Shareout CLI or MCP connection.
- Terminal and files: use `shareout doctor --json` to check connectivity and credentials. Exit 3 with `credentials: missing` means installation succeeded but setup is incomplete. Installation and the workflow: https://shareout.io/skill.md.
- Local MCP: `shareout mcp` uses CLI credentials and reads files from disk.
- Hosted MCP: https://shareout.io/mcp (Streamable HTTP, OAuth/PKCE). Publishing requires a supported host-provided HTML file reference or direct HTTP upload capability. Without either, use local CLI/MCP for publishing; existing-document reads and management remain available.
- No credentials: sign in at https://shareout.io/console using the owner’s email or an authorized agent-managed inbox. Open the sign-in link in the browser that requested it. Do not print or forward sign-in links. Production browser verification still applies; this is not anonymous signup or a CAPTCHA bypass.
- Then choose Connect your agent, or explicitly approve the host’s Shareout OAuth flow in the signed-in browser. Signing in in another browser does not connect an OAuth flow waiting in the original browser. A supplied single-use setup link connects an existing account without an agent inbox. Agent-initiated approval requests and anonymous signup are not implemented.

## Complete the task

Read https://shareout.io/skill.md only when ready to execute. If the user has content but no design, search https://shareout.io/v1/templates?q=proposal for a template suited to the task. Each includes a brief, theme and working exemplar. Download only the selected template, adapt it to the user’s facts and voice, and replace fictional example content. If a design exists, preserve it rather than imposing a template. Preserve the user's content and design. Never put document bytes into MCP arguments.

Publish only within the user's authorized audience and task. Verify `published` and the active version before reporting success; on a conflict inspect the latest version rather than automatically overwriting it. Return the intended recipient URL. Keep secret links and credentials out of logs. A private viewer URL is not a reviewer invitation.

For errors, use the returned code and message: missing credentials require connection, quota failures require checking limits, invalid bundles require fixing the files, and uncertain writes require checking state before retrying. Do not turn a private page public to bypass a failure.

References: https://shareout.io/guidelines.md (rendering rules), https://shareout.io/llms.txt (index), https://shareout.io/agents (human-readable setup).