---
name: refurbsitter
description: Set up RefurbSitter agent access, create Apple refurb restock watches, and handle signed webhooks.
---

# RefurbSitter agent playbook

Use this procedure when the account owner asks you to configure restock alerts.

## Connect to MCP

Use `https://refurbsitter.com/api/mcp` with OAuth or send an `Authorization: Bearer YOUR_API_KEY` header.

Use OAuth with Claude and ChatGPT connectors. In Claude Code, add the server and run `/mcp` to sign in.

```bash
claude mcp add --transport http refurbsitter https://refurbsitter.com/api/mcp
```

Authenticated REST requests require a Bearer API key.

## Get a key with the mailbox owner

To get a key without a browser, use `POST /api/agent/v1/signup` with the account owner’s `email` and an optional `label`. Save the returned `flow_id`.

Ask the mailbox owner for the six-digit code. Send it as a string with `flow_id` to `POST /api/agent/v1/signup/verify`. Store the returned `key` in a secret store.

For request examples, see the [signup reference](/docs/api#signup).

## Check the plan and ask before checkout

Call `get_account` or `GET /api/agent/v1/account`. Use `plan`, `watch_count`, `watch_limit`, and `allowed_channels` to decide what you can do.

Free agent access covers account and catalog reads and checkout. Use MCP for Spot watch operations. On Hunt, Fleet, or Reseller, use either MCP or REST for watch operations and one webhook destination.

If the owner chooses a plan, pass its ID as `plan` to `create_checkout_link` or `POST /api/agent/v1/checkout`. Checkout IDs are `refurb-spot-pass-19`, `refurb-hunt-pass-69`, `refurb-fleet-99`, `refurb-fleet-annual-999`, `refurb-spot-pass-9`. For example, `refurb-spot-pass-9` selects Spot. Give the checkout URL to the owner to complete payment. Read the account again before using paid operations. For Reseller, point the owner to [contact](/contact).

## Create a watch from a catalog ID

Call `list_catalog` or `GET /api/agent/v1/catalog`. Find a matching entry in a product’s `configurations`. Confirm the configuration and alert channels with the owner. Then send `config_id` and `channels` to `create_watch` or `POST /api/agent/v1/watches` on an eligible plan.

```json
{"config_id":"studio-m5-max-18-40@48/512","channels":["email"]}
```

Use the ID from the current catalog response when running this step. Read the resulting `watch` or call `list_watches` to confirm it.

## Enable and verify webhooks

With the owner’s agreement, set their public HTTPS `webhook_url` using `set_webhook` or `PUT /api/agent/v1/webhook`. Store the returned `signing_secret` when present. Include `webhook` in the watch’s `channels`.

Verify each delivery using the [signed webhook guide](/docs/webhooks). Check the signature over the timestamp and raw body, then deduplicate by the signed `id`. If the URL changes or the secret is rotated, update the verifier with the new secret.
