Docs

Watchpost does one thing: it reads an intended purchase and returns approve / review / block before the money moves. There are four ways to submit a request. Your integration must call Watchpost and honor its answer; Watchpost cannot independently stop a payment outside that flow. Available analysis depends on the details submitted and external services.

Connector install

For Claude Desktop and Cursor. Run npx @watchpost/mcp install, confirm in the browser tab it opens, restart the agent: the CLI writes the MCP config for you. Install guide.

API reference

For developers building their own agent or backend, including custom ChatGPT integrations. Hosted ChatGPT has no native Watchpost connector. ACP and AP2 input adapters are available; they do not independently verify merchant signatures. API reference.

Skill

For compatible Agent Skills runtimes such as OpenClaw and Hermes. A Markdown instruction file and a helper script your agent loads, no MCP host involved. How to add it.

Browser extension

A beta prototype that pauses recognized checkout-button clicks for a verdict. Detection is heuristic and can miss flows; it is not a universal payment gate. Side-load for now. Details.

Not sure which

For Claude Desktop or Cursor, start with the local connector and its prerequisites. For a custom backend, use the API. Compatible skill runtimes need a configured skill and token. Whichever path you choose, verify a sample check without paying before relying on it.