`firecrawl-build` marks `FIRECRAWL_API_KEY` as required, but keyless execution is allowed

Hi team - I was using Firecrawl through Codex.

The firecrawl-build skill declares:
inputs:
- name: FIRECRAWL_API_KEY
- ...
**required: true**

Based on that, the agent-generated script initially treated the API key as mandatory and stopped when FIRECRAWL_API_KEY was not set.
But later, the agent removed its own hard requirement, retried the same v2 /scrape flow without the auth header, and the run succeeded through the available keyless path.
That created some confusion for implementation logic: it wasn’t clear whether the missing-key case should be treated as a real error, or as a supported fallback the agent should allow.

It would help to clarify the intended behavior across all resources :)

Start with the firecrawl-build skill's input declaration and compare its required FIRECRAWL_API_KEY setting with the reported keyless v2 /scrape behavior. Done means the declared requirement and missing-key behavior are consistent, with the intended behavior clarified across the relevant resources.

Written by the indexing model from the issue text.