# LinkSwap credentials

LinkSwap has no user accounts, no passwords, no email signup and no API key requirement.

## control_token

`submit_site` (MCP) / `POST /api/v1/sites` (REST) returns a `control_token` starting with `lsw_live_`. It is:

- shown **exactly once** and stored only as a hash — it cannot be recovered by LinkSwap or by support;
- scoped to a single listing;
- required by `verify_site` / `POST /api/v1/sites/{id}/verify` and by `cancel_placement` / `POST /api/v1/cancellations`;
- sent as the `control_token` tool argument, the `X-Control-Token` header, or the `control_token` JSON body field.

Agents should keep it in conversation state for the duration of the task. Humans can keep it in the browser: `/submit` and `/my` store it in this browser's local storage so the listing can be verified and managed later. Anyone holding the token can verify or remove that one listing, so treat it like a password and never publish it in a page, repository or chat log that is shared publicly.

## verification_token

The `verification_token` is embedded in `badge_html` and the alternative verification snippets. It is **not secret**: proving that a token appears on a website requires control of that website. The public MCP tool `get_badge` deliberately re-issues the snippet so a lost badge can be placed later. Reading badge code grants no editing rights.

## Reads

All GET endpoints and all read-only MCP tools are public. They expose only public listing fields — never tokens, email addresses, order details or internal identifiers.

## Optional X-API-Key

Not an authentication credential. It only changes how the daily limit of 5 submissions is counted (per key instead of per IP). It does not raise the limit and does not grant extra permissions.

## Cron and webhook secrets

`CRON_SECRET` protects `POST /api/v1/badge/recheck` and is never exposed to clients. `STRIPE_WEBHOOK_SECRET` verifies payment webhooks. Payment is applied only from a signed webhook event; a browser return URL is never trusted.

## Payments

A hosted checkout URL is returned for the human owner. Neither LinkSwap nor an agent should ever collect card details. Waffo Pancake is the merchant of record and PCI-DSS compliant payment processor; Stripe Checkout is the hosted checkout used where configured. See `/terms`, `/privacy`, `/refunds` and `/pricing`.
