{
  "schema_version": "1.1",
  "id": "archive:https://openai.com/index/introducing-chatgpt-wallet",
  "slug": "introducing-chatgpt-wallet-1mib2b3",
  "url": "https://feed7.dev/p/introducing-chatgpt-wallet-1mib2b3",
  "title": "Introducing ChatGPT Wallet",
  "why_included": "ChatGPT Wallet lets users approve agent purchases without sharing card details with the agent or merchant. Builders may need to account for agent access and payment-risk checks in existing commerce flows.",
  "summary": "ChatGPT Wallet uses a payment token instead of exposing card details, and requires a security check for each purchase. It is initially rolling out in dots to eligible ChatGPT Pro subscribers in the US. The Commerce Partner Playbook covers product feeds, agent access, and payment risk systems.\nIf you build a commerce site, check whether your CDN or firewall blocks signed ChatGPT agent requests, and ask payment and risk providers how they handle agent purchases. Existing checkout flows can accept the wallet’s payment tokens.\nAvailability is limited, and some sites or risk systems may block or decline legitimate agent purchases. Each purchase currently needs user approval; delegated purchases with spending limits are a future direction.",
  "practical_implication": "",
  "agent_context": "ChatGPT Wallet uses a payment token instead of exposing card details, and requires a security check for each purchase. It is initially rolling out in dots to eligible ChatGPT Pro subscribers in the US. The Commerce Partner Playbook covers product feeds, agent access, and payment risk systems.\nIf you build a commerce site, check whether your CDN or firewall blocks signed ChatGPT agent requests, and ask payment and risk providers how they handle agent purchases. Existing checkout flows can accept the wallet’s payment tokens.\nAvailability is limited, and some sites or risk systems may block or decline legitimate agent purchases. Each purchase currently needs user approval; delegated purchases with spending limits are a future direction.",
  "source": {
    "name": "OpenAI",
    "url": "https://openai.com/index/introducing-chatgpt-wallet",
    "published_at": "2026-11-13T15:00:00.000Z"
  },
  "source_class": "blog_post",
  "content_type": "Official Release",
  "layer": "tools",
  "domains": [],
  "topics": [
    "computer-use",
    "tool-use"
  ],
  "verification": {
    "status": "official_source",
    "label": "Official Source",
    "method": "source_feed",
    "verified_at": null
  },
  "uncertainty": [],
  "connected_context": {
    "meaning": "Against the candidates’ focus on how agents navigate and operate interfaces, this Signal adds a commerce-specific boundary: purchases use payment tokens, but each one still requires user approval. It makes permission and payment-risk handling part of agent readiness while leaving delegated spending as a future direction.",
    "corpus_size": 1089,
    "generated_at": "2026-11-14T10:52:58.947Z",
    "connections": [
      {
        "title": "The Power of Meta Access in the Software of the Future --- Demonstrated on LLM Chat UIs and Chat AI",
        "source_name": "arXiv",
        "source_url": "https://arxiv.org/abs/2611.08428v1",
        "feed7_url": "https://feed7.dev/p/2611-08428v1-1qand6b",
        "reason": "Both put user approval and bounded permissions at the center of agent actions; the Wallet applies that boundary to purchases, while the paper discusses broader application access."
      }
    ]
  },
  "lifecycle": "Current",
  "published_at": "2026-11-13T15:00:00.000Z",
  "modified_at": "2026-11-13T15:00:00.000Z",
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/introducing-chatgpt-wallet-1mib2b3",
    "json": "https://feed7.dev/p/introducing-chatgpt-wallet-1mib2b3.json",
    "markdown": "https://feed7.dev/p/introducing-chatgpt-wallet-1mib2b3.md"
  }
}