The Country box now reads what people actually send, and a value it cannot place runs on the default market instead of refusing the whole list. Three spellings that used to be refused are read now, and each of them lands on a market the bundled country table already carries, so nothing is ever invented: a locale tag is read for its market half, since the language half is what the Language field already carries (en-GB is the United Kingdom, pt-BR is Brazil, and US-CA is still not Canada); a comma list runs on the first country it names, so germany, france and Dubai, United Arab Emirates both work; and the value we could not read before now says which market the run used. Where nothing at all can be placed, the run no longer returns you an empty dataset: it uses the default market, United States, and says so three times over — an uncharged first row naming both the value you sent and the market used, the same sentence on the run page, and the market itself in the country column of every delivered row. A bare number that is not a country code gets its own sentence, because it is not a typo: that is a Google Ads target for a place inside a country — a city, a region, a postal code — and this actor reports volume one whole country at a time, so the row tells you to send the country's own code or name. Two values are still refused outright, uncharged and one row per keyword, because a default there would be worse than nothing: a market the source carries no data for at all (returning a different country's numbers to someone who named a real one is the one thing this field must never do), and a whole-region ask like worldwide or EU, where picking a single country for you is exactly the substitution you did not ask for. A Country box longer than any country name is refused too — that is a pasted block, not a market. Nothing about what you pay changed with this: the per-keyword price, the fresh-lookup fee, the input fields, the output columns and the charged events are all as they were, the notice row is uncharged like every other notice, and a keyword that is not looked up is still never charged.
Fresh search-volume lookups now have a daily allowance on the Apify free plan. On a free Apify plan this actor makes at most 2 fresh lookups per account per day. Everything you have already paid for is untouched by it: a keyword your account already had inside 30 days is still handed straight back uncharged, a keyword already in our own 30-day cache is still delivered and charged exactly as before, and the run still finishes successfully either way. Past the allowance a keyword that would have needed a brand-new lookup is simply not looked up — it ships as its own uncharged row saying so, resumeCursor lists it so a later run picks it up where it stopped, and the run page says the allowance is used and that the rest comes back the next day or on any paid plan. If the run's API token cannot open your account's key-value store the daily count cannot be read at all, so that run keeps a single-run allowance of one fresh lookup and the rows and the run page say so too: a count we cannot read never becomes an unlimited allowance, and never becomes a refusal either. Paid plans are not affected in any way — the allowance does not exist on them — and a run whose plan this build cannot read is treated as a paid one. Nothing about what you pay changed here: the per-keyword price, the $0.19 fresh-lookup fee and the two cases that waive it, the input fields, the output columns and the charged events are all exactly as they were, and a keyword that was not looked up is never charged.