prefill and default look the same in Console. Only one of them lets an agent skip your required field.
I have 23 audit Actors on the Apify Store . They all do a version of the same thing: take a public record, check whether what it still claims is true, and write the verdict into a dataset. Last week I set out to prove they were unsafe for AI agents to chain together. I had a specific accusation in mind, I built the experiment to demonstrate it, and the experiment refused. What I found instead was…
The prefill and default settings in an input schema appear interchangeable in the Apify Console, but they serve distinct purposes. A prefill provides example values for a user to select from, while a default value is automatically used when the field is left empty by the user. This distinction is crucial for chaining actors together in an agent workflow.
In the case of the Actor called "http-status-checker," it contains a required field named "urls" with a default value. When an agent calls this actor through the MCP (Model Context Protocol) server and omits the "urls" field, the actor automatically uses the default value provided. This allows the agent to run without any issues or errors.
However, if the same actor is called without providing any value for the "urls" field at all, the actor will refuse the input and return an error. This is because there is no default value to fall back on when no value is supplied. The actor explicitly requires a value for the "urls" field to function correctly.
This discovery highlights the importance of understanding and properly utilizing prefill and default settings in input schemas. By recognizing the differences between these two settings, developers can prevent unexpected behavior when chaining actors together in agents, ensuring that the workflow handles missing input values appropriately.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
