{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifcfe4qrihnwrn34ja53u2tvbbtpdvfgzpez2fktxeofv4wxb7e5q",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mfwi3hxjub72"
  },
  "path": "/t/building-a-browser-to-codex-bridge-via-codex-mcp-server-tou-clarification-needed/1375345#post_4",
  "publishedAt": "2026-02-28T12:15:16.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "@vb"
  ],
  "textContent": "Thanks @vb, you’re right — I was looking at the Consumer Terms of Use, which prohibits “automatically or programmatically extract data or Output.”\n\nAfter checking the OpenAI Services Agreement (for APIs/developers), the equivalent clause is narrower: it only restricts extracting data “other than as permitted through the Services.” Since `codex mcp-server` and `codex exec` are officially documented integration points — and Sign in with ChatGPT itself generates an API key under the hood — programmatic usage through these interfaces seems clearly intended.\n\nAppreciate the nudge in the right direction. That clears things up for my project.",
  "title": "Building a browser-to-Codex bridge via codex mcp-server — ToU clarification needed"
}