The issue is specific to API calls requiring an API key during testing within the action creation page. Since your crypto API call (which didn’t need a key) worked fine while testing, but the stock API (which required a key) only worked after publishing, it suggests a possible restriction on authenticated API calls during the test phase. This might be a broader ChatGPT-4o limitation or a bug affecting custom actions with API keys.