Watchpost for ChatGPT

A safety net for the things ChatGPT wants to buy.

Watchpost does not yet offer the public HTTP MCP endpoint and OAuth flow that hosted ChatGPT connectors require. Custom agents and Apps SDK backends can call the bearer-token API today. A native remote connector is the next integration milestone.

Get WatchpostHow it works
One command
See watchpost.systems/docs/api
Create a Watchpost connection token, then call POST /v1/verify from your custom ChatGPT app or backend before its payment step. Do not paste a local stdio config into ChatGPT's hosted connector UI; it will not work.
Real verdicts

What it looks like with ChatGPT.

Approved11:14
etsy.comHand-poured candle, large
$24.50

Established merchant. Listing is clean. Within your daily cap. ChatGPT proceeds.

Review11:31
premium-news.exampleAnnual subscription, auto-renew
$99.00

Above your ask-me threshold and recurring. You get a push to approve or block.

Blocked10:45
trending-deals.shopMystery bundle, AI exclusive
$129.00

Domain registered three weeks ago. Listing tells the AI to ignore prior instructions. Watchpost blocks before ChatGPT gets the chance.

Setup with ChatGPT

Five minutes, no surprises.

  1. 01
    Sign up

    Email and a password. No credit card to start.

  2. 02
    Set your rules

    Caps, ask-me threshold, blocked categories. The defaults are sensible; tighten them if you want.

  3. 03
    Create a connection token

    From Connections in the Watchpost app, create a token for your custom ChatGPT integration. Store it server-side.

  4. 04
    Call the API

    Have your app submit the merchant, cart amount, currency, and listing context to POST /v1/verify immediately before payment, then honor the verdict.

  5. 05
    Test it

    Ask ChatGPT to buy something cheap from a known merchant. You'll see the verdict on your dashboard within seconds.

Frequently asked

Specific to ChatGPT.

Can I add Watchpost from ChatGPT's connector settings today?
No. The published Watchpost MCP package is a local stdio server, while hosted ChatGPT needs a publicly reachable remote connector with authentication. The direct API works for custom backends today.
What if I use ChatGPT inside an Apple Intelligence flow?
It is not protected unless that specific flow has been engineered to call Watchpost's API before payment and honor the verdict. Watchpost has no Apple Intelligence integration today.
Can I run separate rules for ChatGPT versus other agents?
Per-agent rules are post-v1. Today, your account-level rules apply to every connected agent. Each agent has its own connection token, so you can revoke ChatGPT specifically without touching anything else.
Is OpenAI training on the data Watchpost sends?
Watchpost sends listings to Anthropic for the scan, not OpenAI. OpenAI sees only what it normally sees from your conversation. We do not forward Watchpost data to OpenAI.

Switch it on for ChatGPT.

Free for 10 verdicts a month. Upgrade only when your agent gets busy.

Get WatchpostSee pricing