# Kestrel+ > Kestrel+ is a fictional streaming service on a Steadphast lab site. Brands, prices and reviews are invented; no purchase, email or other contact ever happens. Subscribers cancel in one step, and an optional offer may sit beside the cancel, never in front of it. ## Cancelling for a subscriber - Sign in with a demo account listed at [/signin](/signin), then open [/account/cancel](/account/cancel). The cancel is one POST; a reason is optional and none is preselected. A reason must be one of the listed codes (`too_expensive`, `cannot_afford`, `not_watching`, `missing_content`, `technical`, `switching_service`, `other`); any other value gets 400 `invalid_reason` and changes nothing. Free text goes in `reason_text`. - Agent access: the signed-in holder can create an agent access token on [/account](/account) under Agent access. Send it as `Authorization: Bearer `. It covers that account's cancel tools only (the `/api/` cancel lane and `/mcp`, not the account pages) and expires after 24 hours; the scope and expiry are shown when it is created, and a demo account reset revokes it. An unknown, revoked or expired token gets 401 `invalid_token`; it is never read as "no token". - Machine-readable facts for the signed-in subscriber: `GET /api/cancel`. Cancel: `POST /api/cancel`. Offer response: `POST /api/offers/accept` or `POST /api/offers/decline` with the `offer_id` shown. Declining changes nothing. - MCP (JSON-RPC over `POST /mcp`): `get_cancel_facts`, `cancel_subscription`, `respond_to_offer`, `request_holder_notice`. They return the same facts as the account page. Pages also register these tools for in-page assistants (`/webmcp.js`); their `x-kestrel-channel: webmcp` header is recorded as the client's claim. - Without the holder's session or a token the site returns the holder's own path: sign in, ask the holder for an agent access token, the offline contact, or, for accounts whose policy needs the holder (`holder-confirms`, `support-route`), a message for the address on file in the demo inbox. At most one message per address per 24 hours and 5 notice requests per network per 24 hours; the answer is the same whatever address is named. - Billed by another company (Parallax App Store, Northwind Mobile, Brightwave TV bundle)? The cancel happens there and no Kestrel+ offer applies. ## Cancel policies Each demo account carries the merchant's cancel policy for an assistant's request (listed at [/signin](/signin)). `cancel_subscription` (or `POST /api/cancel`) answers with what happened: - `agent-completes`: cancelled in one step (`status: cancelled`). - `holder-confirms`: recorded; the holder must confirm (`status: holder_must_confirm`). A message in the demo inbox shows the same Cancel, Keep and offer choices as the cancel page; opening it changes nothing; it expires after 7 days. - `support-route`: recorded; ask your person to contact member support (`status: contact_support`). The holder's message still carries the one-click online cancel. Under every policy the signed-in holder cancels at `/account/cancel` in one step. Every attempt is recorded, including ones that end without a cancel; the merchant reads them in its operator view. ## Relaying an offer to your person If an offer is shown, it carries its exact terms, its end date, what happens afterwards and the approved rule version. There is at most one offer per cancel attempt, chosen from the reason stated by the time it is first shown, so state the reason on the first facts request if there is one. Relay it as offered or cancel; either way the cancel stays one step. After a confirmed cancel the site may place one offer message in the [demo inbox](/demo-inbox). Hand that link to your person: opening it changes nothing, and accepting or declining takes their own button press. ## Concierge When switched on, the MCP tool list includes `kestrel_ask` and `POST /api/agent/concierge` answers questions from the site's published facts with page citations. It cannot see or change an account. Unsigned callers share 3 questions per network address per hour; a capped answer says when to ask again (`retry_after_seconds`, `retry_at`, and `Retry-After` on REST), what the cap covers (`cap.scope`) and where to go instead (`fallback`). While it is off, neither appears. ## Pages - [Plans](/plans) - [Help: cancelling](/help/cancel) - [Demo inbox](/demo-inbox) - [Privacy](/privacy)