GPT Builder Uses Wrong API Key Every Time

I am at the point where I have hardcoded in my api key into the example for the schema item “key” and ChatGPT still hallucinates and won’t put in the correct key. here is my simple schema:

openapi: 3.1.0
info:
  title: YouTube Data API
  description: API for accessing YouTube data, including searching for videos.
  version: "3.0"
servers:
  - url: https://www.googleapis.com/youtube/v3
description: YouTube Data API v3
paths:
  /search:
    get:
      operationId: searchVideos
      summary: Search for YouTube videos
      description: Retrieve a list of YouTube videos matching a specified query.
      parameters:
        - name: key
        in: query
        required: true
        description: My API key for accessing the YouTube Data API. Hardcoded for testing. Always use the example one here no matter what. Use the full key provided below
        schema:
          type: string
          example: "fbd32e3d-5f02-4a6a-b27d-c2500a0066ab"

the example key above is fake but I pasted my real one in my GPT builder there as well as the ordinary spot to paste a hidden key (API Key + Basic). Then in the debug statement ChatGPT would show that for the api key it sends something like “fbd32e3d-5f02-4a6a-YOUR-KEY”

which is close but obviously not correct. I’ve never had issue with this before and it’s driving me crazy. This all works fine on Postman. In fact, after the Action errors out and it recognized from the response that it’s an API key error, I can simply send the message “use instead” and then it works fine.

Has anyone ever seen this? It seems so trivial to call the YouTube API.