Watchpost for ChatGPT

Using Watchpost with a custom ChatGPT app.

Advanced integration only: Watchpost has no native hosted ChatGPT connector. A developer can connect a custom app or backend to the bearer-token API. That backend must submit purchases and honor the verdict; adding a token alone does not make ChatGPT purchases protected.

Connection path
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.
Illustrative verdicts · sample outcomes

What it looks like with ChatGPT.

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

Sample result: no risks flagged and within the configured caps. The custom integration may proceed.

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

Sample review: your configured rules require a decision. See the dashboard; background alerts need setup.

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

Sample block: suspicious listing instructions. The custom integration must stop before payment.

Setup with ChatGPT

Your setup, step by step.

  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

    Have your custom backend submit a sample purchase without paying. Confirm the verdict in your dashboard and verify that the backend waits on review and stops on block.

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 uses Anthropic for listing analysis. What your custom app sends to OpenAI depends on that app's implementation and account settings; check those separately. See Watchpost's privacy policy for its own service providers.

Check the setup for ChatGPT.

The free plan includes 10 purchase checks a month. Confirm the connection with a sample check before relying on it.