# Install Pref in your own Muse account

Muse is the first supported guided custom-connector path. Public enrollment is being prepared; an operator-assisted setup path is proposed for release. There is no public-directory listing, automatic installer, native ChatGPT connector or MCP endpoint. Installation in another person's account still requires their consent and actual acceptance.

## Before you start

Request access at **sam@thesideletter.co** and read [getting started](/getting-started), [capabilities](/capabilities), [privacy](/privacy) and [terms](/terms). After identity and consent verification, your operator supplies the exact service origin and arranges your own short-lived scoped key through secure capture. The initial tenant stays synthetic-only. Do not send a key through a prompt, email, URL or support form.

The existing private pilot uses `https://portfolio-agent-production-94f3.up.railway.app`. That address is not a public signup or authority to use the pilot owner's credential. Use the host your operator explicitly approved for your setup.

## Create the private connector

In your own Muse account, ask:

> Create a private custom connector named portfolio-agent for the exact HTTPS service origin my operator supplied. Read that origin's / guide and /openapi.json schema. Configure Authorization: Bearer authentication only for that exact API host. Request the key through secure credential capture; never ask me to paste it into this conversation. Start with session identification and saved-record reads. Do not access email or import real data yet.

The observed Muse installation used its supported secure API credential capture with bearer-header placement and an exact API-host allowlist. Muse created actions from the service documentation; do not assume automatic OpenAPI import. If your runtime cannot offer secure capture or build the required actions, stop and [ask support](/support).

Only enter the supplied key in the supported secure credential form. Confirm the first authenticated call succeeds; capturing a key alone does not prove installation. Call `describe_session` and check the expected client label, synthetic-only mode and read/write permissions. The client label identifies this credential. It is different from the named delivery consumer used later.

## Check the actions actually available

The served schema is authoritative for that service version. Initially verify `describe_session`, `list_investments`, `review_portfolio` and onboarding-only `save_investment`. The current interface also documents `get_collection_coverage`, `record_collection`, `list_document_evidence`, `prepare_selected_briefing`, `get_pending_briefing_status`, `acknowledge_briefing` and `download_portfolio_spreadsheet`. Correction actions need a separately authorized writer; the ordinary maintenance key cannot correct assignments or create holdings.

Missing actions are capability gaps. Ask support to refresh the connector against the actual schema; do not invent endpoints, silently omit history or paste credentials into improvised requests. Public pages and source code do not install actions in Muse.

## Prove an invented save and fresh read

Ask Muse to save an invented holding and invented legal owner with synthetic=true and an invented urn:synthetic source. Open a fresh conversation and ask it to retrieve the saved test from the API without supplying its contents or ID as a hint. Compare the same server observation ID, owner and source. A remembered answer does not pass.

If this fails, stay synthetic-only and ask support. Python/HTTP synthetic tests are engineering evidence; they do not replace this check in the actual user's Muse account.

## Confirm holdings before real collection

Use an optional investment list/spreadsheet or bounded discovery through your own separately authorized email and accessible platforms. Confirm uncertain candidates, legal owners and vehicles using specific evidence. Lists and invitations do not establish ownership or funding. Unknown fields remain unknown.

Agree on the exact holdings, sources and date window before real enablement and the first bounded import. Keep source credentials with the assistant/provider. Save concise sourced facts and references, never full emails, attachments, tax/account numbers, cookies or access-bearing URLs. Verify the saved facts in a fresh conversation.

The operator then retires the import key and checks rejection after the required hosted registry restart. Enter a separate maintenance key through secure capture with `portfolio:read`, `collection:write`, `delivery:write` and one named `delivery_consumers` entry. This does not authorize new source permissions, a destination or a schedule. Owner deletion authority remains separate.

## Read, correct and download

[Using Pref in Muse](/public/using-in-muse.md) has review, discovery and correction prompts. For a source-backed correction, reread current evidence and preserve history. Download should expose the authenticated CSV as a usable portfolio.csv file through Muse's supported artifact UI. A success message is not download acceptance.

For selected delivery, prepare only the exact versions being shown and acknowledge only after actual private destination receipt of every selected change. A fresh broad briefing can contain all history; never acknowledge it after showing one update. Scheduler output alone is not delivery. The [neutral recipe](/public/connector-recipe-v1.md) describes this operator/client contract.

The hosted private pilot serves v0.4.4. On-demand source save/fresh retrieval and selected acknowledgement/quiet repeat passed for that pilot. Current Muse correction/download UX, automatic collection with confirmed private delivery, ongoing retained backups and another consenting user's complete experience remain operational gates. No new job or public activation is implied. The public enrollment objective remains; no invitation-only or on-demand-only fallback is selected here.

[Support, revocation and deletion](/support) · [Operator runbook](/public/secure-onboarding.md)